From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] UART bluetooth chip problem
Date: Fri, 09 Dec 2005 19:41:26 +0100 [thread overview]
Message-ID: <1134153686.10644.12.camel@blade> (raw)
In-Reply-To: <7846f1440512090957t2f6cd767xc61ae8e19953993e@mail.gmail.com>
Hi Arthur,
> I'm not sure if this is what you're looking for when you say build id
> for the chip, but this is what i see when I look at the back of the
> chip:
the build id is the firmware identifier. It is a uint16 and you also
find it as HCI Revision or LMP Subversion in case of a CSR chip.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-12-09 18:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 1:11 [Bluez-users] UART bluetooth chip problem Arthur Chiu
2005-12-08 5:44 ` Marcel Holtmann
2005-12-08 18:19 ` Arthur Chiu
2005-12-08 20:34 ` Marcel Holtmann
2005-12-08 23:10 ` Arthur Chiu
2005-12-09 0:23 ` Marcel Holtmann
2005-12-09 17:46 ` Arthur Chiu
2005-12-09 17:57 ` Arthur Chiu
2005-12-09 18:15 ` Arthur Chiu
2005-12-09 18:41 ` Marcel Holtmann [this message]
2005-12-09 18:47 ` Marcel Holtmann
2005-12-09 19:23 ` Arthur Chiu
2005-12-09 20:01 ` Marcel Holtmann
2005-12-12 18:21 ` Arthur Chiu
2005-12-12 19:43 ` Marcel Holtmann
2005-12-12 21:06 ` Arthur Chiu
2005-12-12 21:18 ` Marcel Holtmann
2005-12-19 21:54 ` Arthur Chiu
2005-12-19 22:58 ` Marcel Holtmann
2005-12-20 1:02 ` Arthur Chiu
-- strict thread matches above, loose matches on Subject: below --
2005-12-08 18:58 Pering, Trevor
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=1134153686.10644.12.camel@blade \
--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;
as well as URLs for NNTP newsgroup(s).