From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Petro <petro@auctionwatch.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Eepro100 driver.
Date: Wed, 13 Feb 2002 21:35:35 -0500 [thread overview]
Message-ID: <3C6B2277.CA9A0BF8@mandrakesoft.com> (raw)
In-Reply-To: <20020213211639.GB2742@auctionwatch.com>
Petro wrote:
>
> I'm a little confused about the status of the EEPro100 driver.
>
> The version in the current kernel has 2 version numbers, and 2
> dates:
>
> v1.09j-t 9/29/99 Donald Becker
> and
> $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin
>
> While the driver available at
> http://www.scyld.com/network/eepro100.html has a version and date
> of v1.19 12/19/2001.
>
> A couple questions:
>
> (1) Has this driver code "forked"?
Yes, a long time ago
> (2) Is there a technical reason that Mr. Beckers version is not
> being kept up to date?
No, a political one, Mr. Becker doesn't like us :) He has refused to
send patches for any kernel, for a long time now.
> (3) We are experiencing a slight problem with the current version
> ( eth1: card reports no resources.) that is supposedly fixed in
> v1.19. Are there plans to integrate the current v1.19 into the main
> line?
No. His fix is not "the right one". There is a gentleman at Sun with
access to the eepro100 documentation, Steve Parker, who has kindly lent
us his brain and time to fix up the driver.
Long term, it is going to be replaced with e100 from Intel, as soon as
that driver is in good shape.
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 2:35 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 [this message]
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
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=3C6B2277.CA9A0BF8@mandrakesoft.com \
--to=jgarzik@mandrakesoft.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