From: Kalle Valo <kalle.valo@nokia.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
reinette chatre <reinette.chatre@intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] iwlagn: default to MAX_UCODE_BEACON_INTERVAL in iwl_adjust_beacon_interval
Date: Sat, 14 Mar 2009 19:33:20 +0200 [thread overview]
Message-ID: <49BBEA60.6070702@nokia.com> (raw)
In-Reply-To: <1237050872.5235.95.camel@johannes.local>
Johannes Berg wrote:
> On Sat, 2009-03-14 at 19:08 +0200, Kalle Valo wrote:
>> Johannes Berg wrote:
>>> Kalle, I suspect that your beacon offload will require something like
>>> holding on to BSS structs too, is that correct?
>> My current solution is just to disable beacon filtering (and power save)
>> whenever we are scanning. That way beacon filtering doesn't interfere
>> scanning in anyway.
>
> That makes sense, but disabling beacons means that
>
> iwlist wlan0 scan last
>
> will not show _any_ BSS while associated, but it should really show the
> BSS we're associated to. This is the problem I was referring to.
Oh man, I wasn't even aware of this feature. So yes, my patches
definitely need a way to hold bss structs. I need to study the
implementation more before I can comment.
(Dropping the ipw3945 list from CC, it bugs me about not being subscribed.)
Kalle
prev parent reply other threads:[~2009-03-14 17:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <154E55ADF9629D4E8D13F08BF92ABEB629C9D28B8D@PDSMSX501.ccr.corp.intel.com>
[not found] ` <20090220145223.GA15006@tuxdriver.com>
[not found] ` <1235155966.5860.44.camel@rc-desk>
[not found] ` <20090220194306.GA4051@tuxdriver.com>
[not found] ` <20090221003013.GA3890@tuxdriver.com>
2009-02-21 0:31 ` [PATCH] iwlagn: default to MAX_UCODE_BEACON_INTERVAL in iwl_adjust_beacon_interval John W. Linville
2009-02-21 17:31 ` reinette chatre
2009-02-21 22:59 ` John W. Linville
2009-02-24 2:38 ` Johannes Berg
2009-02-25 1:44 ` John W. Linville
2009-03-14 15:59 ` Johannes Berg
2009-03-14 16:01 ` Johannes Berg
2009-03-14 17:08 ` Kalle Valo
2009-03-14 17:14 ` Johannes Berg
2009-03-14 17:33 ` 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=49BBEA60.6070702@nokia.com \
--to=kalle.valo@nokia.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=reinette.chatre@intel.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.