nanogui: Thread: Keypad implementation

All,

I am looking into the microwindows code on how to implement a 
keypad rather than a PC-style keyboard but the kdb_*  files don't 
seem to implement a hardware keypad, just a tty keyboard with 
scannable options. Has anyone done this already? Specifically, I am 
attempting to implement a custom 21 key keypad but could probably 
modify a generic 8x8 keypad if someone has already done this work.

Reference: I am developing on an Embedded Planet 823 platform
running MVista HardHat 2.2.14 kernel.

Regards,
     Michael Pergola
     Software Engineer
     Baltimore, MD  21236     (410) 931-6778 x4259

> the kdb_*  files don't
> seem to implement a hardware keypad, just a tty keyboard with
> scannable options.

To be more correct, we just implement keyboards that have a kernel driver 
interface, so that abstracts the code just enough.  For example, the Ipaq is 
pretty close to being a "hardware" keypad, but the driver is written in such 
a way as to provide a common interface for us to key into (no pun intended).

What you really should do is develop a simple kernel module that reads your 
keyboard, and sends back a set of common scancodes.  Then, you could copy the 
kbd_ipaq.c file, and re-engineer it for your own use.    That way, you can 
get a common interface, reuse a ton of code, and have an easy way to make 
changes in the future without rebuilding the entire system.

Jordan


On Friday 11 January 2002 07:22, Pergola, Michael mentioned:
> All,
>
> I am looking into the microwindows code on how to implement a
> keypad rather than a PC-style keyboard but the kdb_*  files don't
> seem to implement a hardware keypad, just a tty keyboard with
> scannable options. Has anyone done this already? Specifically, I am
> attempting to implement a custom 21 key keypad but could probably
> modify a generic 8x8 keypad if someone has already done this work.
>
> Reference: I am developing on an Embedded Planet 823 platform
> running MVista HardHat 2.2.14 kernel.
>
> Regards,
>      Michael Pergola
>      Software Engineer
>      Baltimore, MD  21236     (410) 931-6778 x4259
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####

Jordan,

Great idea. Thanks for pointing me in the right direction. 

How is the iPAQ physically connected with microwindows?
On the Embedded Planet I have an available serial port but
our current product's implementation brings the keypad's
lines directly into the microcontroller.

Mike

> -----Original Message-----
> From:	Jordan Crouse ####@####.####
> Sent:	Friday, January 11, 2002 10:45 AM
> To:	Pergola, Michael; ####@####.####
> Subject:	Re: [nanogui] Keypad implementation
> 
> > the kdb_*  files don't
> > seem to implement a hardware keypad, just a tty keyboard with
> > scannable options.
> 
> To be more correct, we just implement keyboards that have a kernel driver 
> interface, so that abstracts the code just enough.  For example, the Ipaq
> is 
> pretty close to being a "hardware" keypad, but the driver is written in
> such 
> a way as to provide a common interface for us to key into (no pun
> intended).
> 
> What you really should do is develop a simple kernel module that reads
> your 
> keyboard, and sends back a set of common scancodes.  Then, you could copy
> the 
> kbd_ipaq.c file, and re-engineer it for your own use.    That way, you can
> 
> get a common interface, reuse a ton of code, and have an easy way to make 
> changes in the future without rebuilding the entire system.
> 
> Jordan
> 
> 
> On Friday 11 January 2002 07:22, Pergola, Michael mentioned:
> > All,
> >
> > I am looking into the microwindows code on how to implement a
> > keypad rather than a PC-style keyboard but the kdb_*  files don't
> > seem to implement a hardware keypad, just a tty keyboard with
> > scannable options. Has anyone done this already? Specifically, I am
> > attempting to implement a custom 21 key keypad but could probably
> > modify a generic 8x8 keypad if someone has already done this work.
> >
> > Reference: I am developing on an Embedded Planet 823 platform
> > running MVista HardHat 2.2.14 kernel.
> >
> > Regards,
> >      Michael Pergola
> >      Software Engineer
> >      Baltimore, MD  21236     (410) 931-6778 x4259
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: ####@####.####
> > For additional commands, e-mail: ####@####.####

Well, of course, I don't want to mislead you....  There are two very 
different concepts on the ipaq.  You have the serial console, which acts as 
the controlling tty (through /dev/ttySA0) for the system, and *then* you have
a set of hardware keys that are accessable through a special driver file.  
These are the keys that are supported in Microwindows.  We currently don't 
have any support for reading from the serial port (though we might, if 
someday I break down and buy a Stowaway keyboard).  

But for the hardware keys (and when I say hardware keys, I mean the half 
dozen keys on the front of the device), they also communicate through a 
microcontroller, which is handled by a driver that decodes the keypress, and 
sends them as "scancodes" through a device file.  I put scancodes in quotes, 
because its not trying to pretend it's a tty, but because it is simply 
abstracting the actual hardware codes with a common #define.

Jordan

On Friday 11 January 2002 09:11, Pergola, Michael mentioned:
> Jordan,
>
> Great idea. Thanks for pointing me in the right direction.
>
> How is the iPAQ physically connected with microwindows?
> On the Embedded Planet I have an available serial port but
> our current product's implementation brings the keypad's
> lines directly into the microcontroller.
>
> Mike
>
> > -----Original Message-----
> > From:	Jordan Crouse ####@####.####
> > Sent:	Friday, January 11, 2002 10:45 AM
> > To:	Pergola, Michael; ####@####.####
> > Subject:	Re: [nanogui] Keypad implementation
> >
> > > the kdb_*  files don't
> > > seem to implement a hardware keypad, just a tty keyboard with
> > > scannable options.
> >
> > To be more correct, we just implement keyboards that have a kernel driver
> > interface, so that abstracts the code just enough.  For example, the Ipaq
> > is
> > pretty close to being a "hardware" keypad, but the driver is written in
> > such
> > a way as to provide a common interface for us to key into (no pun
> > intended).
> >
> > What you really should do is develop a simple kernel module that reads
> > your
> > keyboard, and sends back a set of common scancodes.  Then, you could copy
> > the
> > kbd_ipaq.c file, and re-engineer it for your own use.    That way, you
> > can
> >
> > get a common interface, reuse a ton of code, and have an easy way to make
> > changes in the future without rebuilding the entire system.
> >
> > Jordan
> >
> > On Friday 11 January 2002 07:22, Pergola, Michael mentioned:
> > > All,
> > >
> > > I am looking into the microwindows code on how to implement a
> > > keypad rather than a PC-style keyboard but the kdb_*  files don't
> > > seem to implement a hardware keypad, just a tty keyboard with
> > > scannable options. Has anyone done this already? Specifically, I am
> > > attempting to implement a custom 21 key keypad but could probably
> > > modify a generic 8x8 keypad if someone has already done this work.
> > >
> > > Reference: I am developing on an Embedded Planet 823 platform
> > > running MVista HardHat 2.2.14 kernel.
> > >
> > > Regards,
> > >      Michael Pergola
> > >      Software Engineer
> > >      Baltimore, MD  21236     (410) 931-6778 x4259
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: ####@####.####
> > > For additional commands, e-mail: ####@####.####
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####