From: Iwo Mergler <iwo@call-direct.com.au>
To: Reiner Herrmann <r_herrma@informatik.uni-kl.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: mac80211: Force beacon update?
Date: Fri, 03 Jul 2009 17:29:07 +1000 [thread overview]
Message-ID: <4A4DB343.7060800@call-direct.com.au> (raw)
In-Reply-To: <4A4DB01E.2030408@informatik.uni-kl.de>
Reiner Herrmann wrote:
> Hi,
>
> I want to attach a custom IE to beacons, but some drivers (like b43)
> are fetching their beacons via ieee80211_beacon_get() only once and
> retransmit this beacon every time.
> Some other drivers (like mac80211_hwsim, ath9k) are calling it
> before every beacon transmission.
>
> Is there a general way to make all drivers generate new beacons instead
> of caching them or would I have to adapt them?
> If adapting drivers is the only way, do you have any suggestions on
> how to do that?
Hi Reiner
the drivers that call ieee80211_beacon_get() only once, have
hardware that transmits beacons automatically. That is, the
beacon template from ieee80211_beacon_get() is stored in the
hardware and the hardware then automatically sends that while
updating a few fields as needed.
In other words, the driver doesn't know anything about the
beacons after the initial setup, and thus can't call ieee80211_beacon_get().
No caching is involved. :-)
So to do what you want, you need to disable the automatic
beaconing and use packet injection and send your beacons
as raw frames.
Best regards,
Iwo
next prev parent reply other threads:[~2009-07-03 7:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-03 7:15 mac80211: Force beacon update? Reiner Herrmann
2009-07-03 7:29 ` Iwo Mergler [this message]
2009-07-03 8:00 ` Johannes Berg
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=4A4DB343.7060800@call-direct.com.au \
--to=iwo@call-direct.com.au \
--cc=linux-wireless@vger.kernel.org \
--cc=r_herrma@informatik.uni-kl.de \
/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