All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan De Luyck <lkml@kcore.org>
To: linux-kernel@vger.kernel.org
Subject: [2.6.6] eepro100 vs e100?
Date: Wed, 19 May 2004 08:58:39 +0200	[thread overview]
Message-ID: <200405190858.44632.lkml@kcore.org> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello List,

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:

0000:00:08.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] 
(rev 05)
        Subsystem: Hewlett-Packard Company NetServer 10/100TX
        Flags: bus master, medium devsel, latency 66, IRQ 16
        Memory at fecfd000 (32-bit, prefetchable)
        I/O ports at fcc0 [size=32]
        Memory at fed00000 (32-bit, non-prefetchable) [size=1M]
        Capabilities: [dc] Power Management version 1

I'm wondering what driver is the "best" one to use? Judging by the comments in 
the files, the e100 driver seems to be the best maintained, though I'm 
probably wrong ;p

The website that is referenced in the eepro100 driver is no longer available 
(returns a 404).

If someone can shed some light on this, thanks!

Jan
- -- 
Sanity is the trademark of a weak mind.
		-- Mark Harrold
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAqwWhUQQOfidJUwQRAt7wAJ9H/wapw68XfrYHgV44tf4MfqIUeACdFBvF
R4Aupx+q9AlCKEWjtAE2v2c=
=jQHj
-----END PGP SIGNATURE-----

             reply	other threads:[~2004-05-19  6:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-19  6:58 Jan De Luyck [this message]
2004-05-19  7:11 ` [2.6.6] eepro100 vs e100? 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
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=200405190858.44632.lkml@kcore.org \
    --to=lkml@kcore.org \
    --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.