From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: "Jinsung Lee" <ljs@netsys.kaist.ac.kr>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Implementing wireless testbed on Linux
Date: Mon, 24 Aug 2009 10:18:13 +0200 [thread overview]
Message-ID: <200908241018.13234.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <029301ca2239$0ac9ad70$205d0850$@kaist.ac.kr>
> In the case of using 802.11n chipset, which card and device
> driver should I choose? At the same time, which version of
> Linux kernel should be appropriate?
I'd go with Atheros based PCI cards. The cards are good, and the
support is outstanding (Atheros people work together with Linux
community on this mailing list!).
> Is there any difference between pci and usb interfaces?
Sure. Please read http://www.pcisig.com/specifications and
http://www.usb.org/developers/docs/. The busses are VERY
different in case of hierarchy, latency, max transfer rates and
so on.
I fear, however, that this mailing list isn't the right channel
to transfer this knowledge.
> Definitely, all device and software should be stable and
> up-to-date.
That's a contradicion. Especially wireless is quite evolving in
the Linux kernel.
There's the possibility that you use a vendor-kernel (e.g. Debian
kernel, Fedora kernel, or whatever distro you use). I personally
won't do this, but I'd use a more "vanilla" kernel. The vendors
usually put a huge amount on patches into their kernels, that
will make results not as easy to compare. Also, if you have a
specific questions, chances are way higher that the people in
the mailing list know about the "vanilla" kernel or
wireless-testing kernel than some random vendor kernel.
If you absolutely need something stable, you should go with the
least recent stable linux kernel (see http://www.kernel.org/).
If you want to be more up-to-date, you should use
wireless-testing. Expect new functionality, fixed bugs, but also
new bugs there :-) However, If you ever have to change some
driver code, you definitely want wireless-testing. You cannot
(usually) use the source from the stable kernel when submitting
patches. More info at
http://wireless.kernel.org/en/developers/Documentation
prev parent reply other threads:[~2009-08-24 8:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 8:26 Implementing wireless testbed on Linux Jinsung Lee
2009-08-24 8:18 ` 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=200908241018.13234.hs4233@mail.mn-solutions.de \
--to=hs4233@mail.mn-solutions.de \
--cc=linux-wireless@vger.kernel.org \
--cc=ljs@netsys.kaist.ac.kr \
/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