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

On Thu, 2004-01-15 at 12:30, Marcel Holtmann wrote:
> Hi Max,
> 
> > - BCM203x loader
> > Should mention (at the top) that it's based on the user-space BCM loader
> > Copyright (C) such and such (eg me ;-))
> 
> I am going to add this. From an USB dump of the Windows driver I
> remember that it is doing some more stuff before it finishes the
> firmware loading. Do you have the complete specs from Broadcom for these
> devices?
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.

> > - This
> > > static inline void hci_conn_put(struct hci_conn *conn) 
> > >  {
> > >  	if (atomic_dec_and_test(&conn->refcnt)) {
> > > -		if (conn->type == SCO_LINK)
> > > +		if (conn->type == ACL_LINK) {
> > > +			unsigned long timeo = (conn->out) ?
> > > +				HCI_DISCONN_TIMEOUT : HCI_DISCONN_TIMEOUT * 2;
> > > +			hci_conn_set_timer(conn, timeo);
> > > +		} else
> > >  			hci_conn_set_timer(conn, HZ / 100);
> > > -		else if (conn->out)
> > > -			hci_conn_set_timer(conn, HCI_DISCONN_TIMEOUT);
> > >  	}
> > >  }
> > 
> > will kill _incoming_ connection when last local socket is closed. I used
> > to have HCI_CONNIDLE_TIMEOUT for that. But I got rid of it because I
> > think it's wrong. We should not kill incoming ACL connection. It should
> > be killed by the initiator.
> 
> You are absolutly right and I can only agree with you, but the reality
> is different. The problem is that some devices don't care about their
> ACL links (for example the Apple Bluetooth mouse) and the Bluetooth
> specification says nothing about the ownership of an ACL link. There is
> no rule who must terminate an ACL link if it is no longer used.
I'm trying to remember scenario where it was a problem (ie us killing
incoming connection) but it simply vanished from my memory :).
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.

Max 

  reply	other threads:[~2004-01-16 21:25 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 [this message]
2004-01-17  1:08       ` Marcel Holtmann
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=1074288307.2559.434.camel@localhost \
    --to=maxk@qualcomm.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    /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.