From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Petro <petro@auctionwatch.com>, linux-kernel@vger.kernel.org
Subject: Re: Eepro100 driver.
Date: Thu, 14 Feb 2002 00:29:04 -0500 [thread overview]
Message-ID: <3C6B4B20.FE4AE960@mandrakesoft.com> (raw)
In-Reply-To: <20020213211639.GB2742@auctionwatch.com> <3C6B2277.CA9A0BF8@mandrakesoft.com> <3C6B406E.1010706@candelatech.com>
Ben Greear wrote:
>
> Jeff Garzik wrote:
>
> > Long term, it is going to be replaced with e100 from Intel, as soon as
> > that driver is in good shape.
>
> Any ETA on that? (Make them really support the ethtool IOCTLs first :))
Soon but not terribly soon. Intel has been responsive to feedback from
Andrew Morton and myself. Once it passes our review and Intel's
testing, it will go in. eepro100 will live on for a while, until we are
certain e100 is stable, though. (and eepro100 won't disappear from 2.4
at all)
> In the past, I heard there were licensing problems, have those
> been cleared up?
Things are looking hopeful on this front. e1000 is going to be
submitted for inclusion into the kernel soon, reportedly with a GPL /
BSD + patent grant license. e100 should follow suit.
This hasn't happened yet, so I don't want to say "yes" for sure...
Jeff
--
Jeff Garzik | "I went through my candy like hot oatmeal
Building 1024 | through an internally-buttered weasel."
MandrakeSoft | - goats.com
next prev parent reply other threads:[~2002-02-14 5:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 21:16 Eepro100 driver Petro
2002-02-14 2:35 ` Jeff Garzik
2002-02-14 4:43 ` Ben Greear
2002-02-14 5:29 ` Jeff Garzik [this message]
2002-02-18 1:52 ` Petro
2002-02-18 21:18 ` Ben Greear
2002-02-22 16:27 ` Jes Sorensen
2002-02-22 16:35 ` Jeff Garzik
2002-02-22 16:38 ` Jes Sorensen
2002-02-22 20:37 ` endre
2002-02-22 21:57 ` Jeff Garzik
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=3C6B4B20.FE4AE960@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=petro@auctionwatch.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