public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Raul Miller <moth@magenta.com>
Cc: Vojtech Pavlik <vojtech@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: user problem with usb duo mouse and keyboard
Date: Mon, 22 Dec 2003 01:10:39 +0100	[thread overview]
Message-ID: <20031222001039.GA16419@ucw.cz> (raw)
In-Reply-To: <20031221182757.F28449@links.magenta.com>

On Sun, Dec 21, 2003 at 06:27:57PM -0500, Raul Miller wrote:

> On Mon, Dec 22, 2003 at 12:00:42AM +0100, Vojtech Pavlik wrote:
> > hid-core.c includes hid.h, which in turn, if DEBUG is defined, includes
> > hid-debug.h. That last file defines some functions (hid_dump_input,
> > hid_dump_device), which are called by hid-core.c.
> ...
> > This is the problem! Don't ever use usbkbd and usbmouse. Use hid
> > instead.
> 
> Oh!
> 
> And, looking at the docs on those modules, I see nice big warnings that
> say something similar...
> 
> Looking further, these modules where build and installed by default
> when I installed my system (debian, with the 2.4.18-bf2.4 kernel), and
> I've been carrying forward that configuration on my hand-built kernels,
> and never realized I needed to get rid of those modules.
> 
> I see the hid-debug messages in syslog now, but the keyboard and mouse
> are working properly as well.  Do you want to pursue this any further?
> [If so, I can send you the messages.]

If they are working, then no.

> [It's perhaps of note that the extra keys on the keyboard are reported
> as scancode 0 by showkey (with other release scan codes) when plugged

This is normal. This is because the keycodes are above 128 and that's
all that you can fit into a single signed byte.

> in via usb and which have different keypress scan codss when plugged as
> a ps/2 keyboard.]

This is also normal and can be fixed via the setkeycodes utility. The
driver cannot be preconfigured for every PS/2 keyboard out there,
because their scancodes conflict. On USB the configuration is static,
because USB carries much more information about the keys.

> [[There's a slight chance that [to avoid confused messages from other
> people in my situation] a warning message from hid about usbkbd and
> usbmouse would be a good idea.]]

Maybe. But fortunately current distros get it right.

> Thank you very much.
> Sorry about the confusion,

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

      reply	other threads:[~2003-12-22  0:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-21 20:43 problem with usb duo mouse and keyboard Raul Miller
2003-12-21 21:39 ` Vojtech Pavlik
2003-12-21 22:03   ` Raul Miller
     [not found]     ` <20031221223443.GA15744@ucw.cz>
     [not found]       ` <20031221175121.E28449@links.magenta.com>
     [not found]         ` <20031221230042.GA15960@ucw.cz>
2003-12-21 23:27           ` user " Raul Miller
2003-12-22  0:10             ` Vojtech Pavlik [this message]

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=20031222001039.GA16419@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=moth@magenta.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