From: Alexander Holler <holler@ahsoftware.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] hid2hci and Logitech Hub
Date: Fri, 26 Dec 2003 03:02:00 +0100 [thread overview]
Message-ID: <19230000.1072404120@[192.168.207.2]> (raw)
In-Reply-To: <1072369721.2876.90.camel@pegasus>
Hi Marcel,
--On Donnerstag, Dezember 25, 2003 17:28:42 +0100 Marcel Holtmann
<marcel@holtmann.org> wrote:
> make sure that you always post also the answers to the mailing list ;)
I though that's nothing from interrest for the mailing list. ;)
>> > Logitech uses some specific HID reports to switch the device from HID
>> > to HCI mode. They use the report ID 16 for that and we also must send
>> > the same reports through hiddev interface of the USB HID driver, but
>> > by now I haven't figured out how to do it the right way.
>
> I think it will be this one
>
> 0x10, 0xff, 0x81, 0x80, 0x00, 0x00, 0x00
>
> The 0x10 is the report ID.
As the report info for 0x10 shows 1 field and the maxusage from that field
is 1, it seems there is no way sending 6 bytes (usages?) with one report
0x10 using hiddev (if I have understood that part of hiddev correct ;) ).
I've tried sending 6 reports (0x10) with the values 0xff ... 0x00. That
hasn't worked (allways remember, I've just started collecting some
knowledge of usb, bluetooth and hid ;) ).
>> PS: 2.6 and the patch for 2.6 still oops when I disable the
>> bluetooth-device of my nb. Commenting out release of the isoc_iface
>> (which is still done automacally) helps. I will write these days a
>> report to the usb-helpline.
>
> For now simply compile your kernel without USB SCO support. I still
> haven't found the time to look deeper into it.
Just remove or comment out the release of the isoc_iface. The release isn't
needed and that avoids the oops. ;)
> That is not really hard to achieve. I already reverse engineered most of
> the protocol they use on report ID 16 and 17, but I don't found the time
> to write it up.
Nice to hear. I will ask you after I got the hub working as hci. ;)
Regards,
Alexander
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2003-12-26 2:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-25 12:48 [Bluez-devel] hid2hci and Logitech Hub Alexander Holler
2003-12-25 14:37 ` Marcel Holtmann
[not found] ` <30700000.1072366993@[192.168.207.2]>
2003-12-25 16:28 ` Marcel Holtmann
2003-12-26 2:02 ` Alexander Holler [this message]
2003-12-26 2:44 ` Marcel Holtmann
2003-12-26 4:26 ` Alexander Holler
2003-12-26 15:06 ` Marcel Holtmann
2003-12-26 16:49 ` Alexander Holler
2003-12-26 19:15 ` 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='19230000.1072404120@[192.168.207.2]' \
--to=holler@ahsoftware.de \
--cc=bluez-devel@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