From: bluez.mexon@spamgourmet.com
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] hid2hci fails: broken pipe
Date: Fri, 23 Feb 2007 13:04:10 +0100 [thread overview]
Message-ID: <45DED83A.2020701@yahoo.com.au> (raw)
In-Reply-To: <1172214440.28266.4.camel@violet>
Marcel Holtmann - marcel@holtmann.org wrote:
> 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.
OK, well, that sucks.
I wrote an email begging Level1 to re-introduce a Bluecore4-ext model,
and an email to CSR asking for a list of manufacturers who use
Bluecore4-ext in their USB dongles. I don't expect either to produce
any useful result, but hey, you've gotta speak to be heard. In the
meantime, I guess I'm sticking with wires.
Thanks for your help, that clarified a lot of things.
-------------------------------------------------------------------------
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
prev parent reply other threads:[~2007-02-23 12:04 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
2007-02-23 12:04 ` bluez.mexon [this message]
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=45DED83A.2020701@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