From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hid2hci fails: broken pipe
Date: Fri, 23 Feb 2007 08:07:20 +0100 [thread overview]
Message-ID: <1172214440.28266.4.camel@violet> (raw)
In-Reply-To: <45DE8544.4010900@yahoo.com.au>
Hi,
> > wait a second. You don't even know if it is a HID proxy dongle. You
> > should run "hciconfig hci0 revision" as root. If this is a ROM version
> > then it is not HID proxy. And even if it is an External version, you
> > still need to have to correct unified firmware and the correct boot
> > parameter to make it come up in HID mode first.
> ...
> > You need a BlueCore External to have HID proxy support. The ROM versions
> > are all HCI only.
>
> Aw man, I tried. I really tried. Look here:
>
> http://sourceforge.net/mailarchive/forum.php?thread_id=31657125&forum_id=1883
>
> Didn't I try? Yes, I tried. And it didn't bloody help, did it?
>
> aeon:~# hciconfig hci0 revision
> hci0: Type: USB
> BD Address: XX:XX:XX:XX:XX:XX ACL MTU: 192:8 SCO MTU: 64:8
> HCI 18.2.1
> Chip version: BlueCore3-ROM
> Max key size: 128 bit
> SCO mapping: HCI
>
> There it is, in black and white. It's the ROM version. I guess a
> DN-3008M1 really is completely different to a DN-3008. That or New
> Zealand websites are evil and shouldn't be trusted.
>
> So OK, maybe you can tell me. I would like to buy a USB Bluetooth
> dongle that does the HID proxy thing, preferably 2.0, preferably class
> 1. Do you know where I might be able to buy such a thing?
don't ask me. It is kinda hard to find a BlueCore4-External dongle these
days. And I actually need some where you can flash new firmware into it.
If anyone find a reliable source of these, I would buy at least a
handful. The best ones _were_ the Level1 things, because they used a
high quality flash chip. However the new ones have ROM chips as well.
> And also: boot parameter? Do you mean a Linux boot parameter or another
> setting that goes on the flash of the dongle? Because if it's the
> former, that would invalidate the whole point of HID proxy, wouldn't it?
The CSR unified firmware has a boot parameter where you can tell it to
boot up in HID mode or HCI mode (and some other modes). In general every
unified firmware is HID proxy capable. You might simply have to switch
it on.
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
next prev parent reply other threads:[~2007-02-23 7:07 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
2007-02-22 6:52 ` Marcel Holtmann
2007-02-23 6:10 ` bluez.mexon
2007-02-23 7:07 ` Marcel Holtmann [this message]
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=1172214440.28266.4.camel@violet \
--to=marcel@holtmann.org \
--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