linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "sl reddy" <slreddyforneobux@gmail.com>
Cc: "Onteddu Slreddy" <slreddy88@gmail.com>,
	netdev <netdev@vger.kernel.org>,
	linux-can@vger.kernel.org, linux-kernel@vger.kernel.org,
	e1000-devel@lists.sourceforge.net, linux-usb@vger.kernel.org,
	linux-wireless@vger.kernel.org, ath9k-devel@venema.h4ckr.net,
	wil6210@qca.qualcomm.com, brcm80211-dev-list@broadcom.com,
	devicetree-discuss <devicetree-discuss@lists.ozlabs.org>
Subject: Re: Wifi basics documents
Date: Fri, 8 Feb 2013 11:20:40 +0100	[thread overview]
Message-ID: <5114D178.10007@broadcom.com> (raw)
In-Reply-To: <CAGmqTTSovcse3k4kv5o=+K6adAb672O5nJ=nXfZmc=d36gMSJw@mail.gmail.com>

On 02/08/2013 10:53 AM, sl reddy wrote:
> any successions will be helpful for me

My *suggestion* would be:

http://wireless.kernel.org/en/developers/Documentation

For what it is worth, below is some terrible ascii art.

Gr. AvS

Fullmac model:

                 user-space (libnl)
                  |
+----------+      v
| cfg80211 |------o nl80211 api
+----------+
     ^
     |
     v
+----------+
| fullmac  |------o netdev
| driver   |
+----------+

Softmac model:

                 user-space (libnl)
                  |
+----------+      v
| cfg80211 |------o nl80211 api
+----------+
     ^
     |
     v
+----------+
| mac80211 |------o netdev
+----------+
     ^
     |
     v
+----------+
| softmac  |
| driver   |
+----------+



      parent reply	other threads:[~2013-02-08 10:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHT=_ri0JBrbPfWJrzjYR4eNDDW9ygMkJSDU4vJXEfh_STLK9g@mail.gmail.com>
2013-02-08  8:34 ` Wifi basics documents Arend van Spriel
     [not found]   ` <CAGmqTTSovcse3k4kv5o=+K6adAb672O5nJ=nXfZmc=d36gMSJw@mail.gmail.com>
2013-02-08 10:20     ` Arend van Spriel [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=5114D178.10007@broadcom.com \
    --to=arend@broadcom.com \
    --cc=ath9k-devel@venema.h4ckr.net \
    --cc=brcm80211-dev-list@broadcom.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=slreddy88@gmail.com \
    --cc=slreddyforneobux@gmail.com \
    --cc=wil6210@qca.qualcomm.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).