From: Ben Greear <greearb@candelatech.com>
To: Petro <petro@auctionwatch.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Eepro100 driver.
Date: Mon, 18 Feb 2002 14:18:07 -0700 [thread overview]
Message-ID: <3C716F8F.7060705@candelatech.com> (raw)
In-Reply-To: <20020213211639.GB2742@auctionwatch.com> <3C6B2277.CA9A0BF8@mandrakesoft.com> <3C6B406E.1010706@candelatech.com> <3C6B4B20.FE4AE960@mandrakesoft.com> <20020218015234.GA6113@auctionwatch.com>
Petro wrote:
> On Thu, Feb 14, 2002 at 12:29:04AM -0500, Jeff Garzik wrote:
>
>>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)
>>
>
> So what do you suggest people like Mr. Greear and I do in the mean
> time?
It's easy enough to download the e100 from Intel's site if you
want to use it. I will continue to try to use the eepro100 unless
I find problems with my particular hardware NICS. The eepro100
still supports MII-IOCTLS better than the e100 supports ethtool
interfaces, and I like to know all those twisty little bits!
Ben
>
>
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2002-02-18 21:18 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
2002-02-18 1:52 ` Petro
2002-02-18 21:18 ` Ben Greear [this message]
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=3C716F8F.7060705@candelatech.com \
--to=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