All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Steven Singer <steven.singer@csr.com>
Cc: Florian Echtler <echtler@fs.tum.de>,
	Olivier Bornet <olivier.bornet@smartdata.ch>,
	BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] bthid cvs question
Date: Mon, 05 Jan 2004 20:02:34 +0100	[thread overview]
Message-ID: <1073329354.2508.26.camel@pegasus> (raw)
In-Reply-To: <3FF99466.8080209@csr.com>

Hi Steven,

> A lot of devices use page scan repetition mode R2 by default as it's the
> lowest power mode.

the most device I have seen are using R1 by default and the only R2 are
my HID devices.

> BlueZ's behaviour is wrong. If you do not know the page scan repetition
> mode of the device you're going to connect to then you must use R2. The
> 1.1 spec does not state this explicitly, but it can be implied.

I am no baseband expert, so let me see if I understand you right. In the
case we don't know the page scan repetition mode we should use R2 in
prefer of R1 or even R0? Does this have disadvantages if the devices is
in R1 or R0 mode? I ask because we found that connecting with R1 by
default gives us a significant page time improvement.

If only R2 makes sense in case that we don't the exact value, somebody
should bring up an errata to the HCI working group ;)

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 19:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-09 17:28 [Bluez-users] bthid cvs question Jeffrey Arbuckle
2003-12-10  1:43 ` Marcel Holtmann
2003-12-10  8:02   ` Olivier Bornet
2003-12-10 14:18     ` Marcel Holtmann
2003-12-20 23:01       ` Florian Echtler
2003-12-21  1:25         ` [Bluez-devel] " Marcel Holtmann
2003-12-21 10:52           ` Florian Echtler
2003-12-21 11:56             ` [Bluez-devel] " Marcel Holtmann
2003-12-21 12:48               ` Florian Echtler
2003-12-21 13:14                 ` [Bluez-devel] " Marcel Holtmann
2004-01-05 16:44           ` Steven Singer
2004-01-05 19:02             ` Marcel Holtmann [this message]
2004-01-05 21:21               ` [Bluez-devel] " Steven Singer

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=1073329354.2508.26.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=echtler@fs.tum.de \
    --cc=olivier.bornet@smartdata.ch \
    --cc=steven.singer@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.