public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Jean Tourrilhes <jt@hpl.hp.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Re: out of range
Date: Wed, 12 Jan 2005 21:32:58 +0100	[thread overview]
Message-ID: <1105561978.7961.140.camel@pegasus> (raw)
In-Reply-To: <20050112183806.GE31615@bougret.hpl.hp.com>

Hi Jean,

> > I think there is no way to differ between it yet. Feel free to propose
> > an idea how that should be done within the normal socket operation.
> 
> 	Marcel : I did propose to you a scheme to detect out of range
> conditions ahead of the Supervision Timeout that would clearly also
> work for this.

I had your patch in my -mh patches for some time, but then it got out of
sync with the mainline development and I dropped it. However I want your
patch inside the kernel, but I still don't like the way of notification.
What do you think about setting sk->sk_err with an error code like we do
for the reliable feature that detects ACL packet errors. Even if the HCI
events itself are global I like to do the notification through the
socket interfaces of L2CAP and RFCOMM. Comments?

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-01-12 20:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-12 18:38 Re: out of range Jean Tourrilhes
2005-01-12 20:32 ` Marcel Holtmann [this message]
2005-01-12 21:25   ` Jean Tourrilhes
2005-01-12 23:15     ` [Bluez-devel] " 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=1105561978.7961.140.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=jt@hpl.hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox