From: Joe <wirelesss@gmx.de>
To: linux-wireless@vger.kernel.org
Subject: Re: [english 95%] QUESTIONS to ieee80211_beacon_get AND ieee80211_get_buffered_bc
Date: Tue, 10 Jun 2008 17:34:42 +0200 [thread overview]
Message-ID: <484E9F12.9010502@gmx.de> (raw)
In-Reply-To: <484E9436.605@gmx.de>
Hello Johannes,
thanks to your helpfull support, which enabled me to precise my request,
which I edited in the follows:
> Hy all,
>
> I have a question to he two methods:
>
> ieee80211_beacon_get
> ieee80211_get_buffered_bc
> in tx.c
>
> Both are called by the hardware driver to get a current beacon from
> the ieee80211 stack. Thereby the ieee80211_beacon_get is called
> normally. The other method is just called, if a buffered /multicast
> channel(DTIM) is needed or used - but necessaryly the
> ieee80211_beacon_get must be called before. Is this right?
> So if I want to manipulate the beacons send out I would start at
> ieee80211_beacon_get right?
>
> How often refresh the hardwaredriver usually the requested beacon?
> Does "Returned skb is used only once and low-level driver is
> responsible of freeing it." means, that the method is called always
> when new Beacon frame will be transmitted? Or does this depend on the
> hardware?
> Which kind of hardwaredrivers does allready utilize this methods, isit
> allready the standard way to transfer the generation of the beacons to
> the stack?
>
> An total independent question: Following the suggestion of Holger
> Schurig I started to extend the Glossary in the wiki (with the
> abbreviations in the source code) a few hours ago, but My extension
> was removed again. Why?
>
> All the Best
> Sebastian
next prev parent reply other threads:[~2008-06-10 15:32 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 17:55 iwl4965 oops in 2.6.25-rc5 x86_64 Thomas Backlund
2008-06-05 18:03 ` Tomas Winkler
2008-06-05 18:09 ` Thomas Backlund
2008-06-05 20:10 ` Thomas Backlund
2008-06-05 21:48 ` iwl4965 oops in 2.6.26-rc5 x86_64 Thomas Backlund
2008-06-06 0:44 ` Ian Schram
2008-06-06 11:32 ` Tomas Winkler
2008-06-06 12:01 ` Thomas Backlund
2008-06-06 12:33 ` Thomas Backlund
2008-06-06 13:59 ` Tomas Winkler
2008-06-06 14:29 ` Dan Williams
2008-06-06 14:48 ` Thomas Backlund
2008-06-06 14:51 ` Thomas Backlund
2008-06-06 15:12 ` Tomas Winkler
2008-06-06 15:22 ` Dan Williams
2008-06-06 15:22 ` Dan Williams
2008-06-06 15:57 ` Thomas Backlund
2008-06-06 15:57 ` Thomas Backlund
2008-06-06 16:04 ` Dan Williams
2008-06-06 16:04 ` Dan Williams
2008-06-06 21:43 ` Thomas Backlund
2008-06-06 23:59 ` Tomas Winkler
2008-06-07 13:28 ` Thomas Backlund
2008-06-08 10:27 ` Tomas Winkler
2008-06-08 12:21 ` Thomas Backlund
2008-06-08 15:31 ` Tomas Winkler
2008-06-08 20:07 ` Thomas Backlund
2008-06-09 15:55 ` Dan Williams
2008-06-09 16:43 ` Tomas Winkler
2008-06-09 16:54 ` Dan Williams
2008-06-10 14:48 ` QUESTIONS to ieee80211_beacon_get AND ieee80211_get_buffered_bc Joe
2008-06-10 14:58 ` Johannes Berg
2008-06-10 14:58 ` Johannes Berg
[not found] ` <484E9B84.1070902@gmx.de>
2008-06-10 15:46 ` [english 87%] " Johannes Berg
2008-06-10 15:34 ` Joe [this message]
2008-06-10 15:40 ` [english 95%] " 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=484E9F12.9010502@gmx.de \
--to=wirelesss@gmx.de \
--cc=linux-wireless@vger.kernel.org \
/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.