From: Igor Bezukh <Igor@galilsoft.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: A question about Wireless dongle HW and driver support - best practice
Date: Fri, 11 Jul 2014 11:39:20 +0000 [thread overview]
Message-ID: <1405078551691.6483@galilsoft.com> (raw)
In-Reply-To: <2bac19ce5f704178b25628b5e9e08344@DBXPR07MB093.eurprd07.prod.outlook.com>
Hi All,
We have an embedded system that consists of Atmel AT91SAM9G20 SoC ( singgle core ARMv5).
This SoC also has USB 1.1 ( 11Mbps).
Kernel version is 2.6.32.
The solution should have two wireless dongles - one acting as Acess Point and the other acting as WiFi client.
In other words, we need the system to be a wireless repeater bridge.
We had a lot of issues with the Atheros CARL9170 drivers and with Ralink 2870.
Ralink 2870 doesn't have support for AP mode, at least in it's 5572 driver pack for linux from Meidatek website.
We need the driver to support both Master and Managed modes, and working on a single CPU core, no SMP.
Can you please suggest a good chipset for such a solution from driver perspective and from HW performance perspective?
TIA,
Igor Bezukh
parent reply other threads:[~2014-07-11 11:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <2bac19ce5f704178b25628b5e9e08344@DBXPR07MB093.eurprd07.prod.outlook.com>]
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=1405078551691.6483@galilsoft.com \
--to=igor@galilsoft.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).