linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: hotplugging to deal with firmware download
Date: Tue, 04 Jun 2002 19:32:49 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-102322040325281@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-102297360623547@msgid-missing>

>>You need the ability to reidentify for simple things like setting the 
>>correct IP on the correct network adapter, or correct resolution
>>on the correct camera.
>  
> I agree.  Then use something unique in the device like I said in a
> different message: device physical path, serial number, mac address, fs
> label, etc.

For network devices this is exposed through struct ethtool_drvinfo;
there's a bus_info field.  In 2.5 most of the USB networking drivers
(it should be/become all!) use this to advantage; there's a new
API, usb_make_path(), that provides a stable physical path.

Admittedly many userspace tools ignore that, as well as the ethernet
address, in favor of nasty unstable names like "eth0".  But I know
that somewhere there's a tool that'll rename interfaces, so that those
tools which expect "eth0" style names to be stable won't need to break
too badly ... :)


> But only use the physical path if that's your last resort, as it's the
> most unstable.  This is the main reason the USB printer spec started
> specifying that all USB printers need to have a serial number.  To help
> uniquely identify them.

Actually in the "typical" suspend/resume case (like powerdown overnight,
or over lunch) I think the physical path is unlikely to change.

Though there are certainly cases like suspend, carry laptop to new site,
hook up to new printer ... so it's certainly true that it's a good idea
to use the physical path in conjunction with other data (like device
vendor and product IDs) if that's all you have to work with.

- Dave





_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2002-06-04 19:32 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-01 23:16 [linux-usb-devel] Re: hotplugging to deal with firmware download Brad Hards
2002-06-02  5:50 ` Oliver Neukum
2002-06-02  8:19 ` Oliver Neukum
2002-06-02 11:11 ` Brad Hards
2002-06-02 17:16 ` David Brownell
2002-06-02 21:59 ` Oliver Neukum
2002-06-02 22:21 ` Brad Hards
2002-06-03  4:18 ` Oliver Neukum
2002-06-03 17:52 ` Greg KH
2002-06-03 21:00 ` Oliver Neukum
2002-06-03 21:55 ` Greg KH
2002-06-03 22:02 ` David Brownell
2002-06-03 22:26 ` Oliver Neukum
2002-06-03 22:35 ` Greg KH
2002-06-03 22:37 ` Greg KH
2002-06-03 22:48 ` Oliver Neukum
2002-06-03 22:58 ` Oliver Neukum
2002-06-03 23:05 ` Greg KH
2002-06-03 23:30 ` Oliver Neukum
2002-06-03 23:40 ` Greg KH
2002-06-04  8:06 ` Oliver Neukum
2002-06-04 19:32 ` David Brownell [this message]
2002-06-04 19:44 ` David Brownell
2002-06-05 11:45 ` Oliver Neukum
2002-06-05 14:19 ` David Brownell
2002-06-05 14:32 ` Oliver Neukum
2002-06-05 14:54 ` David Brownell
2002-06-05 21:48 ` Oliver Neukum
2002-06-06  0:25 ` David Brownell
2002-06-06  9:04 ` Andries.Brouwer
2002-06-06 12:54 ` Oliver Neukum
2002-06-06 14:55 ` Oliver Neukum
2002-06-06 17:16 ` David Brownell
2002-06-06 19:19 ` Andries.Brouwer

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-102322040325281@msgid-missing \
    --to=david-b@pacbell.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).