From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Some general HID questions..
Date: Thu, 06 Jan 2005 13:28:20 +0100 [thread overview]
Message-ID: <1105014500.4299.25.camel@pegasus> (raw)
In-Reply-To: <Pine.LNX.4.61.0501061130420.17785@block.bubble>
Hi Florian,
> As it was recently discussed on this list, the newly released
> kernel 2.6.10 doesn't feature report mode support for BT HID devices
> any more, and neither do the -mh patches. I've just had a look at
> the vanilla sources, and they seem heavily stripped down compared
> to 2.6.9-mh1.
>
> Am I correct to assume that this happened because a universal HID
> parser (suitable for USB and Bluetooth and whatnot) will be introduced
> in the near future? If so, I'd like to know more about that and would
> consider helping, too. Could somebody give me some pointers where
> to start (e.g. who's developing the universal parser)?
you read the email where I explained that I will keep the revision
history by any costs? The input subsystem is no merged back and once I
get my x-mas and new years backlog done, I will start with it.
Regards
Marcel
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-01-06 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 11:05 [Bluez-users] Some general HID questions Florian Echtler
2005-01-06 12:28 ` Marcel Holtmann [this message]
2005-01-06 13:07 ` Florian Echtler
2005-01-06 13:11 ` 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=1105014500.4299.25.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
/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