linuxconsole-dev

New Input PS/2 driver

[James S. <jsi...@tr...>]

Okay. It is not that new since I have been using it for several months now
with now problems. I just ported from console project CVS to 2.4.10.
Basically this patch address the issues people have been having with the
current PS/2 driver. Plus it has the bonus of using the universal input
api. It even allows for unpluging the keyboard with no problem and you can
have two keybaord plugged in at the same time with no problems. NOTE:
don't have both keyboard plugged in at boot time. It confusses them. 
The olnly thing which I haven't had time to do is support PS/2 based
keybards that don't use the standard IRQ and port ranges. Several mips
devices have this issue. The patch is 60 K so I posted a link. To use the 
keyboard driver you need to 

1) enable the input core and keyboard support in the input menu. 

2) In the character menu select PS/2 port support and i8042 aux+kbd
   controller. Their are hooks for other types of PS/2 "clones" on other
   platforms.

3) You have 3 different devices to select from. I don't think I have to
   explain them.

   XT keyboard.
   AT and PS/2 keyboards
   PS/2 mouse
   
Here is the diff.

http://www.transvirtual.com/~jsimmons/input-ps2.diff

P.S
  For assumment I have a funny movie clip in the same area(dancemonkeyboy.mpeg).

Re: New Input PS/2 driver

[Arndt S. <ab...@sr...>]

On Mon, Oct 01, 2001 at 09:47:53PM -0700, James Simmons wrote:
> [... Announcement of his new PS/2 input driver ...]
> http://www.transvirtual.com/~jsimmons/input-ps2.diff

Great! Does it, by chance, include the ability for bidirectional
communication with a PS/2 device from a user space program?

I want to write a keymap download program for Handykey's Twiddler2
(a chording keyboard connected to the PS/2 keyboard and mouse ports,
see http://www.handykey.com), for which this would be very handy.

Thank you,
Arndt

-- 
Arndt Schoenewald <ab...@sr...>

Re: New Input PS/2 driver

[James S. <jsi...@tr...>]

> On Mon, Oct 01, 2001 at 09:47:53PM -0700, James Simmons wrote:
> > [... Announcement of his new PS/2 input driver ...]
> > http://www.transvirtual.com/~jsimmons/input-ps2.diff
> 
> Great! Does it, by chance, include the ability for bidirectional
> communication with a PS/2 device from a user space program?

Not yet. Their are ioctl calls  EVIOCSKEYCODE and EVIOCGKEYCODE but they
have never been implemented. It would be pretty easy to implement. I just
have to add something to input.c.

> I want to write a keymap download program for Handykey's Twiddler2
> (a chording keyboard connected to the PS/2 keyboard and mouse ports,
> see http://www.handykey.com), for which this would be very handy.

Take a look at input.h with the above ioctl values.

Re: New Input PS/2 driver

[Allan S. J. <sno...@on...>]

On Tuesday 02 October 2001 06:47, James Simmons wrote:
> Okay. It is not that new since I have been using it for several months now
> with now problems. I just ported from console project CVS to 2.4.10.
> Basically this patch address the issues people have been having with the
> current PS/2 driver. Plus it has the bonus of using the universal input
> api. It even allows for unpluging the keyboard with no problem and you can
> have two keybaord plugged in at the same time with no problems.

Nice, I've just tested it and it works mostly, at least more than ruby. 
Theres still problems with multiple keys. Holding shift and any of the 
insert/delete/home/end/page up/page down keys, results in two warnings:
unknown key(set 2, scancode 0x159 on input/0 ) pressed and released

Also when rebooting the input-kernel the BIOS reported keyboard error and I 
had to do a full power-off.

But I didnt see any off the autorepeat problems from ruby.

This is becoming a pretty good alternative, if we can keep up a functional 
patch against 2.4 until 2.5.

Regards.
`Allan

Re: New Input PS/2 driver

[James S. <jsi...@tr...>]

> Nice, I've just tested it and it works mostly, at least more than ruby. 
> Theres still problems with multiple keys. Holding shift and any of the 
> insert/delete/home/end/page up/page down keys, results in two warnings:
> unknown key(set 2, scancode 0x159 on input/0 ) pressed and released

Hm. Your keyboard generates a unquie scancode when pressing those key
combo that is lacking in the scancode to event table. I wonder what we
should label those scancodes. 
 
> Also when rebooting the input-kernel the BIOS reported keyboard error and I 
> had to do a full power-off.

I have this problem when I have 2 PS/2 keyboards plugged in. The input
driver doesn't depend on the firmware so it programs the i8042 chipset
itself. At reboot it in theory should reset itself to a sane state. This
is done by the i8042_controller_cleanup which is setup by 
register_reboot_notifier. This means it is not being called by the
notifier chain. Do you have this issue only when hitting alt-ctrl-delete?
 
> But I didnt see any off the autorepeat problems from ruby.

That is my fail. I changed some of the console code to use the input api
to reset the auto repeat rate. This is a bug in that code somewhere I have
to fix.

> This is becoming a pretty good alternative, if we can keep up a functional 
> patch against 2.4 until 2.5.

No problem. I hope to get it into Alan's tree soon.