public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gianni Tedesco <gianni@ecsc.co.uk>
To: Nico Schottelius <nico-mutt@schottelius.org>
Cc: linux.nics@intel.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: network driver informations [general NIC, Wireless and e100]
Date: 01 Aug 2002 13:00:15 +0100	[thread overview]
Message-ID: <1028203217.32264.44.camel@lemsip> (raw)
In-Reply-To: <20020731212426.GA3342@schottelius.org>

[-- Attachment #1: Type: text/plain, Size: 724 bytes --]

On Wed, 2002-07-31 at 22:24, Nico Schottelius wrote:
> Hello!
> 
> I recently tried the e100 driver and was happy that it reports
> if there is a connection and speed and so on.
> 
> But should these informations not be reported through /proc-fs ?
> I think this would make it easier for programs to monitor connection
> status. We could even have a small red/green light in the KDE panel
> to display connection status for different cards.

AFAIK this information is already available for ethernet cards with an
MII tranciever via a bunch of ioctl()'s. Google for mii-diag.c for an
example.

-- 
// Gianni Tedesco (gianni at ecsc dot co dot uk)
8646BE7D: 6D9F 2287 870E A2C9 8F60 3A3C 91B5 7669 8646 BE7D

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2002-08-01 11:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-31 21:24 network driver informations [general NIC, Wireless and e100] Nico Schottelius
2002-08-01 12:00 ` Gianni Tedesco [this message]
2002-08-01 12:10 ` Jeff Garzik
2002-08-01 17:42   ` John Levon
2002-08-02  0:26     ` Jeff Garzik
2002-08-02 19:19     ` Greg KH
2002-08-04 20:12   ` Nico Schottelius

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=1028203217.32264.44.camel@lemsip \
    --to=gianni@ecsc.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux.nics@intel.com \
    --cc=nico-mutt@schottelius.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