From: "David Lynch Jr." <dhlii@dlasys.net>
To: Julian Calaby <julian.calaby@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: N device with open source firmware
Date: Thu, 05 Apr 2012 23:09:03 -0400 [thread overview]
Message-ID: <1333681744.4108.150.camel@hp-dhlii> (raw)
In-Reply-To: <CAGRGNgUZqvgtuEfJk7vZ0Y4mEzadTBj4G3VQwmTykvy0R9dp8g@mail.gmail.com>
On Fri, 2012-04-06 at 13:00 +1000, Julian Calaby wrote:
> Hi David,
>
> On Fri, Apr 6, 2012 at 04:15, David Lynch Jr. <dhlii@dlasys.net> wrote:
> > I am looking for recommendations for an 802.11N device that is well
> > documented and has opensource firmware for a project. I do nto care
> > whether it is mPCI, USB, .... so long as there is good documentation on
> > the chipset and good open source firmware as I will be making extensive
> > firmware changes for testing purposes.
>
> If I recall correctly, the ar9170 devices with the carl9170 driver use
> an open source firmware and are 802.11n capable.
I have a fair amount of experience with the ar9170 and the carl9170
firmware. I was hoping something was better documented and supported.
But I can live with that if i have to.
thank you.
>
> There was also an effort to produce a open source firmware for
> broadcom devices, but I'm not sure what it's status is and what
> progress they made.
>
> Also, there's a GSoC project to open source the firmware for the USB
> ath9k devices, (ath9k_htc) but I don't think any progress has been
> made.
>
> Thanks,
>
next prev parent reply other threads:[~2012-04-06 3:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 18:15 N device with open source firmware David Lynch Jr.
2012-04-06 3:00 ` Julian Calaby
2012-04-06 3:09 ` David Lynch Jr. [this message]
2012-04-06 11:26 ` Christian Lamparter
2012-04-06 15:30 ` David Lynch Jr.
2012-04-06 22:33 ` Adrian Chadd
2012-04-07 20:20 ` David Lynch Jr.
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=1333681744.4108.150.camel@hp-dhlii \
--to=dhlii@dlasys.net \
--cc=julian.calaby@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