From: Vojtech Pavlik <vojtech@suse.cz>
To: Nils Faerber <nils.faerber@kernelconcepts.de>
Cc: Marcel Holtmann <marcel@holtmann.org>,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>,
Greg Kroah-Hartman <greg@kroah.com>
Subject: Re: [Bluez-devel] Renaming USB HID driver
Date: Tue, 23 Mar 2004 11:30:15 +0100 [thread overview]
Message-ID: <20040323103015.GA395@ucw.cz> (raw)
In-Reply-To: <1080037332.7098.83.camel@localhost>
On Tue, Mar 23, 2004 at 11:22:13AM +0100, Nils Faerber wrote:
> Am Mo, den 22.03.2004 schrieb Marcel Holtmann um 14:54:
> > Hi Folks,
> Hello!
>
> > my plan is to move the HID parser out of the USB subsystem and provide a
> > general HID parser implementation under drivers/hid/ which could then be
> > used by the USB and the Bluetooth subsystem drivers. To avoid any naming
> > conflict due and after the development I suggest to rename the USB HID
> > module from hid.ko to usbhid.ko (see attached patch).
> [...]
> > Comments?
>
> Maybe as additional motivation for a better abstraction, like Marcel
> porposed, I would like to mention other keyboard devices on other Linux
> platforms that could benefit from this!
> For example I am currently working on Linux for PDAs. Some of them can
> be attached to external keyboards, mostly serial. Having a cleanly
> abstracted HID layer would make it possible to have those properly
> supported. Currently this is done by a pretty ugly hack calling
> handle_scancode() or similar :(
You seem to be talking 2.4? In 2.6 you have an abstract input layer,
where you call register_input_device() and then input_report_key() for
these kinds of devices. You definitely are not supposed to call
handle_scancode() directly.
We're talking about another HID separation, separating the parser for
HID descriptors, as defined in the USB HID specification.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2004-03-23 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-22 13:54 [Bluez-devel] Renaming USB HID driver Marcel Holtmann
2004-03-23 10:22 ` Nils Faerber
2004-03-23 10:30 ` Vojtech Pavlik [this message]
2004-03-24 15:27 ` Philip Blundell
2004-03-25 14:45 ` Nils Faerber
2004-03-29 8:47 ` dirk husemann
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=20040323103015.GA395@ucw.cz \
--to=vojtech@suse.cz \
--cc=bluez-devel@lists.sourceforge.net \
--cc=greg@kroah.com \
--cc=marcel@holtmann.org \
--cc=nils.faerber@kernelconcepts.de \
/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;
as well as URLs for NNTP newsgroup(s).