From: Peter Stephenson <pws@csr.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] hciconfig hci0 reset bug
Date: Wed, 26 Mar 2008 12:50:15 +0000 [thread overview]
Message-ID: <20080326125015.60e5fa96@news01> (raw)
In-Reply-To: <5eee8c670803201019q4703c779wbb597b806cf4d7c@mail.gmail.com>
On Thu, 20 Mar 2008 17:19:22 +0000
"Odysseus Flappington" <deriziotis@gmail.com> wrote:
>...
> So, if I'm reading this correctly, you should issue the reset for all
> CSR-based dongles with build id > 118.
>
> Am I on the right track here? Does this information look accurate to you
> guys?
This is basically correct in that the fix appeared in firmware around then
(the internal log says 117, but possibly that was never released---I've
confined my search to the development side).
However, it's not that simple in that releases of earlier firmware branches
were still being made for some time. Our ID numbers increase monotonically
so these would have later numbers. I haven't done an exhaustive search;
mostly these releases had L2CAP + RFCOMM on chip for embedded applications,
so you wouldn't care about them. I don't see any evidence of a later HCI
release based on the old code, offhand (but don't take this as gospel).
If you want to be quite sure not to pick up a build which didn't have the
fix for reset, you could restrict the change to BlueCore 2 and later chips
using the "bcget chipver" call. The early branches without the fix
only ever ran on BlueCore 1: the fix was made in major release 12 and
BlueCore 2 first ran on major release 14.
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK Tel: +44 (0)1223 692070
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2008-03-26 12:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 22:51 [Bluez-users] hciconfig hci0 reset bug Odysseus Flappington
2008-03-03 1:21 ` Dave Young
2008-03-03 1:24 ` Dave Young
2008-03-03 11:35 ` Odysseus Flappington
2008-03-03 22:19 ` Odysseus Flappington
2008-03-17 12:28 ` Odysseus Flappington
2008-03-18 7:14 ` Dave Young
2008-03-20 17:19 ` Odysseus Flappington
2008-03-22 0:29 ` Dave Young
2008-03-26 16:22 ` Marcel Holtmann
2008-04-04 8:58 ` Odysseus Flappington
2008-07-21 20:53 ` Odysseus Flappington
2008-07-22 5:02 ` Dave Young
2008-03-26 12:50 ` Peter Stephenson [this message]
2008-03-26 16:24 ` 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=20080326125015.60e5fa96@news01 \
--to=pws@csr.com \
--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