linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carl Orsborn <cjo@csr.com>
To: jt@hpl.hp.com
Cc: Marcel Holtmann <marcel@holtmann.org>,
	BlueZ mailing list <bluez-devel@lists.sourceforge.net>,
	Steven Singer <steven.singer@csr.com>
Subject: Re: [Bluez-devel] CSR firmware question...
Date: Fri, 13 Aug 2004 11:49:36 +0100	[thread overview]
Message-ID: <411C9CC0.90507@csr.com> (raw)
In-Reply-To: <20040813002514.GA21388@bougret.hpl.hp.com>

Hi, Jean,

Can you reveal what you're doing with the CSR device when
you suffer deadlock?  We may recognise the symptoms, and possibly
know of a workaround or of fixed firmware.

Build 0x1bb is "HCI 15.3", released in August 2002.  Build 0x20e
is "HCI 16.4", released in October 2002.  HCI 16.4 introduced
basic scatternet support and fixed some issues in HCI 15.3.

HCI 16.14 (build 0x33d) was published to product manufacturers
in April 2003.  This fixed a handful of issues in HCI 16.4.  You
may be able to get hold of this, but I have no knowledge of
what firmware D-Link have tested with their hardware and have
subsequently (signed and?) published.

If your hardware is suitable (i.e., if it has an 8 Mbit flash
device), you may be able to load HCI 18.1 or HCI 18.2; these
support BT 1.2.

Carl


Jean Tourrilhes wrote:

> 	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 ?




**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************

  parent reply	other threads:[~2004-08-13 10:49 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
2004-08-16  8:24     ` Marcel Holtmann
2004-08-13 10:49 ` Carl Orsborn [this message]
2004-08-13 18:07   ` [Bluez-devel] " 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=411C9CC0.90507@csr.com \
    --to=cjo@csr.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).