b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Büsch" <mb@bu3sch.de>
To: b43-dev@lists.infradead.org
Subject: 802.11 MAC state information
Date: Tue, 08 Feb 2011 15:27:43 +0100	[thread overview]
Message-ID: <1297175263.29400.11.camel@maggie> (raw)
In-Reply-To: <009801cbc77c$17225830$45670890$@gmx.net> (sfid-20110208_053652_042296_D74736C9)

On Tue, 2011-02-08 at 11:36 +0100, h2o-post wrote: 
> Hi all,
> 
> I would like to know from the Broadcom experts, if there is the possibility in the b43 driver to read the current state of the 802.11 MAC..
> As I am more familiar with the Atheros design, I am uncertain if there are register that someone could just sample to get this information or if you need to get some hocks int the micro controller code ??? 
> To explain briefly the way I get this information form Atheros hardware: on the wifi card there is a 40MHzmac clock that counts up 4 registers. One for the clock ticks itself, one for the MAC been in transmitting mode, one counter for the MAC been in receiving mode and the last counter represents energy detection above the cca threshold.
> I already checked the b43 souce code in order to find some registers that could count those mac states .. but I was not able to find anything. So I am asking to the list 
> where such information would be accessible from the Broadcom wifi hardware.

You can get all information you want from
http://bcm-v4.sipsolutions.net/

There's no such thing as "the MAC state". There are
hundreds of registers related to various "MAC states". So you'll
have to be more specific on what you want to know.

-- 
Greetings Michael.

  reply	other threads:[~2011-02-08 14:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-08 10:36 802.11 MAC state information h2o-post
2011-02-08 14:27 ` Michael Büsch [this message]
2011-02-08 15:21   ` AW: " h2o-post
2011-02-08 15:28     ` Michael Büsch

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=1297175263.29400.11.camel@maggie \
    --to=mb@bu3sch.de \
    --cc=b43-dev@lists.infradead.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).