The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Ralph Corderoy <ralph@inputplus.co.uk>
Cc: Anton Altaparmakov <aia21@cantab.net>,
	Pete Zaitcev <zaitcev@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Happy Hacking Keyboard Lite Mk 2 USB Problems with 2.4.18.
Date: Wed, 3 Jul 2002 02:06:07 +0200	[thread overview]
Message-ID: <20020703020607.A7689@ucw.cz> (raw)
In-Reply-To: <200207011746.g61Hkxf27019@blake.inputplus.co.uk>; from ralph@inputplus.co.uk on Mon, Jul 01, 2002 at 06:46:58PM +0100

On Mon, Jul 01, 2002 at 06:46:58PM +0100, Ralph Corderoy wrote:
> 
> Hi Anton,
> 
> > > What I'd like to see, if both hid.o and usbkbd.o can handle a
> > > keyboard, is that hid.o gets the job.  Then usbkbd.o can stay in
> > > config.in and be built just in case it's needed.
> > 
> > usbkbd.o is never needed when hid.o is present unless I have
> > misunderstood something.
> 
> Ah, I thought that in the same way the BIOS might not support the HID
> interface and so can use the simpler Boot interface, a keyboard might
> not implement the HID interface and just implement the simpler Boot one.
> Apologies if this isn't the case.  I agree that hid.o should be able to
> cope with everything then.

No, this is not the case. Even if the device implements only one mode
and that mode is HIDBP compatible, it's still also HID compatible,
because HIDBP is a subset of HID.

> > > Ah, OK, thanks.  Unfortunately, I've already moved onto 2.4.18 built
> > > from source due to some of my other needs.
> > 
> > In that case just reconfigure your kernel not to include usbkbd and
> > use hid instead, recompile, and be happy.
> 
> Yes, that's what I've done, and I'm happy, but still wish to persue the
> problem in order that usbkbd.o gets fixed.  Otherwise, someone else will
> spend their weekend learning about usbkbd.c, HID, Boot, etc.  :-)

usbkbd.c will get fixed. No worries.

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2002-07-03  0:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1025521441.28343.linux-kernel2news@redhat.com>
2002-07-01 15:16 ` Happy Hacking Keyboard Lite Mk 2 USB Problems with 2.4.18 Pete Zaitcev
2002-07-01 16:24   ` Hubert Mantel
2002-07-01 16:47   ` Ralph Corderoy
2002-07-01 17:25     ` Pete Zaitcev
2002-07-01 17:26     ` Anton Altaparmakov
2002-07-01 17:46       ` Ralph Corderoy
2002-07-03  0:06         ` Vojtech Pavlik [this message]
2002-07-02  4:16     ` Brad Hards
2002-07-02  4:26       ` Pete Zaitcev
2002-07-02  4:45         ` Brad Hards
     [not found] <mailman.1025526604.30310.linux-kernel2news@redhat.com>
2002-07-01 15:18 ` Pete Zaitcev
2002-07-01 11:02 Ralph Corderoy
2002-07-01 11:24 ` Brad Hards
2002-07-01 12:29   ` Ralph Corderoy
2002-07-01 17:19 ` Anton Altaparmakov

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=20020703020607.A7689@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=aia21@cantab.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ralph@inputplus.co.uk \
    --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