[lcdproc] keypad support
Fri, 08 Jun 2001 22:10:15 -0400
Joris Robijn wrote:
> > > You only need to connect as many keys as you need. You can connect up
> > > to 55 keys in a matrix like below and yes you only need the switches.
> I'm building keypad support into the HD44780 driver. Now, I am
> wondering, what keypad layout should I set as default, to be compatible
> with some standard keypads ? Can you tell me about how that keypad you
> have (or better: keyboard, with so many keys) has it's layout ? A link
> to a description would be fine too...
I have the matrix orbital 3x3 matrix UP, DOWN, LEFT, RIGHT, ENTER, F1,
I'll have to forward the info to you later (on my other box downstairs).
I wrote my own keypad reader code, but used some of your ideas from the
CVS HD44780 code. If my customer allows me, I'll release it.
You might want to:
1) make par_keypad.[h,c] to contain the keypad code
functions such as:
int read_keypad (int mode, int port, int X, int Y)
mode would be one of several standard keypad
connections for input and output (or we could have just
one D0..D7 for output, busy, etc. for input).
X is D0..N
Y is the input count
2) make keypad_config.h to contain a struct with the matrix
- define several standard matrix configurations with ASCII wiring
- define several options to select which keypad you want
- provide notes on how to customize your own keypad
- provide a template for customized keypads
3) provide notes on how to customize the keypad for your
own applications (including schematics, a test keymap of
A, B, C, D, E, etc., press a key, see what you get, then
change the value to something you want to be returned, etc.).
I'll have to forward my parallel port parport.h and notes
file to you tomorrow.
W. Wade, Hampton <email@example.com>
If Microsoft Built Cars: Every time they repainted the
lines on the road, you'd have to buy a new car.
Occasionally your car would just die for no reason, and
you'd have to restart it, but you'd just accept this.
To unsubscribe from this list send a blank message to