From: Peter Stephenson <pws@csr.com>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Slaves in Sniff mode
Date: Wed, 23 Jun 2004 13:06:22 +0100 [thread overview]
Message-ID: <200406231206.i5NC6NrA007514@news01.csr.com> (raw)
In-Reply-To: "tOpSy TuRvY"'s message of "Wed, 23 Jun 2004 13:23:59 +0200." <Pine.BSO.4.58.0406231319140.20827@nemo.student.utwente.nl>
tOpSy TuRvY wrote:
> Does anyone know if the master delays ACL transmittions to slaves in sniff
> mode (i.e. till they become active again), or will it just keep on
> transmitting the baseband frame till the slave eventually wakes up and can
> send an ACK.
It should transmit any data during the sniff window. The rules there
are identical to those in active mode, although obviously you will
get very much reduced throughput.
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
next prev parent reply other threads:[~2004-06-23 12:06 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 [this message]
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
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=200406231206.i5NC6NrA007514@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