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: Thu, 06 Jun 2002 17:16:10 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-102338379432086@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-102297360623547@msgid-missing>
Andries.Brouwer@cwi.nl wrote:
>>I seem to recall pointing you at usb-storage once already,
>>as the only USB driver today which needs to do such stuff.
>>It has a notion of device identity, based ISTR on serial
>>numbers, and saves that state. UTSL.
>
>
> You quote this as an example of how to do things.
> I am not especially happy with the results.
My point was only that when asked for an example,
I had already provided one ... :)
You're saying you don't like the model adopted by
usb-storage, which is your prerogative. The person
to talk to about that is Matt Dharm.
> My experience: take a handful of compact flash card readers,
> plug them randomly into some hubs, take a handful of compact
> flash cards, plug them randomly into some readers. Now remove
> and repeat. I find it impossible to predict which device will
> get which name. Sometimes the name goes with the card, sometimes
> with the reader, sometimes neither of the two, sometimes both(!).
That does seem troublesome. It should be one or the other,
consistently. And "both" seems buglike.
> (Yes, it happens that I access the same card both via sdc and sde.)
> Probably things would become clear if I would read the code,
> but I haven't done so yet.
>
> Andries
>
>
> [Names that go with the card are really confusing. It is as if
> one has A:/B:, that is fd0/fd1, and the name of the floppy reader
> depends on the floppy inserted, so that one has to remember the
> history. Bad.]
Named media is one of the standard models for volume management,
and I'm used to seeing that be done without regard to low-level
device naming. For USB, there's an additional issue of being able
to assign names to the devices ... like (external) "fd0" is "fd0"
no matter which connector it's plugged in to, if it's got a serial
number providing some notion of identity.
- 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
next prev parent reply other threads:[~2002-06-06 17:16 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
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 [this message]
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-102338379432086@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).