LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Jan De Luyck <lkml@kcore.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.6] eepro100 vs e100?
Date: Wed, 19 May 2004 11:46:15 -0400	[thread overview]
Message-ID: <40AB8147.5080404@tmr.com> (raw)
In-Reply-To: <200405190858.44632.lkml@kcore.org>

Jan De Luyck wrote:

> I'm currently in the process of cleaning up my 2.6 kernel configuration on my 
> trusty SMP HP Netserver LC3, which comes shipped with 2 identical intel Pro 
> Ethernet 100 mbit cards:

While initially there did seem to be lockups with multiple e100 devices, 
I haven't seen that in some versions. I have several servers which run 
the NICs at 70-80 Mbit all the time and see no issues with the e100 at 
this time.

-- 
bill davidsen <davidsen@tmr.com>
   CTO TMR Associates, Inc
   Doing interesting things with small computers since 1979

  parent reply	other threads:[~2004-05-19 15:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-19  6:58 Jan De Luyck
2004-05-19  7:11 ` Danny ter Haar
2004-05-19 11:12 ` Meelis Roos
2004-05-19 11:19 ` J. Ryan Earl
2004-05-19 15:46 ` Bill Davidsen [this message]
2004-05-19 22:48 ` Darren Williams

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=40AB8147.5080404@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@kcore.org \
    --subject='Re: [2.6.6] eepro100 vs e100?' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).