From: Matthew Dharm <mdharm-usb@one-eyed-alien.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Network hotplug semantics
Date: Thu, 08 Feb 2001 07:02:11 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98161573514987@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
Given the nature of 10BaseT (being stateless on the wire), I would say that
the interface should be signalled at the presence of hardware, not at the
presence of link.
Another way to look at this is the following: I can't see if my wire is
connected to a switch. I _can_ see that the KLSI unit is attached to my
computer.
Matt
On Thu, Feb 08, 2001 at 06:03:34PM +1100, Brad Hards wrote:
> Situation: USB ethernet adapter (in my case, a KLSI one).
>
> Should the interface (e.g. ethX) be signalled when the device is plugged
> in to the USB port, or when the electrical connection of the 10BaseT
> wire is made? What counts as "plugged" in this case?
>
> Brad
>
> _______________________________________________
> Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
> Linux-hotplug-devel@lists.sourceforge.net
> http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
--
Matthew Dharm Home: mdharm-usb@one-eyed-alien.net
Maintainer, Linux USB Mass Storage Driver
I'm just trying to think of a way to say "up yours" without getting fired.
-- Stef
User Friendly, 10/8/1998
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2001-02-08 7:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 7:02 Matthew Dharm [this message]
2001-02-08 7:03 ` Network hotplug semantics Brad Hards
2001-02-08 8:32 ` Oliver Neukum
2001-02-09 0:28 ` David Brownell
2001-02-09 1:27 ` Andrew Morton
2001-02-10 3:46 ` Brad Hards
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=marc-linux-hotplug-98161573514987@msgid-missing \
--to=mdharm-usb@one-eyed-alien.net \
--cc=linux-hotplug@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).