From: "J.A. Magallon" <jamagallon@able.es>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>,
Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: [PATCH] intel eths for 2.4 [was: Plan for e100-e1000 in mainline]
Date: Thu, 2 May 2002 01:46:44 +0200 [thread overview]
Message-ID: <20020501234644.GA1698@werewolf.able.es> (raw)
In-Reply-To: <20020501010828.GA1753@werewolf.able.es> <3CCF796C.5090401@mandrakesoft.com>
On 2002.05.01 Jeff Garzik wrote:
>J.A. Magallon wrote:
>
>>Hi.
>>
>>Well, subject says it all. Which is the status/plans for inclussion
>>of those drivers in mainline kernel ? AFAIR, e1000 had been licensed,
>>but e100 was not clear yet.
>>
>
>e100 has been in 2.5.x for quite a long time. All license issues have
>similarly been resolved a long time ago.
>
>I expect Intel's Q/A to green light their current driver. With a few
>patches it should be ready for 2.4.x soon.
>
>You can easily copy drivers/net/e100[0] into a 2.4.x kernel, it likely
>compiles without modification.
>
I did it, taking drivers from 2.5.12, and at least it compiles.
I have to try in the real box, but I don't think there were any problems,
at least the same than 2.5....
Marcelo, is there any chance to get this in next -pre or in .19 ?
Patches are big, so I put them at:
http://giga.cps.unizar.es/~magallon/linux/kernel/intel/e100-2.0.27-pre3.bz2
http://giga.cps.unizar.es/~magallon/linux/kernel/intel/e1000-4.2.8.bz2
(note, second gives some offsets and a fail if applied without the first
one...)
Some notes/questions:
- e100 has no help text.
- Versions are far newer than those listen in intel web pages:
* e100: Intel web is 1.8.35, the driver taken from 2.5.12 is 2.0.27-pre3
* e1000: Intel web is 4.1.7, driver in 2.5 is 4.2.8
Thanks for all the info.
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Mandrake Linux release 8.3 (Cooker) for i586
Linux werewolf 2.4.19-pre7-jam9 #2 SMP mié may 1 12:09:38 CEST 2002 i686
next prev parent reply other threads:[~2002-05-01 23:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-01 1:08 Plan for e100-e1000 in mainline J.A. Magallon
2002-05-01 5:13 ` Jeff Garzik
2002-05-01 14:12 ` Roy Sigurd Karlsbakk
2002-05-01 14:19 ` Steffen Persvold
2002-05-01 23:46 ` J.A. Magallon [this message]
2002-05-02 0:04 ` [PATCH] intel eths for 2.4 [was: Plan for e100-e1000 in mainline] Jeff Garzik
2002-05-02 0:16 ` J.A. Magallon
2002-05-06 10:19 ` Plan for e100-e1000 in mainline Jamie Lokier
2002-05-06 22:25 ` J.A. Magallon
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=20020501234644.GA1698@werewolf.able.es \
--to=jamagallon@able.es \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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