public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Echtler <echtler@fs.tum.de>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Some general HID questions..
Date: Thu, 6 Jan 2005 12:05:31 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.61.0501061130420.17785@block.bubble> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello everybody!

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)?

Thanks, yours, Florian
- -- 
Homo homini lupus.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFB3RuA7CzyshGvatgRAhyQAJ4zLUjzdDw/0KZoWa3dkKJt/E0nwwCdFfg3
m/UzE8fVdnsr7L4kgHkLsZI=
=tF5m
-----END PGP SIGNATURE-----


-------------------------------------------------------
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

             reply	other threads:[~2005-01-06 11:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-06 11:05 Florian Echtler [this message]
2005-01-06 12:28 ` [Bluez-users] Some general HID questions Marcel Holtmann
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=Pine.LNX.4.61.0501061130420.17785@block.bubble \
    --to=echtler@fs.tum.de \
    --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