public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Audio & Bluetooth
Date: Tue, 09 Nov 2004 15:28:14 +0100	[thread overview]
Message-ID: <1100010494.6866.7.camel@pegasus> (raw)
In-Reply-To: <200411091411.33911.tim@birdsnest.maths.tcd.ie>

Hi Timothy,

> > you are kidding me? Use "hciconfig hci0 revision" or look at my webpage
> > where most of the build ids are decoded.
> 
> A bit OT, but I tried that on my Sony Picturebook (C1VFK) and got
> =====================================
> tim@william ~]$ sudo hciconfig hci0 revision
> hci0:   Type: USB
>         BD Address: 08:00:46:21:58:29 ACL MTU: 128:8  SCO MTU: 64:8
>         Build 66
>         Chip version: BlueCore01b (ES)
> =====================================
> 
> I guess that means the chip in the in-built Bluetooth is pre-pre-historic.

this is a pre HCI 11.2 firmware and my oldest card is a Xircom CBT one
with build id 101.

> Is there any hope of upgrading in such a case?
> Eg could upgrading the BIOS upgrade the BT chip too?

No. This is always done separately. However this boot loader shouldn't
check the signature of the DFU file and so in general you can try to
load a HCI 16.4 on it. Of course at your own risk. Does Sony provide an
update for this notebook?

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users/listinfo/bluez-users

  reply	other threads:[~2004-11-09 14:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-08 18:59 [Bluez-users] Audio & Bluetooth administrator tootai
2004-11-08 19:31 ` Brad Midgley
2004-11-08 19:57 ` Marcel Holtmann
2004-11-08 22:56   ` Martin List-Petersen
2004-11-08 23:28     ` Marcel Holtmann
2004-11-09  2:05       ` Martin List-Petersen
2004-11-09  9:54         ` Peter Stephenson
2004-11-09 14:11       ` Timothy Murphy
2004-11-09 14:28         ` Marcel Holtmann [this message]
2004-11-09 14:47         ` Peter Stephenson
2004-11-10  0:56           ` Marcel Holtmann
2004-11-11 20:57   ` Martin List-Petersen
2004-11-11 21:27     ` Marcel Holtmann
2004-11-12  1:09       ` Martin List-Petersen
2004-11-12  1:26         ` Marcel Holtmann
2004-11-12  1:40           ` Martin List-Petersen

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=1100010494.6866.7.camel@pegasus \
    --to=marcel@holtmann.org \
    --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