All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nico Schottelius <nico-mutt@schottelius.org>
To: linux.nics@intel.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: network driver informations [general NIC, Wireless and e100]
Date: Wed, 31 Jul 2002 23:24:26 +0200	[thread overview]
Message-ID: <20020731212426.GA3342@schottelius.org> (raw)

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

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.

The point in fact is, looking into dmesg for connection status is definitly
wrong IMHO. It's neither a clean access nor easy to watch for applications.

So what do you think about /proc/net/<DEVNAME> support for status ?

As far as I can see this is partly implemented in /proc/net/wireless
or in /proc/net/dev.
Adding another column in the latter would do the job, too.

Anyways, just an idea.

Hope to hear your critics,

Nico


-- 
Changing mail address: please forget all known @pcsystems.de addresses.

Please send your messages pgp-signed and/or pgp-encrypted (don't encrypt mails
to mailing list!). If you don't know what pgp is visit www.gnupg.org.
(public pgp key: ftp.schottelius.org/pub/familiy/nico/pgp-key)

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2002-08-01  7:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-31 21:24 Nico Schottelius [this message]
2002-08-01 12:00 ` network driver informations [general NIC, Wireless and e100] Gianni Tedesco
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=20020731212426.GA3342@schottelius.org \
    --to=nico-mutt@schottelius.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux.nics@intel.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.