Re: Problem with keyboard generating events persists in 2.6.7

[Aivils <ai...@un...>]

On Monday 05 July 2004 20:42, Kjetil Kjernsmo wrote:
> On mandag 5. juli 2004, 19:27, Helge Hafting wrote:
> > How do you get ruby out of cvs these days?
>=20
> Hm, it worked fine for me just a few days ago... No idea.
>=20
> > Perhaps a USB driver p=EF=BF=BDroblem?
>=20
> It could be. I contacted Greg Kroah-Hartmann like Zoltan suggested, no=20
> response yet.
>=20
> > What's inferior about using keyboards on ps/2? That's what I use,
> > and serial mice.  That way I didn't have to buy any new keyboard.
>=20
> Oh, it is just the availability of suitable extension cables... Now the=20
> place is a mess with cables all over, some of them is a bit short, but=20
> I have this very nice 5m cable with VGA+2xPS/2-in-one, and I'd like to=20
> use that. It would be so much more maintainable. Especially when you=20
> want to clean out the corners. I did that the other day. Whoah! :-)=20

IMHO You should do gross hack by yourself

=2D-- hid-core.c  2004-06-17 10:37:47.000000000 +0300
+++ hid-core_.c 2004-07-09 11:12:43.045096352 +0300
@@ -1491,7 +1491,7 @@ static struct hid_blacklist {
        { USB_VENDOR_ID_ATEN, USB_DEVICE_ID_ATEN_2PORTKVM, HID_QUIRK_NOGET =
},
        { USB_VENDOR_ID_ATEN, USB_DEVICE_ID_ATEN_4PORTKVM, HID_QUIRK_NOGET =
},
        { USB_VENDOR_ID_ATEN, USB_DEVICE_ID_ATEN_4PORTKVMC, HID_QUIRK_NOGET=
 },
=2D       { USB_VENDOR_ID_TANGTOP, USB_DEVICE_ID_TANGTOP_USBPS2, HID_QUIRK_=
NOGET },
+       { USB_VENDOR_ID_TANGTOP, USB_DEVICE_ID_TANGTOP_USBPS2, HID_QUIRK_NO=
GET | HID_QUIRK_STOP_TANGTOP},

        { USB_VENDOR_ID_A4TECH, USB_DEVICE_ID_A4TECH_WCP32PU, HID_QUIRK_2WH=
EEL_MOUSE_HACK_BACK },
        { USB_VENDOR_ID_CYPRESS, USB_DEVICE_ID_CYPRESS_MOUSE, HID_QUIRK_2WH=
EEL_MOUSE_HACK_EXTRA },






=2D-- hid-input.c 2004-05-10 05:32:28.000000000 +0300
+++ hid-input_.c        2004-07-09 11:23:21.278070192 +0300
@@ -432,6 +432,13 @@ void hidinput_hid_event(struct hid_devic

        input_regs(input, regs);

+       /* debug wrong TANGTOP event */
+       printk("HID_EVENT: type %d code %d \n", usage->type, usage->code);
+       /* stop wrong event */
+       if ((hid->quirks & HID_QUIRK_STOP_TANGTOP) &&
+            usage->type =3D=3D UNDESIRED_TYPE && usage->code =3D=3D UNDESI=
RED_CODE)
+               return;
+
        if (((hid->quirks & HID_QUIRK_2WHEEL_MOUSE_HACK_EXTRA) && (usage->c=
ode =3D=3D BTN_EXTRA))
                || ((hid->quirks & HID_QUIRK_2WHEEL_MOUSE_HACK_BACK) && (us=
age->code =3D=3D BTN_BACK))) {
                if (value)



=2D-- hid.h       2004-05-10 05:31:57.000000000 +0300
+++ hid_.h      2004-07-09 11:11:41.563442984 +0300
@@ -211,6 +211,7 @@ struct hid_item {
 #define HID_QUIRK_2WHEEL_MOUSE_HACK_BACK       0x080
 #define HID_QUIRK_2WHEEL_MOUSE_HACK_EXTRA      0x100
 #define HID_QUIRK_2WHEEL_MOUSE_HACK_ON         0x200
+#define HID_QUIRK_STOP_TANGTOP                 0x400

 /*
  * This is the global environment of the parser. This information is




This set of paches means You locate wrong event and leater stop it with
# define UNDESIRED_TYPE=20
# define UNDESIRED_CODE


Aivils