Re: [Bluez-users] hciconfig hci0 reset bug

["Dave Young" <hidave.darkstar@gmail.com>]

On Tue, Jul 22, 2008 at 4:53 AM, Odysseus Flappington
<deriziotis@gmail.com> wrote:
> 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?

Hi, I ever tried to implement it, but I'm occupied by other projects.

The key problem is that bluetooth drivers can only set the flags
during the probe now, but we need to send bluetooth commands to get
the revision.

>
> 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 <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.
>>
>> Regards
>>
>> Marcel
>>
>
>



-- 
Regards
dave