public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff Nguyen" <jeff@aslab.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Ville Herva" <vherva@mail.niksula.cs.hut.fi>,
	<linux-kernel@vger.kernel.org>, <linux-net@vger.kernel.org>
Subject: Re: VM-global-2.2.18pre17-7
Date: Fri, 27 Oct 2000 10:40:51 -0700	[thread overview]
Message-ID: <017b01c0403d$0c9f19b0$7818b7c0@aslab.com> (raw)
In-Reply-To: <E13pD7X-0004fZ-00@the-village.bc.nu>

Alan,

I agree with your point. In term of usability, the e100 driver has a wider
range of support for the Intel NIC cards.

Jeff

----- Original Message -----
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jeff Nguyen <jeff@aslab.com>
Cc: Ville Herva <vherva@mail.niksula.cs.hut.fi>;
<linux-kernel@vger.kernel.org>; <linux-net@vger.kernel.org>
Sent: Friday, October 27, 2000 10:16 AM
Subject: Re: VM-global-2.2.18pre17-7


> > You should use the Intel e100 driver at
> > http://support.intel.com/support/network/adapter/pro100/100Linux.htm.
> > It works much better than eepro100.
>
> Thats not the general consensus, but its worth trying in case it works
best
> for a given problem. In paticular it knows about bugs with combinations of
> transceivers which the eepro100 driver does not.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-10-27 17:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.21.0010251633080.3324-100000@freak.distro.conectiva>
     [not found] ` <39F84B64.5935C12@ovh.net>
     [not found]   ` <39F8566D.51561CB3@profmakx.de>
2000-10-26 16:21     ` VM-global-2.2.18pre17-7 octave klaba
2000-10-26 19:53       ` VM-global-2.2.18pre17-7 Timothy Ball
2000-10-27 10:31         ` VM-global-2.2.18pre17-7 Andrew Morton
2000-10-27  5:59       ` VM-global-2.2.18pre17-7 Neale Banks
2000-10-27 13:29         ` VM-global-2.2.18pre17-7 Marcelo Tosatti
2000-10-27 15:13           ` VM-global-2.2.18pre17-7 Ville Herva
2000-10-27 15:42             ` VM-global-2.2.18pre17-7 Jeff Nguyen
2000-10-27 17:16               ` VM-global-2.2.18pre17-7 Alan Cox
2000-10-27 17:40                 ` Jeff Nguyen [this message]
2000-10-27 18:52             ` VM-global-2.2.18pre17-7 octave klaba
2000-10-28 12:53               ` VM-global-2.2.18pre17-7 octave klaba

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='017b01c0403d$0c9f19b0$7818b7c0@aslab.com' \
    --to=jeff@aslab.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=vherva@mail.niksula.cs.hut.fi \
    /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