All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Jones <pjones@redhat.com>
To: Greg KH <gregkh@suse.de>
Cc: Dave Airlie <airlied@gmail.com>,
	Jeff Chua <jeff.chua.linux@gmail.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Scott James Remnant <scott@canonical.com>,
	Kay Sievers <kay.sievers@vrfy.org>, Dave Jones <davej@redhat.com>
Subject: Re: can we move USB_DEVICEFS to non-embedded?
Date: Wed, 08 Jul 2009 11:05:38 -0400	[thread overview]
Message-ID: <4A54B5C2.9000908@redhat.com> (raw)
In-Reply-To: <20090708145625.GA20690@suse.de>

Greg KH wrote:
> On Wed, Jul 08, 2009 at 10:12:08AM -0400, Peter Jones wrote:
>> Greg KH wrote:
>>> On Wed, Jul 08, 2009 at 09:55:04AM -0400, Peter Jones wrote:
>>>> On 07/08/2009 09:52 AM, Peter Jones wrote:
>>>>> On 07/08/2009 06:54 AM, Dave Airlie wrote:
>>>>>
>>>>>> I'm not quite sure if something in the F11 initrd needs usbfs for
>>>>>> something (cc'ed Peter)
>>>>> Not a thing.
>>>> Actually, I take it back.  We do mount usbfs, and we examine
>>>> /proc/bus/usb/devices as a heuristic to try and determine if
>>>> all the devices have been enumerated.
>>> How can you ever know if all devices are enumerated as you don't know
>>> how many devices will be showing up?
>> You don't, that's why I said it's a heuristic.  But basically, we have a 
>> timeout, and if the device list doesn't change in that amount of time, we
>> call it done.
>>
>> It's not the best technique ever, but it does work.
> 
> Works for what?  Why would you want to delay your boot process like
> this?

Because otherwise when we actually get to mounting the root filesystem,
the device *isn't yet present*.

>>>> So that could be related to what you're seeing.
>>> That file is now available in /sys/kernel/debug/usb/devices if you
>>> really need it.
>> Oh, okay.  I can change it to use that then.
>>
>>> But I would think that you do not.
>> Well, we pretty much do until we switch to dracut.
> 
> What is dracut and why would it change this?

It's the replacement for mkinitrd, and it's using hotplug events for
this stuff instead.

> As no other distro does this kind of waiting, I'm a bit confused as to
> the need for it.

Good to know you pay attention to what's going on in the Linux world.

-- 
   Peter

  reply	other threads:[~2009-07-08 15:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23  5:11 can we move USB_DEVICEFS to non-embedded? Jeff Chua
2009-06-23  8:17 ` Scott James Remnant
2009-06-23 14:42 ` Greg KH
2009-06-23 15:29   ` Jeff Chua
2009-06-23 15:39     ` Greg KH
2009-07-08 10:54       ` Dave Airlie
2009-07-08 11:03         ` Kay Sievers
2009-07-08 11:20           ` Dave Airlie
2009-07-08 11:42             ` Scott James Remnant
2009-07-08 13:00             ` Greg KH
2009-07-08 13:52         ` Peter Jones
2009-07-08 13:55           ` Peter Jones
2009-07-08 14:04             ` Greg KH
2009-07-08 14:12               ` Peter Jones
2009-07-08 14:56                 ` Greg KH
2009-07-08 15:05                   ` Peter Jones [this message]
2009-07-08 15:47                     ` Greg KH
2009-07-08 21:23                       ` Dave Airlie
2009-07-09  0:43                         ` Jeff Chua
2009-07-09  1:59                           ` Randy Dunlap
2009-07-09  2:31                             ` Jeff Chua
2009-07-09  3:01                               ` Randy Dunlap
2009-07-09 12:12                                 ` Jeff Chua
2009-07-09  1:33                         ` Greg KH
2009-07-08 15:12               ` Bill Nottingham
2009-07-08 15:44                 ` Greg KH

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=4A54B5C2.9000908@redhat.com \
    --to=pjones@redhat.com \
    --cc=airlied@gmail.com \
    --cc=davej@redhat.com \
    --cc=gregkh@suse.de \
    --cc=jeff.chua.linux@gmail.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=scott@canonical.com \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.