From: "John W. Linville" <linville@tuxdriver.com>
To: Pavel Roskin <proski@gnu.org>
Cc: Michael Wu <flamingice@sourmilk.net>,
Jeff Williams <angelbane@ou.edu>,
linux-wireless@vger.kernel.org
Subject: Re: Airgo Networks Wireless Card Linux support
Date: Mon, 12 Mar 2007 10:37:47 -0400 [thread overview]
Message-ID: <20070312143747.GA8878@tuxdriver.com> (raw)
In-Reply-To: <1173676135.30756.27.camel@dv>
On Mon, Mar 12, 2007 at 01:08:55AM -0400, Pavel Roskin wrote:
> On Mon, 2007-03-12 at 00:38 -0400, Michael Wu wrote:
>
> > Well, if you're willing to write specs, I'll help write the driver. Silly
> > question first however - have you asked Airgo Networks if they are willing to
> > help with a Linux driver?
>
> From
> http://searchopensource.techtarget.com/originalContent/0,289142,sid39_gci1134910,00.html
>
> "Joe felt that Airgo Networks should be commended for its honorable
> handling of OSS, but he still had no luck there. When he called the
> company, he found out that no Linux drivers will be available for the
> Airgo chip set until late 2005 or early 2006."
>
> Oh well. At least they are not against the idea of Linux drivers.
A reply from 13 February 2007 to a query a made a day or two before that:
"Thank you for your inquiry. At this time we do not have Linux drivers
for Airgo products. Please check back on our web for new products and
updates. With focus on delivering our next generation of solutions, we
are not able to support outside development efforts." [1]
At this point I have to recommend that all Linux users avoid Airgo
hardware unless/until either Airgo decides to support its hardware or
someone is successful with a reverse engineering effort. I expect
that there will be other .11n hardware supported on Linux in the
near future.
Regarding reverse engineering, please do follow the example set by the
bcm43xx team. We don't need any more drivers of questionable origin.
Thanks,
John
[1] To which I replied "If you don't have time to support me, how will
you ever have time to write your own driver?" Of course, I have had
no response to that one.
--
John W. Linville
linville@tuxdriver.com
prev parent reply other threads:[~2007-03-12 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 19:52 Airgo Networks Wireless Card Linux support Jeff Williams
2007-03-12 4:38 ` Michael Wu
2007-03-12 5:08 ` Pavel Roskin
2007-03-12 10:26 ` Doragh, Phil
2007-03-12 14:37 ` John W. Linville [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=20070312143747.GA8878@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=angelbane@ou.edu \
--cc=flamingice@sourmilk.net \
--cc=linux-wireless@vger.kernel.org \
--cc=proski@gnu.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).