public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Semler <cijoml@volny.cz>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Dongle firmware
Date: Tue, 4 Jan 2005 22:45:58 +0100	[thread overview]
Message-ID: <200501042245.58663.cijoml@volny.cz> (raw)
In-Reply-To: <20050104210042.M19007@bandos.homelinux.com>

Dne =FAt 4. ledna 2005 22:16 Jose Bernardo Silva napsal(a):
> On Tue, 04 Jan 2005 13:21:37 +0100, Marcel Holtmann wrote
>
> > Hi Jose,
> >
> > > I've seen recently a few messages about new firmwares, is there a list
> > > of dongles and firmwares available?
> > > I have a Acer BT-500 and a MSI MS-6967, and I'd like to update these
> > > two.
> >
> > you should actually ask the vendor of these dongles for updates. However
> > the ACER is a BlueCore01b and can't be updated with the
> > GenericCSR.dfu firmware file and for the MSI I don't know. The
> > general rule at the moment is if "hciconfig hci0 revision" don't
> > show BlueCore02 and lsusb don't show it as a "Cambridge Silicion
> > Radio". You shouldn't even try to update it.
>
> Marcel,
>
> My BT-500 shows in lsusb as " ID 0a12:0001 Cambridge Silicon Radio Ltd.",
> and "hciconfig hci0 revision shows it as a BlueCore02 as follows:
> hci0:   Type: USB
>         BD Address: 00:60:57:32:96:0E ACL MTU: 192:8  SCO MTU: 64:8
>         HCI 14.7
>         Chip version: BlueCore02 (ES2)
>         Max key size: 56 bit
>         SCO mapping:  PCM
>
> Does this mean I can update it? If so, where can I get that GenericCSR.dfu
> firmware, and what can I use to update?

This dongle looks prepared for apple firmware :)

>
> As for the MSI, the lsusb output isn't very promising ("ID 0db0:1967"),
> even thoguh the output of hciconfig is similar:
> hci0:   Type: USB
>         BD Address: 00:10:DC:AF:E1:13 ACL MTU: 192:8  SCO MTU: 64:8
>         HCI 16.4
>         Chip version: BlueCore02
>         Max key size: 56 bit
>         SCO mapping:  HCI

Don't think about flashing MSI, there isn't firmware for it...I own one too=
  :
((

Michal


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-01-04 21:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-04 11:09 [Bluez-users] Dongle firmware Jose Bernardo Silva
2005-01-04 12:21 ` Marcel Holtmann
2005-01-04 21:16   ` Jose Bernardo Silva
2005-01-04 21:45     ` Michal Semler [this message]
2005-01-05  9:14       ` Jose Bernardo Silva
2005-01-05  9:14       ` Jose Bernardo Silva
2005-01-04 20:39 ` Michal Semler
  -- strict thread matches above, loose matches on Subject: below --
2005-01-17  8:18 [Bluez-users] dongle firmware Marco Trudel
2005-01-17 11:20 ` 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=200501042245.58663.cijoml@volny.cz \
    --to=cijoml@volny.cz \
    --cc=bluez-users@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