From: Joerg Albert <jal2@gmx.de>
To: Ahmed A <ahmedcali@yahoo.com>
Cc: David Acker <dacker@roinet.com>, linux-wireless@vger.kernel.org
Subject: Re: Linux wifi development board
Date: Tue, 06 Oct 2009 20:59:01 +0200 [thread overview]
Message-ID: <4ACB9375.6050805@gmx.de> (raw)
In-Reply-To: <4ACB42CB.7010403@roinet.com>
On 10/06/2009 03:14 PM, David Acker wrote:
> Ahmed A wrote:
>> Hello,
>>
>> I have been looking online for a Linux wifi development board. I have
>> come across a few from small companies (reasonably priced), but most
>> of those companies seem to be out of business. I would appreciate
>> suggestions from anyone that may have used one recently, or suggest a
>> link where I can more info some popular ones.
>>
>> I am mostly interested in doing some software development, prototyping
>> on the "application processor", not on the "baseband processor" (radio
>> part).
>>
>> If there is an alternate mailing list I can post my question, I would
>> appreciate that also.
>
> I have had good luck with boards from Gateworks,
> http://www.gateworks.com/ and radios from Ubiquiti, http://ubnt.com/ .
> All of it is supported by OpenWRT, although I believe that the gw2348-4
> (avila) has mainline support.
If Avila boards are a bit to pricey, you may consider getting an Ubiquity Routerstation (Pro) instead.
It ships with OpenWrt.
Anyhow, just check which devices have OpenWRT mainline support (http://www.openwrt.org) and choose one of them.
If you prefer x86 hardware and more standard distributions you may consider an Alix board
(http://www.pcengines.ch/alix.htm). I've got one here running Debian Lenny on a 8 GByte CompactFlash card.
Both Routerstation and Alix require additional miniPCI (or USB) WLAN cards.
Regards,
Joerg.
next prev parent reply other threads:[~2009-10-06 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 8:12 Linux wifi development board Ahmed A
2009-10-06 13:14 ` David Acker
2009-10-06 18:59 ` Joerg Albert [this message]
2009-10-07 2:06 ` Ahmed A
2009-10-07 12:31 ` David Acker
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=4ACB9375.6050805@gmx.de \
--to=jal2@gmx.de \
--cc=ahmedcali@yahoo.com \
--cc=dacker@roinet.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).