Linux wireless drivers development
 help / color / mirror / Atom feed
From: "David Lynch Jr." <dhlii@dlasys.net>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: Julian Calaby <julian.calaby@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: N device with open source firmware
Date: Fri, 06 Apr 2012 11:30:44 -0400	[thread overview]
Message-ID: <1333726244.11080.5.camel@hp-dhlii> (raw)
In-Reply-To: <201204061326.32294.chunkeey@googlemail.com>

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. 
The AR9170 has open source firmware - but the hardware documentation is
proprietary.

I am not looking to spark a debate, just determine what options exist. 
And more options is better. 



 
On Fri, 2012-04-06 at 13:26 +0200, Christian Lamparter wrote:
> On Friday 06 April 2012 05:09:03 David Lynch Jr. wrote:
> > On Fri, 2012-04-06 at 13:00 +1000, Julian Calaby wrote:
> > > 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. 
> why? is there anything wrong with AR9170 support? If so, please tell me.
> 
> Regards,
> 	Chr



  reply	other threads:[~2012-04-06 15:34 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. [this message]
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=1333726244.11080.5.camel@hp-dhlii \
    --to=dhlii@dlasys.net \
    --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