From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: john slee <indigoid@higherplane.net>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: Network hardware: "Network Media Detection"
Date: Sun, 25 Nov 2001 06:54:09 -0500 [thread overview]
Message-ID: <3C00DBE1.7A523308@mandrakesoft.com> (raw)
In-Reply-To: <E167ja2-0004fF-00@carbon.btinternet.com> <9tpiio$n4u$1@cesium.transmeta.com> <20011125224259.A4844@higherplane.net>
john slee wrote:
>
> On Sat, Nov 24, 2001 at 05:47:04PM -0800, H. Peter Anvin wrote:
> > > Hi
> > > I was wondering if there was any way in linux to use what redmond calls
> > > "Network Media Detection"?
> > This is basically taking the interface down when the link disappears
> > (and vice versa.) Rather useful for portable systems. Don't think
> > anyone has implemented it, but it should be easy enough to do.
>
> is there a common field in net_device{} for link state (not just up or
> down, but media type too)?
>
> all the various ethernet drivers seem to handle link changes rather
> differently. being able to notify userspace of media changes in a
> not-driver-specific manner would be nice as links flapping from 10 to
> 100Mbps and back often means problems are afoot.
>
> also i am undecided on _how_ to tell userspace about it... the current
> hotplug system only seems to handle plug/unplug, whereas this is a
> device state change and as such doesn't really fit the mould...
Functions provided by kernel that net drivers should be using:
netif_carrier_on
netif_carrier_off
netif_carrier_ok
ioctl that should be handled by net drivers, to provide link status to
userspace:
ETHTOOL_GLINK
Long term, we want to send a netlink message when link status changes.
Jeff
--
Jeff Garzik | Only so many songs can be sung
Building 1024 | with two lips, two lungs, and one tongue.
MandrakeSoft | - nomeansno
next prev parent reply other threads:[~2001-11-25 11:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-24 20:38 Network hardware: "Network Media Detection" Jeff Snyder
2001-11-25 1:47 ` H. Peter Anvin
2001-11-25 2:52 ` [MOc]cda*mirabilos
2001-11-25 11:42 ` john slee
2001-11-25 11:54 ` Jeff Garzik [this message]
2001-11-25 12:05 ` linux 2.4.13 Kernel and Ext3 vs Ext2 Miguel Maria Godinho de Matos
2001-11-25 12:49 ` François Cami
2001-11-25 13:23 ` James Davies
2001-11-25 13:37 ` arjan
2001-11-25 14:28 ` James Davies
2001-11-25 16:59 ` Stefan Smietanowski
[not found] ` <1006698831.1212624.0@smtp018.mail.yahoo.com>
2001-11-25 14:49 ` Arjan van de Ven
2001-11-25 19:00 ` J Sloan
2001-11-25 21:16 ` Marco Colombo
2001-11-25 18:46 ` J Sloan
2001-11-25 19:49 ` Stefan Smietanowski
2001-11-26 1:20 ` Horst von Brand
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=3C00DBE1.7A523308@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=hpa@zytor.com \
--cc=indigoid@higherplane.net \
--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 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.