From: "David Lynch Jr." <dhlii@dlasys.net>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Christian Lamparter <chunkeey@googlemail.com>,
Julian Calaby <julian.calaby@gmail.com>,
linux-wireless@vger.kernel.org
Subject: Re: N device with open source firmware
Date: Sat, 07 Apr 2012 16:20:41 -0400 [thread overview]
Message-ID: <1333830041.2826.25.camel@hp-dhlii> (raw)
In-Reply-To: <CAJ-Vmon9R1UO0oqH-O6fauj46-1O7ZN=yM4BiZqFTk5cJS38uA@mail.gmail.com>
On Fri, 2012-04-06 at 15:33 -0700, Adrian Chadd wrote:
> On 6 April 2012 08:30, David Lynch Jr. <dhlii@dlasys.net> wrote:
> > I was not seeking to impugn the linux-wireless AR9170 support, just
> > looking to see what additional alternatives exist before starting a
> > major project that will require substantial firmware work.
> >
> > My complaints with respect to its "openness" regard Atheros.
> >
> > I was hoping for a mini-PCI device.
>
> Ah. There's (as far as I know) no Atheros mini-PCI device that runs firmware.
>
> > The AR9170 has open source firmware - but the hardware documentation is
> > proprietary.
>
> There's an open source NDA process at QCA now. Sign the NDA, get
> access to documentation. Done/done.
I have AR9170 documentation covered by a different NDA with a prior
client. That probably had an NDA with atheros.
I do not like NDAs but will sign them where necescary.
What i am asking is is there an alternative N device besides the AR9170
that one way or another has support in depth - hardware information,
firmware, etc.
I am gathering that the AR9170 is currently the N hardware with the best
information. Atleast i am already familiar with it.
>
>
>
> Adrian
prev parent reply other threads:[~2012-04-07 20:23 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.
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. [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=1333830041.2826.25.camel@hp-dhlii \
--to=dhlii@dlasys.net \
--cc=adrian@freebsd.org \
--cc=chunkeey@googlemail.com \
--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