linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe <wirelesss@gmx.de>
To: linux-wireless@vger.kernel.org
Subject: QUESTIONS to ieee80211_beacon_get AND ieee80211_get_buffered_bc
Date: Tue, 10 Jun 2008 16:48:22 +0200	[thread overview]
Message-ID: <484E9436.605@gmx.de> (raw)
In-Reply-To: <48485F12.2050908@mandriva.org>

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 to get the current beacon from the 
ieee80211 stack, right?
So if I want to manipulate the beacons send out I would start at this 
point right?

But where is the difference inbetween is it depending on the 
hardwaredriver, which method is called?

How often refresh the hardwaredriver usually the requested beacon ? Per 
transmission or only once for ther activity duration?
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


  parent reply	other threads:[~2008-06-10 14:46 UTC|newest]

Thread overview: 33+ 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:57                         ` Thomas Backlund
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         ` Joe [this message]
2008-06-10 14:58           ` QUESTIONS to ieee80211_beacon_get AND ieee80211_get_buffered_bc 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           ` [english 95%] " Joe
2008-06-10 15:40             ` 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=484E9436.605@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 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).