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?
Thanks,
-Ed
----------------------------------------------------------------
Ed Vance edv (at) macrolink (dot) com
Macrolink, Inc. 1500 N. Kellogg Dr Anaheim, CA 92807
----------------------------------------------------------------
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