linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Roshanak Rasoli <mrs.roshanak@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: wireless driver ath9k and module 80211 interaction
Date: Fri, 17 Apr 2015 11:24:17 -0500	[thread overview]
Message-ID: <1429287857.20604.13.camel@redhat.com> (raw)
In-Reply-To: <CAGpeqH3J4BvcDjWfVfxeHKj=aY=B3HYjerfN2ZbBQ3WFUQKBWg@mail.gmail.com>

On Fri, 2015-04-17 at 18:01 +0200, Roshanak Rasoli wrote:
> Hi experts,
> 
> I have a question about the code  that you wrote;
> 
> 1- How does the ath9k announce itself to the mac80211?

The ath9k driver handles its own hardware detection via normal kernel
probing and matching mechanisms, and you end up in
drivers/net/wireless/ath/ath9k/pci.c::ath_pci_probe() or ath_ahb_probe()
depending on the bus the device uses.  From there ath9k calls
ieee80211_alloc_hw() which is how ath9k "announces" itself to mac80211.

> 2- How can the mac80211 know how to configure the ath9k.

The hardware module (ath9k) sends a set of "ops" (struct ieee80211_ops)
to mac80211 in the ieee80211_alloc_hw() call that contains callbacks
that mac80211 will run when it needs to configure the device.  See
drivers/net/wireless/ath/ath9k/main.c for the ath9k_ops structure.

Dan

> Could you please point out to the code.
> 
> Thanks in advance.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



      reply	other threads:[~2015-04-17 16:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17 16:01 wireless driver ath9k and module 80211 interaction Roshanak Rasoli
2015-04-17 16:24 ` Dan Williams [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=1429287857.20604.13.camel@redhat.com \
    --to=dcbw@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mrs.roshanak@gmail.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 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).