From: Nils Faerber <nils.faerber@kernelconcepts.de>
To: Herr Philip Blundell <pb@nexus.co.uk>
Cc: Marcel Holtmann <marcel@holtmann.org>,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>,
Vojtech Pavlik <vojtech@suse.cz>,
Greg Kroah-Hartman <greg@kroah.com>
Subject: Re: [Bluez-devel] Renaming USB HID driver
Date: Thu, 25 Mar 2004 15:45:46 +0100 [thread overview]
Message-ID: <1080225946.7098.120.camel@localhost> (raw)
In-Reply-To: <1080142065.2648.39.camel@mill.nexus.co.uk>
Am Mi, den 24.03.2004 schrieb Philip Blundell um 16:27:
> On Tue, 2004-03-23 at 10:22, Nils Faerber wrote:
> > 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 :(
> I don't think this would actually help much for those keyboards. As far
> as I know, none of the common PDA keyboards speak HID; they all use some
> custom serial protocol for event reporting. You can avoid the gruesome
> handle_scancode() stuff by injecting EV_KEY events into the input stack,
> either via input_report_key() within the kernel, or via uinput from
> user-space.
Ah, yes indeed, that make more sense.
So pls ignore my post ;)
I was about almost about to start digging through HID parsing and
thinking about emulating it...
> p.
CU
nils faerber
--
kernel concepts Tel: +49-271-771091-12
Dreisbachstr. 24 Fax: +49-271-771091-19
D-57250 Netphen D1 : +49-170-2729106
--
next prev parent reply other threads:[~2004-03-25 14:45 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
2004-03-24 15:27 ` Philip Blundell
2004-03-25 14:45 ` Nils Faerber [this message]
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=1080225946.7098.120.camel@localhost \
--to=nils.faerber@kernelconcepts.de \
--cc=bluez-devel@lists.sourceforge.net \
--cc=greg@kroah.com \
--cc=marcel@holtmann.org \
--cc=pb@nexus.co.uk \
--cc=vojtech@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.