From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] HID report mode protocol support in 2.6.11-mh1 broken/missing?
Date: Mon, 14 Mar 2005 11:28:10 +0100 [thread overview]
Message-ID: <1110796090.8158.56.camel@pegasus> (raw)
In-Reply-To: <1110498275.3040.6.camel@pc.vesuri.net>
Hi Vesa,
> I upgraded my kernel from 2.6.10-mh2 to 2.6.11-mh1 and now my mouse and
> keyboard operate in boot protocol mode again so the special keys don't
> work. Does 2.6.11-mh1 lack full support for the report mode protocol, is
> it broken or has something else changed I'd have to know about? I'm
> using bluez-libs and -utils 2.15. The keyboard is a Logitech Elite
> keyboard and the mouse is Logitech MX900.
maybe I made a mistake when porting the report mode to 2.6.11. Last time
I checked it, it worked for me.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-03-14 10:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 23:44 [Bluez-users] HID report mode protocol support in 2.6.11-mh1 broken/missing? Vesa Halttunen
2005-03-14 10:28 ` Marcel Holtmann [this message]
2005-03-14 12:44 ` Florian Evers
2005-03-14 12:55 ` Marcel Holtmann
2005-03-14 13:04 ` Florian Evers
2005-03-14 13:06 ` Marcel Holtmann
2005-03-14 18:50 ` Marcel Holtmann
2005-03-14 19:42 ` Vesa Halttunen
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=1110796090.8158.56.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