From: Matthew Wilcox <matthew@wil.cx>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Pekka J Enberg <penberg@cs.helsinki.fi>,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
linux-kernel@vger.kernel.org, dsd@gentoo.org,
mdharm-usb@one-eyed-alien.net, linux-usb@vger.kernel.org,
vegardno@ifi.uio.no, James.Bottomley@hansenpartnership.com,
linux-scsi@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: [RFC/PATCH] usb-storage: wait for device scanning before mounting root
Date: Fri, 20 Jun 2008 09:31:37 -0600 [thread overview]
Message-ID: <20080620153137.GT4392@parisc-linux.org> (raw)
In-Reply-To: <19f34abd0806200815t49b59df9sd9567b52482eaee3@mail.gmail.com>
On Fri, Jun 20, 2008 at 05:15:43PM +0200, Vegard Nossum wrote:
> On Thu, Jun 19, 2008 at 11:39 PM, Alan Stern <stern@rowland.harvard.edu> wrote:
> > As I recall, it died because the whole notion was very poorly defined
> > to begin with. The idea was to stop waiting when all the SCSI buses
> > had been scanned -- but there's no way to know when that occurs because
> > new buses can be added at any time.
>
> Can you please explain why this is?
The USB spec doesn't mandate a minimum time before devices come
available. There's no way for the device to say "I'm here, I will be
providing USB Storage, but I'm not ready yet". So we can't know when
we've enumerated all the USB devices on the system.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-06-20 15:31 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 20:21 [RFC/PATCH] usb-storage: wait for device scanning before mounting root Pekka J Enberg
2008-04-24 21:08 ` Alan Stern
2008-04-24 21:25 ` Pekka J Enberg
2008-04-24 22:56 ` Greg KH
2008-04-24 23:30 ` Matthew Dharm
2008-04-25 6:30 ` Pekka J Enberg
2008-04-25 7:04 ` Matthew Dharm
2008-04-25 8:19 ` Pekka J Enberg
2008-04-25 15:35 ` Matthew Dharm
2008-04-25 16:05 ` Greg KH
2008-04-25 6:09 ` Pekka J Enberg
2008-04-25 7:53 ` Stefan Richter
2008-04-25 8:15 ` Pekka J Enberg
2008-04-25 9:11 ` Matthew Wilcox
2008-06-19 18:23 ` Matthew Wilcox
2008-06-19 18:39 ` Stefan Richter
2008-06-19 18:43 ` Stefan Richter
2008-06-19 18:54 ` Matthew Wilcox
2008-06-19 19:52 ` Matthew Dharm
2008-06-19 20:49 ` Matthew Wilcox
2008-06-19 21:19 ` Stefan Richter
2008-06-19 19:54 ` Stefan Richter
2008-06-19 20:22 ` Matthew Wilcox
2008-06-19 20:34 ` Stefan Richter
2008-06-19 21:39 ` Alan Stern
2008-06-19 23:13 ` David Brownell
2008-06-20 9:53 ` Gabor Gombas
2008-06-20 14:14 ` Matthew Dharm
2008-06-20 15:15 ` Vegard Nossum
2008-06-20 15:31 ` Matthew Wilcox [this message]
2008-06-20 15:42 ` Alan Stern
2008-06-20 16:37 ` Stefan Richter
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=20080620153137.GT4392@parisc-linux.org \
--to=matthew@wil.cx \
--cc=James.Bottomley@hansenpartnership.com \
--cc=dsd@gentoo.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mdharm-usb@one-eyed-alien.net \
--cc=penberg@cs.helsinki.fi \
--cc=stefanr@s5r6.in-berlin.de \
--cc=stern@rowland.harvard.edu \
--cc=vegard.nossum@gmail.com \
--cc=vegardno@ifi.uio.no \
/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