linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roderick Taylor <rtaylor@hcvwireless.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Jean Tourrilhes <jt@hpl.hp.com>,
	BlueZ Mailing List <bluez-devel@lists.sourceforge.net>,
	Steven Singer <steven.singer@csr.com>
Subject: Re: [Bluez-devel] Re: CSR firmware question...
Date: Mon, 16 Aug 2004 13:01:17 +0100	[thread overview]
Message-ID: <1092657677.1982.14.camel@localhost> (raw)
In-Reply-To: <1092385877.28711.185.camel@pegasus>

Is btdfu app USB only?

A quick skim through the source leads me to believe it is. Will their be
a UART one?

Rod.

On Fri, 2004-08-13 at 09:31, Marcel Holtmann wrote:
> Hi Jean,
> 
> > 	A few questions regarding CSR firmware : what's a commonly
> > available BT USB dongle with a recent CSR firmware.
> 
> as I know there are only dongles with HCI 16.14 firmware available.
> 
> > 	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.
> 
> The D-Link dongle DBT-120 (Rev B3) can be updated using the Apple
> firmware update file. After that it will be HCI 18.1 with default boot
> mode set to HID. Maybe other revisions of the D-Link dongle don't work
> and I already put some of dongles to death while playing with firmware
> upgrade.
> 
> > P.S. : Marcel, do you have a version of btdfu that can write the
> > firmware image to the dongle ? Or some documentation ?
> 
> I never announced the new version of the btdfu, but now as you asked for
> it, here it is:
> 
> 	http://www.holtmann.org/linux/bluetooth/btdfu-0.3.tar.gz
> 
> Use it at your own risk, because you can kill your dongle !!!
> 
> Read what the CSR guys had written about signed firmware and that it is
> not possible to move firmware from one manufacturer to another !!!
> 
> Regards
> 
> Marcel
> 
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel

  parent reply	other threads:[~2004-08-16 12:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-13  0:25 CSR firmware question Jean Tourrilhes
2004-08-13  8:31 ` [Bluez-devel] " 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 [this message]
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=1092657677.1982.14.camel@localhost \
    --to=rtaylor@hcvwireless.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).