From: Jeff Garzik <jgarzik@pobox.com>
To: Mateusz Berezecki <mateuszb@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: Atheros and rt2x00 driver
Date: Thu, 18 Aug 2005 17:05:19 -0400 [thread overview]
Message-ID: <4304F80F.10302@pobox.com> (raw)
In-Reply-To: <20050818205821.GA30510@localhost.localdomain>
Mateusz Berezecki wrote:
> Daniel J Blueman <daniel.blueman@gmail.com> wrote:
> ->
> -> There is a good chance the rt2x00 driver will get into the kernel tree
> -> in time, since there is no firmware to upload - Ralink Tech
> -> (www.ralink.com.tw) took a design decision to incorporate the firmware
> -> into an EEPROM on-board, allowing their driver to be GPL'd, and the
> -> rt2x00 is a Linux-specific rewrite which is stabilising well.
>
> the same applies to atheros. they got stuff either in eeprom or in
> driver. no firmware necessary.
>
> there is an ongoing project for atheros cards.
> work in progress located at http://mateusz.agrest.org/atheros/
There is still the open question of whether this is legal enough to
include in the kernel :(
I really would have preferred a cleanroom approach, like that taken by
the forcedeth driver authors.
Jeff
next prev parent reply other threads:[~2005-08-18 21:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-17 18:11 Atheros and rt2x00 driver Daniel J Blueman
2005-08-18 20:58 ` Mateusz Berezecki
2005-08-18 21:05 ` Jeff Garzik [this message]
2005-08-31 7:56 ` Florian Weimer
2005-08-31 8:16 ` Mateusz Berezecki
2005-08-31 8:28 ` Florian Weimer
2005-08-31 10:25 ` Mateusz Berezecki
2005-08-31 9:23 ` Denis Vlasenko
2005-08-31 10:34 ` Mateusz Berezecki
2005-08-20 0:32 ` Lee Revell
-- strict thread matches above, loose matches on Subject: below --
2005-08-17 17:15 Jon Jahren
2005-08-17 17:42 ` joebob
2005-08-17 18:39 ` David S. Miller
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=4304F80F.10302@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mateuszb@gmail.com \
/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