Bug 12989

Summary: Updated e1000 driver needed
Product: [Retired] Red Hat Linux Reporter: Becky Miller <becky_miller>
Component: kernelAssignee: Michael K. Johnson <johnsonm>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: high    
Version: 7.1CC: alan, matt_domsch
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-08-08 13:56:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
e1000 v2.0.6 driver none

Description Becky Miller 2000-06-24 13:39:17 UTC
The latest version of the Intel E1000 driver version is 2.0.6
This needs to be included in the kernel.

Comment 1 Matt Domsch 2000-07-21 18:46:56 UTC
Created attachment 1428 [details]
e1000 v2.0.6 driver

Comment 2 Matt Domsch 2000-07-21 18:47:46 UTC
v1.0.3 is in kernel 2.2.16-12 on Winston Beta 4.  v2.0.6 is now attached to 
this bug.

Comment 3 Michael K. Johnson 2000-08-01 22:05:07 UTC
Alan, is this something that should be sucked into official kernels?
I see that they added a few extra files and do not have a Makefile
patch or anything intelligent like that... :-/

Comment 4 Alan Cox 2000-08-01 22:15:16 UTC
Neither E100 or E1000 will go into the mainstream 2.2 or 2.4 kernel until Intel
are prepared to give us either a GPL licensed copy or a piece of paper saying
they will not suddenly spring suprise patent claims on users of the driver after
we distribute it.

There are technical reasons for not including E100 (its crap) and E1000 needs a
good clean up but the current holdup is licensing issues and protection against
Intel springing unpleasant traps on companies. (Several of whom interestingly
specifically named this as a worry and named intel as the people they thought
would try it)

Are legal on bugzilla 8)


Comment 5 Michael K. Johnson 2000-08-02 16:35:08 UTC
No, but I spoke to legal, and legal is deeply troubled by the
lack of a patent grant and thinks that without an explicit grant
of some sort, we really should pull the drivers entirely.

Comment 6 Michael K. Johnson 2000-08-04 14:46:21 UTC
Intel has agreed to make a sufficient patent grant, so
this is now scheduled for inclusion shortly.

Comment 7 Michael K. Johnson 2000-08-04 18:54:38 UTC
It builds.  However, because I had to really hack it into
place to make it build within the kernel as a replacement
for our earlier e1000 driver, I may have broken it, and I
can't tell if that's the case.

We don't have hardware to test it, at least as far as I
am aware.  Becky or Matt, could one of you arrange for
testing it and get back to me?  I'll give you a kernel
with the new driver to test.

Comment 8 Matt Domsch 2000-08-04 18:57:07 UTC
yes, we'll get people testing it ASAP.  Please put the new kernel on gribble 
where we can get to it.
Thanks!

Comment 9 Michael K. Johnson 2000-08-04 21:35:57 UTC
It's now on your private directory on gribble, source and all the
i686 binaries.  Just took a while to build, I guess there was a
lot of other stuff in the build system.

Comment 10 Michael K. Johnson 2000-08-07 19:44:49 UTC
Intel is providing a 2.0.7 version of the driver with the
same code base but changed slightly to patch in easier.
This will keep me from having to mangle the driver before
inserting it into the kernel...

I'm still interested to know whether I broke 2.0.6 while
putting it in place, and we still want to test it in case
Intel runs into unexpected trouble getting 2.0.7 to us in
time, so now I'm asking you to run tests twice.  :-/

Comment 11 Michael K. Johnson 2000-08-08 00:56:42 UTC
The 2.0.7 version is integrated.  Matt,
I'll give you a new kernel sometime
tomorrow.

Comment 12 Michael K. Johnson 2000-08-08 13:56:07 UTC
Matt, the 2.2.16-19.1 kernel on gribble has the
updated driver for you to test.  Thanks!

Comment 13 Michael K. Johnson 2000-08-09 17:00:02 UTC
Since it is integrated, I'm closing the bug.  If
you find a bug in the driver, open a new bug...

Thanks!