All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Steven Singer <steven.singer@csr.com>,
	BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] sco / csr final notes
Date: Wed, 31 Mar 2004 21:18:48 +0100	[thread overview]
Message-ID: <406B27A8.2000308@superbug.demon.co.uk> (raw)
In-Reply-To: <1080761775.2536.3.camel@pegasus>

Marcel Holtmann wrote:
> Hi James,
> 
> 
>>Just out of interest, how does one upgrade the firmware on a USB device 
>>using a CSR chip ?
>>
>>I have this device: -
>>
>>bash-2.05b# hciconfig hci0 version
>>hci0:   Type: USB
>>         BD Address: 00:A0:96:1F:42:BF ACL MTU: 192:8  SCO MTU: 64:8
>>         HCI Ver: 1.1 (0x1) HCI Rev: 0x135 LMP Ver: 1.1 (0x1) LMP 
>>Subver: 0x135
>>         Manufacturer: Cambridge Silicon Radio (10)
>>
>>bash-2.05b# hciconfig hci0 revision
>>hci0:   Type: USB
>>         BD Address: 00:A0:96:1F:42:BF ACL MTU: 192:8  SCO MTU: 64:8
>>         HCI 13.10
>>         Chip version: BlueCore01b
>>         Max key size: 56 bit
>>         SCO mapping:  HCI
> 
> 
> you need a *.dfu firmware file from your dongle manufacturer.
> 
> Regards
> 
> Marcel
> 
> 
> 
> 

The dongle manufacturer is Mitsumi, and I cannot find any firmware files 
for it.
Does anyone know of any url that might have updated firmware for this 
device ?

Cheers
James

  reply	other threads:[~2004-03-31 20:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-31 10:32 [Bluez-devel] sco / csr final notes Simon Vogl
2004-03-31 10:59 ` Marcel Holtmann
2004-03-31 11:48   ` Simon Vogl
2004-03-31 15:09     ` Steven Singer
2004-03-31 15:13       ` Simon Vogl
2004-03-31 16:26         ` Steven Singer
2004-03-31 19:10           ` James Courtier-Dutton
2004-03-31 19:36             ` Marcel Holtmann
2004-03-31 20:18               ` James Courtier-Dutton [this message]
2004-03-31 20:29                 ` Marcel Holtmann

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=406B27A8.2000308@superbug.demon.co.uk \
    --to=james@superbug.demon.co.uk \
    --cc=bluez-devel@lists.sourceforge.net \
    --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.