keyboard + custom keypad.
Hi, I need to add a keypad to a product in development that will co-exist with the standard keyboard. It will be a fairly dumb pad capable of generating the equivalent of function keys F1 thru F8. The desired goals are: invisible to the syscons driver (and thus X11). works in parallel (ie. simultaniously) with the keyboard. Looking over the kbd/atkbd/atkbdc/syscons source I havn't yet "seen" a clear strategy for cleanly hooking into the existing code. Any suggestions? I also could use a pointer to any docs out there that describe the structure behind this new bus organization, and the keyboard drivers in particular! tia, -- Steve Passe | powered by s...@csn.net|Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: keyboard + custom keypad.
> > Hi, > > > > I need to add a keypad to a product in development that will co-exist > > with the standard keyboard. It will be a fairly dumb pad capable of > ... > > You could just design the pad using a "keyboard wedge" so that it lives > on the same bus as the keyboard. This is well-understood tech that's > been used for years for things like barcode scanners... In this case its already designed, sitting on a combo card with other sections of the product. Basically, I get an INTR whenever any of 12 keys is closed or opened. I then read 2 bytes from the ISA bus to determine the current state of all 12 keys. Comparing this to the previous state I determine which key changed, then "create" a datum equal to F1 thru F12, as appropriate. The puzzle is where to inject this datum into the flow of data going between atkbdc/atkbd/kdbio/syscons... ps. I am surprised my mail made it to hackers, I just changed ISPs and reverse name lookups are still failing, and hub claimed to have rejected the mailing! -- Steve Passe | powered by s...@csn.net|Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
keyboard + custom keypad.
Hi, I need to add a keypad to a product in development that will co-exist with the standard keyboard. It will be a fairly dumb pad capable of generating the equivalent of function keys F1 thru F8. The desired goals are: invisible to the syscons driver (and thus X11). works in parallel (ie. simultaniously) with the keyboard. Looking over the kbd/atkbd/atkbdc/syscons source I havn't yet "seen" a clear strategy for cleanly hooking into the existing code. Any suggestions? I also could use a pointer to any docs out there that describe the structure behind this new bus organization, and the keyboard drivers in particular! tia, -- Steve Passe | powered by [EMAIL PROTECTED] |Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: keyboard + custom keypad.
> > Hi, > > > > I need to add a keypad to a product in development that will co-exist > > with the standard keyboard. It will be a fairly dumb pad capable of > ... > > You could just design the pad using a "keyboard wedge" so that it lives > on the same bus as the keyboard. This is well-understood tech that's > been used for years for things like barcode scanners... In this case its already designed, sitting on a combo card with other sections of the product. Basically, I get an INTR whenever any of 12 keys is closed or opened. I then read 2 bytes from the ISA bus to determine the current state of all 12 keys. Comparing this to the previous state I determine which key changed, then "create" a datum equal to F1 thru F12, as appropriate. The puzzle is where to inject this datum into the flow of data going between atkbdc/atkbd/kdbio/syscons... ps. I am surprised my mail made it to hackers, I just changed ISPs and reverse name lookups are still failing, and hub claimed to have rejected the mailing! -- Steve Passe | powered by [EMAIL PROTECTED] |Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
