From: Claudio Takahasi <cktakahasi@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] firmware upgrade
Date: Tue, 20 Sep 2005 13:52:34 -0300 [thread overview]
Message-ID: <e1effdeb05092009524d67443b@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1766 bytes --]
Hi folks,
Before start update the firmware of my dongles I would like make sure
that nothing is wrong. Sometimes, dongles upgrades can end up with
a dead dongle :) I read some documents in the Marcel's home
page(http://holtmann.org) but I am afraid of upgrade my dongles :)
I have the following dongles/adapters:
>>>> D-Link DBT-120 Hardware B3
$hciconfig -a hci0 version
hci0: Type: USB
BD Address: XX:XX:XX: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 -a hci0 revision
hci0: Type: USB
BD Address: XX:XX:XX:XX:XX:XX ACL MTU: 192:8 SCO MTU: 64:8
HCI 15.3
Chip version: BlueCore02-External
Max key size: 56 bit
SCO mapping: HCI
>>>> D-Link DBT-122 Hardware A1
$hciconfig -a hci0 version
hci0: Type: USB
BD Address: XX:XX:XX:XX:XX:XX ACL MTU: 377:10 SCO MTU: 16:0
HCI Ver: 1.2 (0x2) HCI Rev: 0x0 LMP Ver: 1.2 (0x2) LMP Subver: 0x309
Manufacturer: Broadcom Corporation (15)
$hciconfig -a hci0 revision
hci0: Type: USB
BD Address: XX:XX:XX:XX:XX:XX ACL MTU: 377:10 SCO MTU: 16:0
Firmware 0.3 / 9
>>>> IBM T41
$hciconfig -a hci0 version
BD Address: XX:XX:XX:XX:XX:XX ACL MTU: 192:8 SCO MTU: 64:8
HCI Ver: 1.1 (0x1) HCI Rev: 0x222 LMP Ver: 1.1 (0x1) LMP Subver: 0x222
Manufacturer: Cambridge Silicon Radio (10)
$hciconfig -a hci0 revision
hci0: Type: USB
BD Address: XX:XX:XX:XX:XX:XX ACL MTU: 192:8 SCO MTU: 64:8
Build 546
Chip version: BlueCore02-External
Max key size: 128 bit
SCO mapping: HCI
I am not sure if upgrade will work in the DBT-122 and in my notebook
IBM T41. If someone has tips or references of how do this procedure
please send me the links.
Thanks in advance,
Claudio
[-- Attachment #2: Type: text/html, Size: 3041 bytes --]
next reply other threads:[~2005-09-20 16:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 16:52 Claudio Takahasi [this message]
2005-09-20 16:56 ` [Bluez-devel] firmware upgrade Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2006-10-11 21:44 Martin Karger
2006-10-11 22:09 ` Marcel Holtmann
2006-10-12 5:04 ` Martin Karger
2006-10-12 7:23 ` Marcel Holtmann
2006-10-12 13:22 ` Martin Karger
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=e1effdeb05092009524d67443b@mail.gmail.com \
--to=cktakahasi@gmail.com \
--cc=bluez-devel@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