linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@nokia.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: "Christoph Hellwig" <hch@infradead.org>,
	"linux-wireless\@vger.kernel.org"
	<linux-wireless@vger.kernel.org>
Subject: Re: No ProbeResp - assume out of range
Date: Wed, 05 Nov 2008 12:30:20 +0200	[thread overview]
Message-ID: <87ljvyfosj.fsf@nokia.com> (raw)
In-Reply-To: 43e72e890811041115v1f7901a0w36593f9852d03c86@mail.gmail.com

Luis R. Rodriguez <mcgrof@gmail.com> writes:

> I posted a patch which enables beacons to be received by the STA --
> this however, as was pointed out by the patch that disabled the beacon
> filter on ath5k (note not ath9k, but ath9k also had it disabled),
> increases the number of interrupts on the device, as it seems it
> enables beacons not only for the BSSID you are on but for all BSSIDs.
> Not sure what other devices support and how their beacon filter, if
> they have any, works.

There are beacon filter implementations, for example stlc4560 works
such that it doesn't send any beacons to the host but sends an event
whenever it cannot here beacons anymore.

> The patch I posted is a fix that works with what mac80211 expects --
> beacons. The way I'm inclined to resolve this properly in mac80211
> is so that we tell drivers to enable beacons in STA mode (if it
> supports this, HW_CAP flag I guess) only after we miss a probe
> reply, or while we are scanning, that way we can also listen for
> beacons in case we want to roam away to another AP. Just throwing
> some ideas out there. Any comments?

I and Johannes discussed about this earlier:

http://marc.info/?l=linux-wireless&m=122441202315681&w=2

It should be fairly trivial to implement as a first step, we can
improve it as we learn more.

-- 
Kalle Valo

      reply	other threads:[~2008-11-05 10:30 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
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 [this message]

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=87ljvyfosj.fsf@nokia.com \
    --to=kalle.valo@nokia.com \
    --cc=hch@infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@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).