Date: Mon, 16 Jul 2007 21:09:43 +1200 From: Sam Banks <w0lfie@clear.net.nz> To: current@FreeBSD.org Subject: Re: ukbd patch advice Message-ID: <469b35d7.197.31f0.5575@clear.net.nz>
next in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format. ---=_fep17469b35d7 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit As suggested by Andrew Thompson, I have attached the patch for ukbd.c to show the changes I've made. Sam. ----- Original Message Follows ----- > Hey all, > > I have been having a problem with my particular usb > keyboard (0x03 was always being written into the first > element of ukbd_data->keycode basically). I have tracked > it down to a problem somewhere in between the uhci chipset > (same problem with other cuts of uhci chipset), the uhci > and/or ukbd drivers and the keyboard. > > A fix to the problem is to reorder members of the struct > ukbd_data. Originally, the members are ordered as > modifiers, reserved and keycode[6] (minus a bunch of > #define's). If I change this order to reserved, modifiers > and keycode[6], my keyboard starts to function as it > should (minus lighting up the LED's but that's another > email all together :)). With this reordering, it stops > other usb keyboards which function with the original code > from working. > > I'm wanting submit a patch for this fix (as other people > are experiencing the same problems) but I'm not sure how > to do this. I was thinking along the lines of the usb > quirks function but it appears outside of a function body, > you cannot have the normal if() type statements, only the > preprocessor #ifdef types. To me, having a kernel config > option for a single keyboard on a single driver seems > quite overkill. > > Does anyone have any suggestions on what I should do or > can anyone point me to some code that deals with a similar > problem? > > On a side note, is anyone able to shed any light into why > they think the above fix works? I am drawing a bit of a > blank to be honest. Is it possible that my fix is only > masking the problem? > > If you need any more info or whatever, yell out. > > Cheers, > > Sam. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" ---=_fep17469b35d7 Content-Type: application/octet-stream; name="ukdb.c.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="ukdb.c.patch" LS0tIHVrYmQuYy5vcmlnCTIwMDctMDctMTYgMjA6NTk6MzQuMDAwMDAwMDAw ICsxMjAwCisrKyB1a2JkLmMJMjAwNy0wNy0xNiAyMTowMjozNy4wMDAwMDAw MDAgKzEyMDAKIC8qCiAgKiBISUQgc3BlYzogaHR0cDovL3d3dy51c2Iub3Jn L2RldmVsb3BlcnMvZGV2Y2xhc3NfZG9jcy9ISUQxXzExLnBkZgpAQCAtOTMs NiArOTMsNyBAQAogI2RlZmluZSBOS0VZQ09ERSA2CiAKIHN0cnVjdCB1a2Jk X2RhdGEgeworICAgIHVfaW50OF90ICAgIHJlc2VydmVkOwogCXVfaW50OF90 CW1vZGlmaWVyczsKICNkZWZpbmUgTU9EX0NPTlRST0xfTAkweDAxCiAjZGVm aW5lIE1PRF9DT05UUk9MX1IJMHgxMApAQCAtMTAyLDcgKzEwMyw2IEBACiAj ZGVmaW5lIE1PRF9BTFRfUgkweDQwCiAjZGVmaW5lIE1PRF9XSU5fTAkweDA4 CiAjZGVmaW5lIE1PRF9XSU5fUgkweDgwCi0JdV9pbnQ4X3QJcmVzZXJ2ZWQ7 CiAJdV9pbnQ4X3QJa2V5Y29kZVtOS0VZQ09ERV07CiB9Owo= ---=_fep17469b35d7--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?469b35d7.197.31f0.5575>