From: Michal Semler <cijoml@volny.cz>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] DBT-120 firmware upgrade
Date: Sat, 27 Nov 2004 01:58:54 +0100 [thread overview]
Message-ID: <200411270158.54567.cijoml@volny.cz> (raw)
In-Reply-To: <200411261152.29925.pavouk@pavouk.org>
Cau,
kdes koupil tuhle dongle? Ji nemuzu nikde sehnat - teda tuhle revizi :(
M.
Dne p=E1 26. listopadu 2004 11:52 Pavel Ruzicka napsal(a):
> Hello,
>
> I want to upgrade DBT-120 Ver B3 (details below).
> I read instructions on http://www.holtmann.org/linux/bluetooth/dfu.html
> I have downloaded BluetoothFWUpdate1.2.dmg.
> On web is version 1.1, but when I try to download it, then version 1.2
> is saved on to disk.
>
> There are 3 dfu files:
> md5sum and name:
> --------------------------------
> f1cb8ce8d3222af2bb6b512f99be62c7 DeskTop.dfu
> 00acbb467c76a1bca899f888fc23a779 GenericCSR.dfu
> f16c41fa42e04d77a9df6ae8c2d40c82 Portable.dfu
>
> Is this right GenericCSR.dfu for DBT-120 B3?
> I mean correct md5sum.
>
> I know, that flashing with btdfu is without warranty, but do you think th=
at
> it will works?
>
> Best regards,
>
> Pavoel Ruzicka
>
> Dongle details:
> ---------------------
> # hciconfig hci0 version
> hci0: Type: USB
> BD Address: 00:0D:88:XX:XX:XX ACL MTU: 192:8 SCO MTU: 64:8
> HCI Ver: 1.1 (0x1) HCI Rev: 0x1bb LMP Ver: 1.1 (0x1) LMP Subver:
> 0x1bb Manufacturer: Cambridge Silicon Radio (10)
> # hciconfig hci0 revision
> hci0: Type: USB
> BD Address: 00:0D:88:8E:B9:F0 ACL MTU: 192:8 SCO MTU: 64:8
> HCI 15.3
> Chip version: BlueCore02
> Max key size: 56 bit
> SCO mapping: HCI
> -------------------------
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-11-27 0:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-26 10:52 [Bluez-users] DBT-120 firmware upgrade Pavel Ruzicka
2004-11-26 17:25 ` Marcel Holtmann
2004-11-27 15:55 ` Pavel Ruzicka
2004-11-27 18:22 ` Marcel Holtmann
2004-11-27 20:30 ` Pavel Ruzicka
2004-11-27 20:50 ` Marcel Holtmann
2004-11-29 12:23 ` Steven Singer
2004-11-29 12:33 ` Marcel Holtmann
2004-11-29 12:49 ` Steven Singer
2004-11-29 17:30 ` Marcel Holtmann
2004-11-29 18:15 ` Peter Stephenson
2004-11-29 18:33 ` Marcel Holtmann
2004-11-29 18:44 ` Peter Stephenson
2004-11-29 18:46 ` Michal Semler
2004-11-27 0:58 ` Michal Semler [this message]
2004-11-27 3:03 ` Marcel Holtmann
2004-11-27 15:12 ` Pavel Ruzicka
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=200411270158.54567.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