Re: [Bluez-users] hciconfig hci0 reset bug

["Odysseus Flappington" <deriziotis@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1725 bytes --]

Hey Marcel,

On 26/03/2008, Marcel Holtmann <marcel@holtmann.org> 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.


Does this mean we have all the information needed to write the patch? Have
you got the logic for a solution ready, but just need time to get it
written?

If I understand correctly, we can't be sure that all non-L2CAP/RFCOMM dongles
with build id > 118 will need a reset since they possibly still released
older firmware on newer builds. If this is the case, it seems like the only
way to be sure of the build id is by testing as many dongles as possible.

I don't see how we can do this other than trying to buy as many older
bluetooth dongles as possible. I can't imagine any of us would be willing to
do this, so perhaps the best thing to do is to reset all build ids > 118 and
adjust the build id as people submit bug-reports related to this issue as
time goes on. Asking whoever submitted a bug report to report their build id
should be reasonable in order to make the fix more accurate.

I would really like to see this fix released since as a user my experience
with external bluetooth dongles in Linux was very disappointing due to this
bug.

Many thanks,
Alex Deriziotis (Jackflap)

[-- Attachment #2: Type: text/html, Size: 2364 bytes --]