From: Marcel Holtmann <marcel@holtmann.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: bluez-devel@lists.sf.net
Subject: Re: [Bluez-devel] K600i and hidp
Date: Tue, 18 Jul 2006 12:40:54 +0200 [thread overview]
Message-ID: <1153219254.4639.2.camel@localhost> (raw)
In-Reply-To: <1153218888.2497.15.camel@johannes.berg>
Hi Johannes,
> When I recently tried the remote control feature on my K600i, I noticed
> that it wouldn't work because the phone doesn't advertise proper
> capabilities. I put into my notes:
>
> [...]
> Apparently the phone has a bug and doesn't describe its subclass
> properly, it seems to never send the bits 0x80 or 0x40 in it, while that
> is required. I had to patch the hidp_setup_input function in
> net/bluetooth/hidp/core.c (lines 546 and 562) to ignore the subclass
> bits.
> [...]
>
> Can we have some sort of device quirk table here to ignore the subclass
> bits for certain devices?
you can use "hidd --subclass=<val> ..." for this.
> (Oh and another question is -- how about moving all this into the
> userspace daemon and using uinput?)
The overall goal is to merge the USB HID driver with the Bluetooth HID
and this is one reason why it is inside the kernel. The other is that we
need good latency for HID.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
parent reply other threads:[~2006-07-18 10:40 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1153218888.2497.15.camel@johannes.berg>]
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=1153219254.4639.2.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sf.net \
--cc=bluez-devel@lists.sourceforge.net \
--cc=johannes@sipsolutions.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