public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Possible Bug: 2.4.14 USB Keyboard
Date: Thu, 15 Nov 2001 20:47:31 +0100	[thread overview]
Message-ID: <20011115204731.A8721@suse.cz> (raw)
In-Reply-To: <3BF2DFBF.6090502@prairiegroup.com> <20011114145312.A6925@kroah.com> <3BF3D029.7070609@prairiegroup.com> <20011115090023.A10511@kroah.com> <3BF40C03.4010509@prairiegroup.com> <mailman.1005850740.5583.linux-kernel2news@redhat.com> <200111151930.fAFJUCq16060@devserv.devel.redhat.com>
In-Reply-To: <200111151930.fAFJUCq16060@devserv.devel.redhat.com>; from zaitcev@redhat.com on Thu, Nov 15, 2001 at 02:30:12PM -0500

On Thu, Nov 15, 2001 at 02:30:12PM -0500, Pete Zaitcev wrote:
> > Do you have the keybdev module loaded? Also, don't load the usbkbd
> > module, if you load hid ...
> > 
> > -- 
> > Vojtech Pavlik
> > SuSE Labs
> 
> There is a small problem with this approach: users have no clue
> how to control what modules are loaded, hotplug loads whatever
> was built (and recorded in modules.usbmap), and some users
> have keyboards that plainly refuse to work with hid, therefore
> vendors have to build both modules.
> 
> See this little gem, for instance:
>  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=55878
> 
> I suspect some distributions can get away with "load the right
> module" approach because their userbase is so small and technical
> that they do not hit these cases often. I think something needs
> fixing in hid.

Interesting. Could you by any chance try to run the 'evtest' program (i
can send it to you if you don't have it handy) on the /dev/input/event
device created for this keyboard? And/or dmesg with DEBUG enabled in
hid-core.c? Also, latest kernels should make even the extra keys of this
keyboard work ...

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2001-11-15 19:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-14 21:18 Possible Bug: 2.4.14 USB Keyboard Martin McWhorter
2001-11-14 22:53 ` Greg KH
2001-11-15 14:24   ` Martin McWhorter
2001-11-15 17:00     ` Greg KH
2001-11-15 18:40       ` Martin McWhorter
2001-11-15 18:55         ` Vojtech Pavlik
     [not found]         ` <mailman.1005850740.5583.linux-kernel2news@redhat.com>
2001-11-15 19:30           ` Pete Zaitcev
2001-11-15 19:47             ` Vojtech Pavlik [this message]
     [not found]   ` <mailman.1005834780.32418.linux-kernel2news@redhat.com>
     [not found]     ` <200111151807.fAFI7XN30496@devserv.devel.redhat.com>
2001-11-15 18:44       ` Martin McWhorter
2001-11-15 19:14         ` Pete Zaitcev
2001-11-15 19:57           ` Martin McWhorter
     [not found]             ` <20011115152432.A26630@devserv.devel.redhat.com>
2001-11-15 21:30               ` Martin McWhorter
     [not found]                 ` <20011115170148.A19715@devserv.devel.redhat.com>
     [not found]                   ` <3BF43E55.80401@prairiegroup.com>
     [not found]                     ` <20011115171751.A22915@devserv.devel.redhat.com>
2001-11-15 22:40                       ` Martin McWhorter
2001-11-16  0:03                         ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20011115204731.A8721@suse.cz \
    --to=vojtech@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zaitcev@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox