linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@nokia.com>
To: "Bharat Bhushan" <bharat.b.bhushan@gmail.com>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
	"Felix Fietkau" <nbd@openwrt.org>,
	"Luis R. Rodriguez" <lrodriguez@atheros.com>,
	"Luis R. Rodriguez" <mcgrof@gmail.com>,
	"Tomas Winkler" <tomasw@gmail.com>,
	"Michael Buesch" <mb@bu3sch.de>,
	"linux-wireless\@vger.kernel.org"
	<linux-wireless@vger.kernel.org>
Subject: Re: No ProbeResp - assume out of range
Date: Tue, 04 Nov 2008 09:05:57 +0200	[thread overview]
Message-ID: <87prlcas2y.fsf@nokia.com> (raw)
In-Reply-To: <d9360e520811032132t6ca3f29djb8c9decc41335e7b@mail.gmail.com> (ext Bharat Bhushan's message of "Tue\, 4 Nov 2008 11\:02\:40 +0530")

"Bharat Bhushan" <bharat.b.bhushan@gmail.com> writes:

>>> Why not configure the beacon miss interrupt instead of passing beacons to
>>> mac80211 in STA mode? That should save some battery on Laptops because it
>>> won't cause 10 extra wakeups every second.
>>
>> We have no way to indicate to mac80211 that the hw is watching beacons,
>> so that'd be equivalent to just dropping them. We've discussed such API,
>> and I hope somebody will implement it :)
>
> if we start dealing with beacons in NIC, i think this will impact
> roaming scenarios, beacouse in most of  roaming algorithms signal
> strength of beacon received played a pivot rolef and  ignoring this at
> NIC  this will not allow client to take judicious decisions.

The NIC should send an event to the driverinforming about the low
signal strength situation and driver will forward this information to
mac80211. The firmware has knowledge of the beacon rssi so this should
be trivial to implement in firmware. But if the firmware really
doesn't support this, the driver can always disable beacon filtering
feature in mac80211.

-- 
Kalle Valo

  reply	other threads:[~2008-11-04  7:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-02 21:05 No ProbeResp - assume out of range Luis R. Rodriguez
2008-11-02 22:03 ` Michael Buesch
2008-11-02 22:29   ` Luis R. Rodriguez
2008-11-02 22:52     ` Michael Buesch
2008-11-02 22:42   ` Tomas Winkler
2008-11-02 22:58     ` Luis R. Rodriguez
2008-11-03  0:25       ` Luis R. Rodriguez
2008-11-03 16:48         ` Felix Fietkau
2008-11-03 17:50           ` Johannes Berg
2008-11-04  5:32             ` Bharat Bhushan
2008-11-04  7:05               ` Kalle Valo [this message]
2008-11-04  6:58             ` Kalle Valo
2008-11-04 11:17         ` Michael Buesch
2008-11-04 12:43           ` Bob Copeland
2008-11-03  7:19     ` Kalle Valo
2008-11-02 22:33 ` Davide Pesavento
2008-11-04 18:19 ` Christoph Hellwig
2008-11-04 19:15   ` Luis R. Rodriguez
2008-11-05 10:30     ` Kalle Valo

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=87prlcas2y.fsf@nokia.com \
    --to=kalle.valo@nokia.com \
    --cc=bharat.b.bhushan@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lrodriguez@atheros.com \
    --cc=mb@bu3sch.de \
    --cc=mcgrof@gmail.com \
    --cc=nbd@openwrt.org \
    --cc=tomasw@gmail.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;
as well as URLs for NNTP newsgroup(s).