From: Greg KH <greg@kroah.com>
To: Ed Vance <EdV@macrolink.com>
Cc: "'linux-kernel'" <linux-kernel@vger.kernel.org>
Subject: Re: hotplug (was devfs)
Date: Wed, 13 Nov 2002 10:45:15 -0800 [thread overview]
Message-ID: <20021113184515.GE5446@kroah.com> (raw)
In-Reply-To: <11E89240C407D311958800A0C9ACF7D1A33CA8@EXCHANGE>
On Wed, Nov 13, 2002 at 10:45:43AM -0800, Ed Vance wrote:
> On Wed, November 13, 2002 at 10:05 AM, Greg KH wrote:
> >
> > On Wed, Nov 13, 2002 at 06:06:06PM +0000, Nick Craig-Wood wrote:
> > >
> > > So I'll be able to say usb bus1/1/4/1 port 3 should be /dev/ttyUSB15
> > > and it will always be that port? That would be perfect.
> >
> > Yes, that is the goal.
> >
>
> Do you expect that goal to eventually be applied to CompactPCI Hot-Swap
> bus/slot port 3?
Yes, in a round-about way. If the device that is in that specific slot
with that specific port, registers with, for example, the network
subsystem, and we have decided that anything in that slot should be
called "eth42", then we can do that based on the topology of the device.
It really depends on the device that is existing in a specific location
(network, scsi, etc.) and not so much as the specific location will
always be a network card called "ethX", as you have to look at the type
of device too.
Does that make sense?
I can tell it's getting to be the time to start writing all of this down
for people to hash out... :)
thanks,
greg k-h
next prev parent reply other threads:[~2002-11-13 18:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-13 18:45 hotplug (was devfs) Ed Vance
2002-11-13 18:45 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-13 18:59 Ed Vance
2002-11-12 9:32 devfs Ian Molton
2002-11-12 9:49 ` devfs john slee
2002-11-12 10:01 ` devfs Sean Neakums
2002-11-12 12:51 ` devfs Oliver Neukum
2002-11-13 10:48 ` hotplug (was devfs) Nick Craig-Wood
2002-11-13 17:02 ` Greg KH
2002-11-13 18:06 ` Nick Craig-Wood
2002-11-13 18:04 ` Greg KH
2002-11-14 11:46 ` Oliver Neukum
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=20021113184515.GE5446@kroah.com \
--to=greg@kroah.com \
--cc=EdV@macrolink.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox