From: bluez.mexon@spamgourmet.com
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] hid2hci fails: broken pipe
Date: Thu, 22 Feb 2007 06:47:10 +0100 [thread overview]
Message-ID: <45DD2E5E.1060703@yahoo.com.au> (raw)
In-Reply-To: <1172060009.7403.17.camel@violet>
Marcel Holtmann - marcel@holtmann.org wrote:
> then something is broken here. Can't tell your what, but it should work.
I tried booting Knoppix and running lsusb, and it also claimed that the
dongle was in "HCI mode". Since that version of Knoppix predates
hid2hci, I think I can assume that this dongle is not booting in HID
mode as I thought it would.
Is it likely that either this particular chip doesn't support HID proxy
despite being bluecore 4, or that it has some pin wired hard to ground
to disable this feature?
>> First, is there any way I can tell, really and for sure, whether the
>> dongle is in HCI or HID mode?
>
> Look at lsusb. In case of CSR chips this is 100% sure.
So you're saying that if it prints "Cambridge Silicon Radio, Ltd
Bluetooth Dongle (HCI mode)" it's in HCI mode, and presumably (although
I've never seen it) if it switched correctly it would print "Cambridge
Silicon Radio, Ltd Bluetooth Dongle (HID mode)". I'd like to see what
the actual output of lsusb looks like when it's correctly in HID proxy mode.
>> Second, I'm a little confused about how this "HID proxy" thing works
>> anyway. How does the dongle remember which mouse and keyboard it's
>> paired with after the power is switched off? Does it have a little bit
>> of flash on board that remembers the last paired device or something?
>> Or have I completely misunderstood what this feature is for?
>
> That is the magic in the dongle HID software. It parses HID devices in
> the background when it is in HCI mode.
Yeah, that bit I get. But it must also know which devices to connect
to, and assuming it's using an encrypted link, it also needs a key.
That has to be stored somewhere so it persists when the thing is powered
down. Does that mean it's got an extra little bit of flash hidden
inside the bluecore somewhere? Or does it use the external flash chip?
That matters, because it would imply that only bluecore chips with
external storage would work in HID proxy mode.
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2007-02-22 5:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 17:39 [Bluez-devel] hid2hci fails: broken pipe bluez.mexon
2007-02-19 17:54 ` Marcel Holtmann
2007-02-19 19:26 ` bluez.mexon
2007-02-21 12:13 ` Marcel Holtmann
2007-02-22 5:47 ` bluez.mexon [this message]
2007-02-22 6:52 ` Marcel Holtmann
2007-02-23 6:10 ` bluez.mexon
2007-02-23 7:07 ` Marcel Holtmann
2007-02-23 12:04 ` bluez.mexon
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=45DD2E5E.1060703@yahoo.com.au \
--to=bluez.mexon@spamgourmet.com \
--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