All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Chris Hubball <chris.hubball@csr.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: RE: [Bluez-devel] Apple mouse and disconnect problem
Date: Mon, 05 Jan 2004 17:27:00 +0100	[thread overview]
Message-ID: <1073320020.2508.17.camel@pegasus> (raw)
In-Reply-To: <7D3093619D15A841A322413C3F138E0855C2F9@exchange02.csr.com>

Hi Chris,

> There is no defined "owner" of an ACL connection mainly because the
> L2CAP connections on top of it can be established by either end.
> 
> From general interop experience, if you close the last L2CAP connection
> on the ACL, you should also disconnect the ACL.  Not sure if you've got
> this feature, but it's also a nice idea to add a timeout before closing
> an ACL as it's common to open another L2CAP connection immediately after
> e.g. SDP search followed by HID.  This saves the paging time to re-open
> the ACL.

we got all these things, but we only take care of the ACL links that we
set up. If the other side reconnects to us and had to create an ACL link
(because none exists) we don't terminate the ACL link after the timeout.
So the question is if it is ok if both ends call hci_disconnect? Do you
have seen any problems both ends are trying to terminate the ACL link?
How do the link manager handles this? I can't find any valuable comment
in the specification or the profiles which end should terminate the ACL
link.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-01-05 16:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-05 16:07 [Bluez-devel] Apple mouse and disconnect problem Chris Hubball
2004-01-05 16:27 ` Marcel Holtmann [this message]
2004-01-05 17:15   ` Steven Singer
  -- strict thread matches above, loose matches on Subject: below --
2004-01-05 16:52 Chris Hubball
2003-12-21  1:52 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=1073320020.2508.17.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=chris.hubball@csr.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.