From: "Peter Sandstrom" <peter@zaphod.nu>
To: "Robert Cantu" <robert@tux.cs.ou.edu>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Question: Etherenet Link Detection
Date: Fri, 28 Sep 2001 01:36:07 +0200 [thread overview]
Message-ID: <CIEJKOKMAIAHDBBLFGFFEEOPCGAA.peter@zaphod.nu> (raw)
In-Reply-To: <20010926174116.A7544@tux.cs.ou.edu>
I know for sure that the Intel 82559 Fast Ethernet embedded controller
has a register where it's possible to read out if the link led is active
or not. It seems quite likely that this would be available on other
controllers as well.
Is there any functionality in the current kernel that enables a userland
program to read this? I mostly turn my machines on and and let them do
their thing until the hardware fails :)
/Peter
-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org]On Behalf Of Robert Cantu
Sent: den 26 september 2001 23:41
To: linux-kernel@vger.kernel.org
Subject: Question: Etherenet Link Detection
Is there a method of detecting the link status of an ethernet NIC? If not,
is it feasible? And if it is, then would it be something in each driver,
or on a level above the driver, thereby available to all drivers? I figure
the list is the best place to ask this, although it might be a moot point.
Example: Have a cable modem hooked into a computer's NIC. Cable service
goes out, link light on back of NIC goes out. A hypothetical program says
that the link is gone via some hook in /proc somewhere.
Is this a worthwhile endeavor, if possible?
Thanks in advance,
Robert
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-09-26 23:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-26 21:41 Robert Cantu
2001-09-27 23:36 ` Peter Sandstrom [this message]
2001-09-26 23:39 ` Matthew Dharm
2001-09-26 23:49 ` Randy.Dunlap
2001-09-26 23:49 ` Tim Hockin
2001-09-27 0:10 ` Randy.Dunlap
2001-09-27 0:06 ` Ben Greear
2001-09-27 14:58 ` Robert Cantu
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=CIEJKOKMAIAHDBBLFGFFEEOPCGAA.peter@zaphod.nu \
--to=peter@zaphod.nu \
--cc=linux-kernel@vger.kernel.org \
--cc=robert@tux.cs.ou.edu \
/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
all inboxes | Powered by JetHome®