From: Alessandro Gnagni <enterprise.nx@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Trying to add support of 802.11ac broadcom chpiset to openwrt
Date: Tue, 12 Nov 2013 13:13:52 +0100 [thread overview]
Message-ID: <52821B80.6000305@gmail.com> (raw)
Hi,
i am trying to implement on a smart city network a solution based on
high end home routers like the asus RT-AC66U.
we want to use openwrt for that but unfortunately the broadcom driver
isn't yet supported.
I have one rt-ac66u here for development, there is anything that i can
do for help?
i came here after a suggestion of one member on openwrt forum:
https://forum.openwrt.org/viewtopic.php?pid=217341#p217341
i also read this past email:
http://www.spinics.net/lists/linux-wireless/msg110443.html
Thx for attention.
next reply other threads:[~2013-11-12 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 12:13 Alessandro Gnagni [this message]
2013-11-12 17:50 ` Trying to add support of 802.11ac broadcom chpiset to openwrt Arend van Spriel
2014-01-27 19:10 ` Adrian Chadd
2014-01-27 21:36 ` 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=52821B80.6000305@gmail.com \
--to=enterprise.nx@gmail.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).