From: "Arend van Spriel" <arend@broadcom.com>
To: "Onteddu Slreddy" <slreddy88@gmail.com>
Cc: 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 09:34:09 +0100 [thread overview]
Message-ID: <5114B881.9000100@broadcom.com> (raw)
In-Reply-To: <CAHT=_ri0JBrbPfWJrzjYR4eNDDW9ygMkJSDU4vJXEfh_STLK9g@mail.gmail.com>
On 02/08/2013 07:55 AM, Onteddu Slreddy wrote:
> Hello All,
>
>
> I recently joined this group the group.
>
> Can anybody suggest me places where I can get Documents which will explain
> wifi Architecture in brief i would like to know details like
>
> In Linux for embedded systems:
> What is the software architecture for wifi
> What are each folders in kernel/net and kernel/drivers/net refer to
> What is wpa_supplicant how to know which version I have to use
> How to get familiar with words like nl802.11, mac802.11, wext,
> copat-wireless, compatwireless-openmac
> If I have to add a new chip driver what are the checklist points i
> have to see
>
> My Quesitions may be basic kindly bare with me
> If any body have self prepared documents that will be great help for me
802.11 is a IEEE standard that is freely available for download.
Regarding Linux architecture and infrastructure there is a lot of
information to be found on wireless.kernel.org.
Regards,
Arend
next parent reply other threads:[~2013-02-08 8:40 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 ` Arend van Spriel [this message]
[not found] ` <CAGmqTTSovcse3k4kv5o=+K6adAb672O5nJ=nXfZmc=d36gMSJw@mail.gmail.com>
2013-02-08 10:20 ` Wifi basics documents Arend van Spriel
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=5114B881.9000100@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=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).