Re: keyboard hook?
> Input API looks nice. For now, I'll write a patch against pc_keyb.c to add a > hook for my qoder stuff, and a loadable module for the meat of the > driver. Okay. > Then I'll port up to the input API. Just send me the code and I will place it into CVS. >I have a Sparc here; does it have drivers you wish to have ported? Alot of work has to be done their :-/ If you are up to it I would be happy to work with you. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: keyboard hook?
Thanks, I'm loking through your driver now. Does the input api already/currently support ps2 keyboards? -M On Sat, Jun 02, 2001 at 08:40:04PM -0700, James Simmons wrote: > > Hi! > >Your best bet for a kernel driver is to use the linux input api like > the usb keyboard do. The drivers are pretty simple to write and since all > the keyboard drivers will be port over to this api it will save a lot of > work done the road. If you need help let me know. I will be glad to help. > It sounds alot alike the p2 to serial driver just placed in our CVS. You > can access our CVS by doing > > cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/linuxconsole login > > cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/linuxconsole >co ruby > > The driver is in ruby/linux/drivers/input as ps2serkbd.c. > > > I'm beginning the process of writing a driver for the "Qoder" > > keyboard-fob barcode scanner made by InterMec. It communicates with the > > host computer using the PS/2 port by way of a "dock" that sits in > > between the keyboard and the computer. > > > One of them is "turn > > numlock light on," which I can do with an ioctl from userspace (as root, > > anyway), but also caps lock, num lock and carriage-return scancodes. > > EV_LED > > > The CueCat driver written by Pierre Coupard also modifies the keyboard > > driver. It would be nice if it was possible to load modules that hook > > into keyboard processing without requiring a kernel patch. And perhaps > > there is, but I haven't run across it yet. > > input api :-) > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: keyboard hook?
> Thanks, I'm loking through your driver now. Does the input api > already/currently support ps2 keyboards? With the current tree no. The work around is to make input api keyboards behave as PS/2 keyboards. In 2.5.X ps2 keyboards will be input api based. As you can see we already have PS/2 input api driver (i8042.c and atkbd.c). I have been using it for several months now. It is just a matter of making sure it works on other platforms besides intel. P.S I also need to port other keyboard drivers on other platforms over to the input api and test these drivers. If anyone would like to help out contact me. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: keyboard hook?
Input API looks nice. For now, I'll write a patch against pc_keyb.c to add a hook for my qoder stuff, and a loadable module for the meat of the driver. Then I'll port up to the input API. The Qoder is strictly ps/2 keyboard, as far as its interface goes, so I cannot use the input API for now. I have a Sparc here; does it have drivers you wish to have ported? On Sun, Jun 03, 2001 at 09:02:18PM -0700, James Simmons wrote: > > > Thanks, I'm loking through your driver now. Does the input api > > already/currently support ps2 keyboards? > > With the current tree no. The work around is to make input api keyboards > behave as PS/2 keyboards. In 2.5.X ps2 keyboards will be input api based. > As you can see we already have PS/2 input api driver (i8042.c and atkbd.c). > I have been using it for several months now. It is just a matter of making > sure it works on other platforms besides intel. > > P.S >I also need to port other keyboard drivers on other platforms over to > the input api and test these drivers. If anyone would like to help out > contact me. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: keyboard hook?
Input API looks nice. For now, I'll write a patch against pc_keyb.c to add a hook for my qoder stuff, and a loadable module for the meat of the driver. Then I'll port up to the input API. The Qoder is strictly ps/2 keyboard, as far as its interface goes, so I cannot use the input API for now. I have a Sparc here; does it have drivers you wish to have ported? On Sun, Jun 03, 2001 at 09:02:18PM -0700, James Simmons wrote: Thanks, I'm loking through your driver now. Does the input api already/currently support ps2 keyboards? With the current tree no. The work around is to make input api keyboards behave as PS/2 keyboards. In 2.5.X ps2 keyboards will be input api based. As you can see we already have PS/2 input api driver (i8042.c and atkbd.c). I have been using it for several months now. It is just a matter of making sure it works on other platforms besides intel. P.S I also need to port other keyboard drivers on other platforms over to the input api and test these drivers. If anyone would like to help out contact me. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: keyboard hook?
Thanks, I'm loking through your driver now. Does the input api already/currently support ps2 keyboards? With the current tree no. The work around is to make input api keyboards behave as PS/2 keyboards. In 2.5.X ps2 keyboards will be input api based. As you can see we already have PS/2 input api driver (i8042.c and atkbd.c). I have been using it for several months now. It is just a matter of making sure it works on other platforms besides intel. P.S I also need to port other keyboard drivers on other platforms over to the input api and test these drivers. If anyone would like to help out contact me. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: keyboard hook?
Thanks, I'm loking through your driver now. Does the input api already/currently support ps2 keyboards? -M On Sat, Jun 02, 2001 at 08:40:04PM -0700, James Simmons wrote: Hi! Your best bet for a kernel driver is to use the linux input api like the usb keyboard do. The drivers are pretty simple to write and since all the keyboard drivers will be port over to this api it will save a lot of work done the road. If you need help let me know. I will be glad to help. It sounds alot alike the p2 to serial driver just placed in our CVS. You can access our CVS by doing cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/linuxconsole login cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/linuxconsole co ruby The driver is in ruby/linux/drivers/input as ps2serkbd.c. I'm beginning the process of writing a driver for the Qoder keyboard-fob barcode scanner made by InterMec. It communicates with the host computer using the PS/2 port by way of a dock that sits in between the keyboard and the computer. One of them is turn numlock light on, which I can do with an ioctl from userspace (as root, anyway), but also caps lock, num lock and carriage-return scancodes. EV_LED The CueCat driver written by Pierre Coupard also modifies the keyboard driver. It would be nice if it was possible to load modules that hook into keyboard processing without requiring a kernel patch. And perhaps there is, but I haven't run across it yet. input api :-) - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: keyboard hook?
Input API looks nice. For now, I'll write a patch against pc_keyb.c to add a hook for my qoder stuff, and a loadable module for the meat of the driver. Okay. Then I'll port up to the input API. Just send me the code and I will place it into CVS. I have a Sparc here; does it have drivers you wish to have ported? Alot of work has to be done their :-/ If you are up to it I would be happy to work with you. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: keyboard hook?
Hi! Your best bet for a kernel driver is to use the linux input api like the usb keyboard do. The drivers are pretty simple to write and since all the keyboard drivers will be port over to this api it will save a lot of work done the road. If you need help let me know. I will be glad to help. It sounds alot alike the p2 to serial driver just placed in our CVS. You can access our CVS by doing cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/linuxconsole login cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/linuxconsole co ruby The driver is in ruby/linux/drivers/input as ps2serkbd.c. > I'm beginning the process of writing a driver for the "Qoder" > keyboard-fob barcode scanner made by InterMec. It communicates with the > host computer using the PS/2 port by way of a "dock" that sits in > between the keyboard and the computer. > One of them is "turn > numlock light on," which I can do with an ioctl from userspace (as root, > anyway), but also caps lock, num lock and carriage-return scancodes. EV_LED > The CueCat driver written by Pierre Coupard also modifies the keyboard > driver. It would be nice if it was possible to load modules that hook > into keyboard processing without requiring a kernel patch. And perhaps > there is, but I haven't run across it yet. input api :-) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: keyboard hook?
Hi! Your best bet for a kernel driver is to use the linux input api like the usb keyboard do. The drivers are pretty simple to write and since all the keyboard drivers will be port over to this api it will save a lot of work done the road. If you need help let me know. I will be glad to help. It sounds alot alike the p2 to serial driver just placed in our CVS. You can access our CVS by doing cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/linuxconsole login cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/linuxconsole co ruby The driver is in ruby/linux/drivers/input as ps2serkbd.c. I'm beginning the process of writing a driver for the Qoder keyboard-fob barcode scanner made by InterMec. It communicates with the host computer using the PS/2 port by way of a dock that sits in between the keyboard and the computer. One of them is turn numlock light on, which I can do with an ioctl from userspace (as root, anyway), but also caps lock, num lock and carriage-return scancodes. EV_LED The CueCat driver written by Pierre Coupard also modifies the keyboard driver. It would be nice if it was possible to load modules that hook into keyboard processing without requiring a kernel patch. And perhaps there is, but I haven't run across it yet. input api :-) - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
