From: Vesa Halttunen <vesuri@jormas.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Keyboard & mouse operate in boot protocol mode causing extra keyboard events with 2.6.10-mh1 and bluez-libs/utils 2.13
Date: Fri, 07 Jan 2005 00:09:21 +0200 [thread overview]
Message-ID: <1105049361.6048.9.camel@pc.vesuri.net> (raw)
Hello,
a couple of months back I had a problem with extraneous keyboard events;
when I typed "sources" I got "sourceces" and so on. This was fixed by
applying an -mh kernel patch that had HID report protocol mode support.
2.6.9-mh3 and bluez-libs/utils 2.10 worked fine but now I upgraded to
2.6.10-mh1 and bluez-libs/utils 2.13 and this problem is back again.
hidd --list gives me
00:07:61:19:9E:A9 HID Boot Device [046d:b301] connected [boot-protocol]
00:07:61:19:FA:68 HID Boot Device [046d:b001] connected [boot-protocol]
so it seems it's not using the HID report protocol but the boot
protocol. hidd --list also used to show the correct names of the devices
(Logitech MX900 Mouse etc.) instead of just HID Boot Device.
What can I do to make hidd use the HID report protocol mode (or whatever
is necessary to fix this problem)?
Thanks,
-Vesa
--
-------------------------------------------------------
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 reply other threads:[~2005-01-06 22:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 22:09 Vesa Halttunen [this message]
2005-01-06 22:29 ` [Bluez-users] Keyboard & mouse operate in boot protocol mode causing extra keyboard events with 2.6.10-mh1 and bluez-libs/utils 2.13 Marcel Holtmann
2005-01-06 22:45 ` [Bluez-users] [Bluez-users]OBEX application blookk -
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=1105049361.6048.9.camel@pc.vesuri.net \
--to=vesuri@jormas.com \
--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