All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Bluetooth kernel patch for 2.6.1
Date: Sat, 17 Jan 2004 02:08:20 +0100	[thread overview]
Message-ID: <1074301700.2629.124.camel@pegasus> (raw)
In-Reply-To: <1074288307.2559.434.camel@localhost>

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. 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 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 :(

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-01-17  1:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-15 19:07 [Bluez-devel] Bluetooth kernel patch for 2.6.1 Marcel Holtmann
2004-01-15 19:50 ` BCM2033 firmware loader [was Re: [Bluez-devel] Bluetooth kernel patch for 2.6.1] Max Krasnyansky
2004-01-15 20:16   ` [Bluez-devel] Re: BCM2033 firmware loader Marcel Holtmann
2004-01-16 21:14     ` Max Krasnyansky
2004-01-17  1:19       ` [Bluez-devel] " Marcel Holtmann
2004-01-20 19:27         ` Max Krasnyansky
2004-01-15 20:03 ` [Bluez-devel] Bluetooth kernel patch for 2.6.1 Max Krasnyansky
2004-01-15 20:30   ` Marcel Holtmann
2004-01-16 21:25     ` Max Krasnyansky
2004-01-17  1:08       ` Marcel Holtmann [this message]
2004-01-20 19:23         ` Max Krasnyansky
2004-01-21  1:36           ` Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2004-01-13  3:59 Marcel Holtmann
2004-01-09 14:56 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=1074301700.2629.124.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=maxk@qualcomm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.