Bug 12989
Summary: | Updated e1000 driver needed | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Becky Miller <becky_miller> | ||||
Component: | kernel | Assignee: | Michael K. Johnson <johnsonm> | ||||
Status: | CLOSED RAWHIDE | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 7.1 | CC: | 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
Becky Miller
2000-06-24 13:39:17 UTC
Created attachment 1428 [details]
e1000 v2.0.6 driver
v1.0.3 is in kernel 2.2.16-12 on Winston Beta 4. v2.0.6 is now attached to this bug. 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... :-/ 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) 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. Intel has agreed to make a sufficient patent grant, so this is now scheduled for inclusion shortly. 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. yes, we'll get people testing it ASAP. Please put the new kernel on gribble where we can get to it. Thanks! 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. 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. :-/ The 2.0.7 version is integrated. Matt, I'll give you a new kernel sometime tomorrow. Matt, the 2.2.16-19.1 kernel on gribble has the updated driver for you to test. Thanks! Since it is integrated, I'm closing the bug. If you find a bug in the driver, open a new bug... Thanks! |