public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Stephenson <pws@csr.com>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Slaves in Sniff mode
Date: Thu, 24 Jun 2004 11:09:57 +0100	[thread overview]
Message-ID: <200406241009.i5OA9wFo030305@news01.csr.com> (raw)
In-Reply-To: "tOpSy TuRvY"'s message of "Thu, 24 Jun 2004 11:43:26 +0200." <Pine.BSO.4.58.0406241134240.10334@nemo.student.utwente.nl>

tOpSy TuRvY wrote:
> Isn't it technically possible for the  master to send small amount of 
> BNEP data to PANUs in parked mode using the PSB logical channel? The 
> PANU would of course have to shift into connected mode before replying.
> 
> The above would allow the system to support a BNEP layer broadcast (e.g. 
> ARP) to all PANUs attached to the GN (i.e those in connected and parked mode)
> .

Broadcasts are allowed to parked slaves, so it's possible to do that
without unparking.  However, this is only possible master to slave and
(while I don't know much about the intervening layers) the notion of an
aysmmetric link isn't very natural at the networking layer, so you would
have to define the occasions when this would occur quite carefully.

For anything else, you would have to unpark the slave.
The spec allows the link manager to do this autonomously if data
arrives, but you can't rely on that (I don't know of anyone who does it,
offhand, but I haven't particularly looked), so the host has to be
prepared to do the unparking.

> > > One last question on this issue. Can the GN in Bluez ask the PANU to go 
> > > into sniff mode *automatically* based on some criteria (e.g. low 
> > > activity), or ask it to come out of sniff mode (e.g. based on a large 
> > > queue).
> > 
> > It would be up to the host code to do this.  There's nothing stopping
> > (say) the bnep layer from monitoring data and sending sniff and unsniff
> > requests.  There's no facility for doing this below HCI.
> > 
> 
> Isn't it better for e.g. the link manager to do this since the BNEP layer 
> can only see BNEP traffic, but the link manager can also see SCO and ACL 
> traffic.

This is why Marcel mentioned the HCI layer --- it sees all the data and
can tell the device to enter or leave sniff.  This is probably the best
bet.  There's no real gain that I can see in forcing it below HCI.
(At the last count our chip had roughly four orders of magnitude less RAM
than the average new PC.  That's why you can get dongles for $15.)

pws


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-06-24 10:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1BcqIi-0002cT-53@sc8-sf-list2.sourceforge.net>
2004-06-22 18:57 ` [Bluez-users] Max Number of PANUs supported in PAN tOpSy TuRvY
2004-06-22 21:30   ` Marcel Holtmann
2004-06-22 22:07     ` tOpSy TuRvY
2004-06-22 22:14       ` Marcel Holtmann
2004-06-23 11:23         ` [Bluez-users] Slaves in Sniff mode tOpSy TuRvY
2004-06-23 12:06           ` Peter Stephenson
2004-06-23 12:16           ` Marcel Holtmann
2004-06-23 12:58             ` tOpSy TuRvY
2004-06-23 13:30               ` Marcel Holtmann
2004-06-23 16:06               ` Peter Stephenson
2004-06-23 16:33                 ` Marcel Holtmann
2004-06-23 17:15                 ` tOpSy TuRvY
2004-06-23 17:41                   ` Peter Stephenson
2004-06-24  9:43                     ` tOpSy TuRvY
2004-06-24 10:09                       ` Peter Stephenson [this message]
2004-06-24 11:39                         ` [Bluez-users] BT_ADDR Address Resolution tOpSy TuRvY
2004-06-24 12:06                           ` Marcel Holtmann
2004-06-24 12:26                             ` tOpSy TuRvY
2004-06-24 12:31                               ` Marcel Holtmann
2004-06-24 12:46                                 ` tOpSy TuRvY
2004-06-24 12:54                                   ` Marcel Holtmann
2004-06-23 17:59                   ` [Bluez-users] Slaves in Sniff mode 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=200406241009.i5OA9wFo030305@news01.csr.com \
    --to=pws@csr.com \
    --cc=bluez-users@lists.sourceforge.net \
    /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