All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Pavel Ruzicka <pavouk@pavouk.org>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>, cijoml@volny.cz
Subject: Re: [Bluez-users] MSI MS-6970 (BToes) firmware upgrade
Date: Fri, 16 Jul 2004 10:53:51 +0200	[thread overview]
Message-ID: <1089968030.4517.89.camel@pegasus> (raw)
In-Reply-To: <200407161045.10846.pavouk@pavouk.org>

Hi Pavel,

> > The only dongle that can be easily updated using the Apple firmware is
> > from D-Link. And I only had success with the B3 revision. The B4 is not
> > working and I broke another dongle of mine.
> 
> Can you tell me, if firmware for D-link use different key than firmware
> for MSI?

I don't know, but I think so. You can check the USB vendor and product
id for your dongle. If it is not the CSR default 0a12:0001 you shouldn't
even think about a firmware upgrade.

> It's possible to get this information from DFU file?

Not that I know.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-07-16  8:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-13 10:25 [Bluez-users] MSI MS-6970 (BToes) firmware upgrade Pavel Ruzicka
2004-07-14 17:33 ` Marcel Holtmann
2004-07-15 19:59   ` Pavel Ruzicka
2004-07-15 20:41     ` Bc. Michal Semler
2004-07-16  6:37       ` Marcel Holtmann
2004-07-16  8:45         ` Pavel Ruzicka
2004-07-16  8:53           ` Marcel Holtmann [this message]
2004-07-16  6:31     ` 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=1089968030.4517.89.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=cijoml@volny.cz \
    --cc=pavouk@pavouk.org \
    /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.