From: Holger Schurig <holgerschurig@googlemail.com>
To: "Heyendal, Carl" <CHeyendal@stanleyworks.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: wireless in linux
Date: Wed, 1 Dec 2010 22:20:52 +0100 [thread overview]
Message-ID: <201012012220.53025.holgerschurig@gmail.com> (raw)
In-Reply-To: <1D6034426110564DA0DEA9EE9793B38357E35E4823@NBE-MBX01.americas.swk.pri>
> I'm staring right now at the latest wpa_supplicant readme with all the
> choices that I need to make. I'll be lucky if it works. It's really been
> a piece-meal effort so far.
This has nothing to do with being a newby. Newbies use distributions. Go and
install Fedora, SuSE, Ubuntu, whatever. They compiled wpa_supplicant for
you.
Okay, I see that you work in the embedded space. Maybe I can point to to
bitbake and www.openembedded.org? Here there's a recipe that cross-compiles
wpa_supplicant for you. While OpenEmbedded itself isn't something for
newbies, using it takes away some of the decision-making ("Which config
option do I need?" from you.
But I wouldn't call any embedded work a work for a newbie ...
> Are there any reference books, tutorials, howto's, wireless enabled
> kernels...anything that someone can point me to that would help?
http://wireless.kernel.org
For wpa_supplicant questions, even when it comes to compiling, try the
hostap mailing list. This list covers both hostap and wpa_supplicant.
BTW, I agree that queries like "Linux wireless introduction" or "Linux
wireless HOWTO" will reveal lot's of outdated stuff.
--
http://www.holgerschurig.de
prev parent reply other threads:[~2010-12-01 21:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 22:05 wireless in linux Heyendal, Carl
2010-11-30 22:16 ` Luis R. Rodriguez
2010-11-30 23:07 ` Larry Finger
2010-12-01 13:57 ` Heyendal, Carl
2010-12-01 16:55 ` Heyendal, Carl
2010-12-01 21:20 ` Holger Schurig [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=201012012220.53025.holgerschurig@gmail.com \
--to=holgerschurig@googlemail.com \
--cc=CHeyendal@stanleyworks.com \
--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).