Re: hciconfig hci0 reset bug
"Odysseus Flappington" <[email protected]> Mon, 21 Jul 2008 21:53:34 +0100
| Newsgroups | gmane.linux.bluez.user |
|---|---|
| Message-ID | <[email protected]> |
Hi Marcel, I keep reading kernel developers saying that we should be persistent, so I'm following up on this, has any progress been made regarding the following issue? This one's a bit of an old one, regarding bluetooth adapters after a certain build number to require a reset command every boot before they'll work properly, I've attached a previous discussion as a reminder to the issue. If there's anything I can do (non-code writing though), please let me know, I'll be glad to help get this sorted. Alexander Deriziotis On 26/03/2008, Marcel Holtmann <[email protected]> wrote: > > Hi Dave, > > I've been looking around to see if I could figure out the build id where >>> the >>> dongles started shipping with the correct HCI_Reset. I think I may have >>> found something. >>> >> >> Thanks a lot. >> >> Marcel, I think it's what you want. I would like to file a patch. >> > > yes, but I already got it via CSR internals. They have always been helpful > when it comes to BlueZ. CSR is an open source friendly company. I didn't > have time to actually produce that patch since we have to turn the whole > logic around. > > Regards > > Marcel > > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Bluez-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bluez-users
Google Mail - hciconfig hci0 reset bug.html
(text/html, 4 KB)
<html lang="en-GB"><head> <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> <title>Google Mail - hciconfig hci0 reset bug</title> <style type="text/css">
body, td{font-family:arial,sans-serif;font-size:80%} a:link, a:active, a:visited{color:#0000CC} img{border:0}
</style> <script>
function Print(){document.body.offsetHeight;window.print()}
</script> </head><body onload="Print()"> <table width="100%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> <td width="143"> <img src="Google%20Mail%20-%20hciconfig%20hci0%20reset%20bug_files/googlemail.gif" alt="Google Mail" width="143" height="59"> </td> <td align="right"> <font size="-1"><b> Odysseus Flappington <[email protected]> </b></font></td> </tr> </tbody></table> <hr> <font size="+2"> <b>hciconfig hci0 reset bug</b></font><br> <hr> <table width="100%" border="0" cellpadding="0" cellspacing="0"> <tbody><tr> <td> <font size="-1"><b> Peter Stephenson <[email protected]> </b></font> </td> <td align="right"> <font size="-1"><b> 26 March 2008 13:50 </b></font> </td></tr><tr> <td colspan="2"> <font size="-1"> <div>Reply-To: BlueZ users <[email protected]></div> <div> To: BlueZ users <[email protected]></div> </font> </td></tr><tr> <td colspan="2"> <table width="100%" border="0" cellpadding="12" cellspacing="0"> <tbody><tr> <td> <font size="-1">On Thu, 20 Mar 2008 17:19:22 +0000<br>
<font color="#550055">"Odysseus Flappington" <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:[email protected]">[email protected]</a>> wrote:<br>
>...<br>
</font><font color="#550055">> So, if I'm reading this correctly, you should issue the reset for all<br>
> CSR-based dongles with build id > 118.<br>
><br>
> Am I on the right track here? Does this information look accurate to you<br>
> guys?<br>
<br>
</font>This is basically correct in that the fix appeared in firmware around then<br>
(the internal log says 117, but possibly that was never released---I've<br>
confined my search to the development side).<br>
<br>
However, it's not that simple in that releases of earlier firmware branches<br>
were still being made for some time. Our ID numbers increase monotonically<br>
so these would have later numbers. I haven't done an exhaustive search;<br>
mostly these releases had L2CAP + RFCOMM on chip for embedded applications,<br>
so you wouldn't care about them. I don't see any evidence of a later HCI<br>
release based on the old code, offhand (but don't take this as gospel).<br>
<br>
If you want to be quite sure not to pick up a build which didn't have the<br>
fix for reset, you could restrict the change to BlueCore 2 and later chips<br>
using the "bcget chipver" call. The early branches without the fix<br>
only ever ran on BlueCore 1: the fix was made in major release 12 and<br>
BlueCore 2 first ran on major release 14.<br>
<br>
--<br>
Peter Stephenson <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:[email protected]">[email protected]</a>> Software Engineer<br>
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road<br>
Cambridge, CB4 0WZ, UK
Tel: +44 (0)1223 692070<br>
<br>
------------------------------<wbr>------------------------------<wbr>-------------<br>
Check out the new SourceForge.net Marketplace.<br>
It's the best place to buy or sell services for<br>
just about anything Open Source.<br>
<a onclick="return top.js.OpenExtLink(window,event,this)" href="http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace" target="_blank">http://ad.doubleclick.net/clk;<wbr>164216239;13503038;w?http://<wbr>sf.net/marketplace</a><br>
</font><div style="padding: 5px 0pt;"><font size="-1"><font size="1" color="#888888">[Quoted text hidden]</font></font></div><font size="-1"></font> </td></tr></tbody></table> </td></tr></tbody></table> <hr> </body></html>