All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Steven Singer <steven.singer@csr.com>
Cc: Peter Bergmann <bergmann.peter@gmx.net>,
	BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] bluetooth and wireless lan horror
Date: 08 Oct 2003 13:49:22 +0200	[thread overview]
Message-ID: <1065613768.5327.138.camel@pegasus> (raw)
In-Reply-To: <3F83F423.7020406@csr.com>

Hi Steven,

> > this idea is nice and it sounds like a useful feature. But it can't
> > depend on the RFCOMM traffic. It must depend on the ACL traffic and the
> > BlueZ core must handle it.
> 
> Yes, sorry. Of course it must depend on ACL traffic not RFCOMM. I
> suspect the easiest way to do it is to advertise an ioctl for this
> feature. I'm not quite sure what the interface should be, but I'm sure
> you can think of something.

I think more of an on/off flag with some additional parameters. And it
maybe described the best with "Automatic Sniff Mode".

> We're getting ahead of ourselves though. We need confirmation from Peter
> that sniff helps the problem. If it doesn't we're wasting our time
> (unless you think the feature is useful for other applications).

It can be useful for all kind of devices where power consumption is
essential. Even an iPAQ with a PAN connection can profit from it. The
Microsoft HID devices make heavy use of sniff mode, before they
disconnect the ACL link after 12 minutes of idle time. And everyone
talks about the long battery life time of Bluetooth HID devices, so this
looks like the right way to reduce power consumption.

Regards

Marcel




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2003-10-08 11:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-03  5:50 [Bluez-users] bluetooth and wireless lan horror Peter Bergmann
2003-10-03  8:58 ` Marcel Holtmann
2003-10-03  9:42   ` Peter Bergmann
2003-10-03  9:55     ` Marcel Holtmann
2003-10-03 11:20       ` Steven Singer
2003-10-06 12:32         ` Marcel Holtmann
2003-10-08 11:25           ` Steven Singer
2003-10-08 11:49             ` Marcel Holtmann [this message]
2003-10-08 15:12               ` [Bluez-users] Reducing power consumption (Was: bluetooth and wireless lan horror) Steven Singer
2003-10-03 11:14 ` [Bluez-users] bluetooth and wireless lan horror Timothy Murphy

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=1065613768.5327.138.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bergmann.peter@gmx.net \
    --cc=bluez-users@lists.sourceforge.net \
    --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.