From: Thomas Munck Steenholdt <tmus@tmus.dk>
To: netdev@oss.sgi.com
Subject: Re: [PATCH] 2.6.3 pcnet32.c fix link reporting for non-mii devices
Date: Sat, 21 Feb 2004 08:27:37 +0100 [thread overview]
Message-ID: <40370869.1040304@tmus.dk> (raw)
Don Fry wrote:
> Thomas,
>
> Thanks for the input. I am the unofficial maintainer, sort of. I don't
> have a card without an mii, so I can't test some of the changes. Do
> you know of a way to determine the link state so I can correctly return
> the state?
>
> By the way, are you running 2.4 or 2.6?
>
>
This patch was made against 2.6.3 but it seems that at least Linus'
kernel tree has been pretty much untouched for at least a little while,
so i think it'll patch very nicely against some of the newer 2.4 kernels.
If you can test my patch on som NICs with mii and it works I guess it's
okay! The only NIC that doesn't have mii that I have personaly
experience with is the virtual device found in VMware. Thats also the
one I used to test the patch and it works fine.
Perhaps check this comment posted to a redhat kernel bug for info:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=100527#c5
The guy suggests taking a peek at the LED status register to figure out
if there's a link or not. However I have no idea if that will work for
the VMware NIC anyway and that's the reason for doing it the way I did!
Thomas
next reply other threads:[~2004-02-21 7:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-21 7:27 Thomas Munck Steenholdt [this message]
[not found] <200402202232.i1KMWqD07369@DYN318364BLD.beaverton.ibm.com>
2004-02-21 21:57 ` [PATCH] 2.6.3 pcnet32.c fix link reporting for non-mii devices Thomas Munck Steenholdt
2004-02-24 5:31 ` Thomas Munck Steenholdt
2004-02-24 5:34 ` Thomas Munck Steenholdt
-- strict thread matches above, loose matches on Subject: below --
2004-02-20 19:55 Thomas Munck Steenholdt
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=40370869.1040304@tmus.dk \
--to=tmus@tmus.dk \
--cc=netdev@oss.sgi.com \
/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.