Re: [Bluez-devel] Bluetooth kernel patch for 2.6.1

[Max Krasnyansky <maxk@qualcomm.com>]

On Fri, 2004-01-16 at 17:08, Marcel Holtmann wrote:
> Hi Max,
> 
> > No. I have several email with Broadcomm engineer who explained how
> > protocol works. That's pretty much it. He didn't mention any additional
> > stuff.
> 
> I have a nice USB dump from the Windows driver. Of course it uses an
> older firmware and mini driver, but it also issues another status
> command before selecting the memory. I decided not to include it,
> because I can't decode the extra information and it makes the driver
> more complex. 
I don't think it's needed. May be for the old firmware. Or maybe
something Windows specific.

> Do you have a contact for me, so we can talk about it. I
> am also interested in a Bluetooth 1.2 firmware if it exists.
I'm actually subscribed to Broadcomm release notifications. 
So I'll get and email as soon as the release something. I don't think
that they have 1.2 support yet. Anyway this subscription and stuff is
kind of proprietary. One of the reasons I got it is because I'm a
Qualcommer :).

> > I'm trying to remember scenario where it was a problem (ie us killing
> > incoming connection) but it simply vanished from my memory :).
> 
> I talked a little bit with Steven and Chris from CSR about it (look at
> the archive) and of course there can be a problem with some link manager
> implementation if both sides issue HCI_Disconnect at the same time. This
> is why I choose the double time if we disconnect an incoming connection
> to be safe for BlueZ <-> BlueZ connections.
> 
> > But I still think it's not right, even though spec does not say who must
> > close the connection (are you sure it doesn't btw ?). That Bluetooth
> > mouse must have its reasons for keeping connection and if you kill it
> > most likely they just reconnect immediately.
> 
> I came around with this on 21 Dec and I thought about it for over 3
> weeks before I finally decided to include this patch. I am not happy
> with it, but doing nothing and keep the ACL link makes me even more sad.
> The Apple mouse with its Broadcom HID stack is even more worse than I
> can think about it. At http://www.holtmann.org/linux/bluetooth/hid.html
> you find some of my notes about Bluetooth HID devices. And the mouse
> never disconnects the ACL link. I checked this and it stays forever :(

I see. Well I guess it's ok as long as it doesn't brake anything.

Max