From: Marcel Holtmann <marcel@holtmann.org>
To: Peter Klausler <pmk@cray.com>
Cc: Edd Dumbill <edd@usefulinc.com>,
Peter Klausler <peter@klausler.com>,
Charles Bueche <charles@bueche.ch>,
BlueZ Developers List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Logitech MX900 mouse with Dell Inspiron 8600
Date: Tue, 02 Dec 2003 18:56:43 +0100 [thread overview]
Message-ID: <1070387803.18574.21.camel@pegasus> (raw)
In-Reply-To: <20031202114203.A31354@schnell.us.cray.com>
Hi Peter,
> > yes you sent it to list. It still resides in my Bluetooth mailbox and
> > it
> > is working fine. I think Marcelo will take my backport of the uinput
> > driver into 2.4.24 and so uinput should be the way to go, even if this
> > means that we have to implement our own HID parser in userspace.
>
> What's wrong with the HID parser in bthid today?
my problem is that it depends on static variables and I don't see any
method to create HID reports from input events that the kernel send to
us and we have to forward to the HID device. For exmaple the keyboard
leds.
I have rewritten my core HID layer which is now only one process with an
event loop. It handles all connection establishment and termination fine
without any problems or stalled ACL links. It also gets the vendor and
product ID's from the PNP information. Some minor things have to be
fixed first, but I think that I will commit it to CVS very soon. If this
code is available I hope we can work together on a full featured HID
parser implementation and I think we can use your current code as a
starting point.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2003-12-02 17:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-30 14:12 [Bluez-devel] Logitech MX900 mouse with Dell Inspiron 8600 Charles Bueche
2003-11-30 18:51 ` Charles Bueche
2003-12-01 15:38 ` Peter Klausler
2003-12-02 15:55 ` Edd Dumbill
2003-12-02 16:01 ` Edd Dumbill
2003-12-03 20:18 ` Charles Bueche
2003-12-03 20:35 ` Marcel Holtmann
2003-12-04 8:53 ` Olivier Bornet
2003-12-04 13:52 ` Marcel Holtmann
2003-12-04 13:57 ` Olivier Bornet
2003-12-04 14:10 ` Marcel Holtmann
2003-12-04 16:35 ` Olivier Bornet
2003-12-04 17:03 ` Marcel Holtmann
2003-12-09 20:31 ` Charles Bueche
2003-12-09 22:42 ` Olivier Bornet
2003-12-10 8:12 ` Charles Bueche
2003-12-10 8:30 ` Olivier Bornet
2003-12-13 15:56 ` Charles Bueche
2003-12-13 16:39 ` Marcel Holtmann
2003-12-13 18:51 ` Charles Bueche
2003-12-13 19:04 ` Marcel Holtmann
2003-12-14 13:55 ` Charles Bueche
2003-12-14 14:22 ` Marcel Holtmann
2003-12-14 20:01 ` Charles Bueche
2003-12-14 20:09 ` Marcel Holtmann
2003-12-10 1:41 ` Marcel Holtmann
2003-12-02 17:39 ` Marcel Holtmann
2003-12-02 17:42 ` Peter Klausler
2003-12-02 17:56 ` Marcel Holtmann [this message]
2003-12-03 10:10 ` Stephen Crane
2003-12-03 13:06 ` Marcel Holtmann
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=1070387803.18574.21.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=charles@bueche.ch \
--cc=edd@usefulinc.com \
--cc=peter@klausler.com \
--cc=pmk@cray.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 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.