All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Plan for e100-e1000 in mainline
Date: Wed, 01 May 2002 01:13:16 -0400	[thread overview]
Message-ID: <3CCF796C.5090401@mandrakesoft.com> (raw)
In-Reply-To: <20020501010828.GA1753@werewolf.able.es>

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.

    Jeff




  reply	other threads:[~2002-05-01  5:13 UTC|newest]

Thread overview: 11+ 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 [this message]
2002-05-01 14:12   ` Roy Sigurd Karlsbakk
2002-05-01 14:19   ` Steffen Persvold
2002-05-01 23:46   ` [PATCH] intel eths for 2.4 [was: Plan for e100-e1000 in mainline] J.A. Magallon
2002-05-02  0:04     ` 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
  -- strict thread matches above, loose matches on Subject: below --
2002-05-01 22:15 Leech, Christopher
2002-05-02  0:14 ` Steffen Persvold

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=3CCF796C.5090401@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.