From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Marcel Holtmann <marcel@holtmann.org>,
BlueZ mailing list <bluez-devel@lists.sourceforge.net>,
Steven Singer <steven.singer@csr.com>
Subject: CSR firmware question...
Date: Thu, 12 Aug 2004 17:25:14 -0700 [thread overview]
Message-ID: <20040813002514.GA21388@bougret.hpl.hp.com> (raw)
Hi guys,
A few questions regarding CSR firmware : what's a commonly
available BT USB dongle with a recent CSR firmware.
Long story :
I'm hitting various bugs with the CSR firmware in my D-Link
USB dongles (0x1bb), where I can easilly deadlock the dongle. My 3Com
dongle, which has a more recent firmware (0x20e), behave much better,
but not perfect.
D-Link doesn't provide a firmware updater, but, beeing
fearless, I tried to firmware upgrade a D-Link dongle and ended up
with a dead dongle (can't even put back the original firmware on it).
From the release notes, the latest CSR firmwares have zillions
of bug fixes. I really wonder how I can enjoy the bug fixes.
Thanks in advance...
Jean
P.S. : Marcel, do you have a version of btdfu that can write the
firmware image to the dongle ? Or some documentation ?
next reply other threads:[~2004-08-13 0:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-13 0:25 Jean Tourrilhes [this message]
2004-08-13 8:31 ` [Bluez-devel] Re: CSR firmware question Marcel Holtmann
2004-08-13 16:37 ` Jean Tourrilhes
2004-08-13 16:57 ` [Bluez-devel] " Marcel Holtmann
2004-08-13 22:34 ` Jean Tourrilhes
2004-08-13 23:35 ` [Bluez-devel] " Marcel Holtmann
2004-08-13 23:53 ` Jean Tourrilhes
2004-08-13 23:59 ` [Bluez-devel] " Marcel Holtmann
2004-08-13 17:02 ` David Woodhouse
2004-08-16 12:01 ` Roderick Taylor
2004-08-16 8:24 ` Marcel Holtmann
2004-08-13 10:49 ` [Bluez-devel] " Carl Orsborn
2004-08-13 18:07 ` Jean Tourrilhes
2004-08-14 10:38 ` Carl Orsborn
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=20040813002514.GA21388@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=jt@hpl.hp.com \
--cc=marcel@holtmann.org \
--cc=steven.singer@csr.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.