From: Ben Greear <greearb@candelatech.com>
To: Donald Becker <becker@scyld.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"eepro100@scyld.com" <eepro100@scyld.com>
Subject: Re: [eepro100] Problem with Linux 2.4.7 and builtin eepro onIntel'sEEA2 motherboard. (Solved, kinda)
Date: Wed, 08 Aug 2001 13:53:15 -0700 [thread overview]
Message-ID: <3B71A6BB.6623B9BF@candelatech.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10108071900340.976-100000@vaio.greennet>
A kind Intel employee told me that the e100 would indeed work
on 2.4.7 kernels, so I downloaded the driver and gave it a shot.
So far, it seems to be working flawlessly. Does anyone know how
to get mii-diag like information out of the e100? (For instance,
I'd like to be able to query the card to see what it's current link
speed is, and force it to various speeds and advertise flags...)
Enjoy,
Ben
--
Ben Greear <greearb@candelatech.com> <Ben_Greear@excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2001-08-08 20:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-07 20:12 Problem with Linux 2.4.7 and builtin eepro on Intel's EEA2 motherboard Ben Greear
2001-08-07 21:53 ` [eepro100] " Donald Becker
2001-08-07 22:21 ` [eepro100] Problem with Linux 2.4.7 and builtin eepro on Intel'sEEA2 motherboard Ben Greear
2001-08-07 22:28 ` Christian Robottom Reis
2001-08-07 23:02 ` Donald Becker
2001-08-08 20:53 ` Ben Greear [this message]
2001-08-07 22:11 ` [eepro100] Problem with Linux 2.4.7 and builtin eepro on Intel's EEA2 motherboard Christian Robottom Reis
2001-08-07 22:25 ` [eepro100] Problem with Linux 2.4.7 and builtin eepro on Intel'sEEA2 motherboard Ben Greear
2001-08-07 22:38 ` Justin Guyett
2001-08-09 0:42 ` Problem with Linux 2.4.7 and builtin eepro on Intel's EEA2 motherboard Florin Andrei
2001-08-09 1:58 ` [eepro100] " Luc Lalonde
2001-08-09 17:46 ` Florin Andrei
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=3B71A6BB.6623B9BF@candelatech.com \
--to=greearb@candelatech.com \
--cc=becker@scyld.com \
--cc=eepro100@scyld.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox