[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080806131729.6384550c@infradead.org>
Date: Wed, 6 Aug 2008 13:17:29 -0700
From: Arjan van de Ven <arjan@...radead.org>
To: Alan Stern <stern@...land.harvard.edu>
Cc: Simon Arlott <simon@...e.lp0.eu>,
Rene Herman <rene.herman@...access.nl>,
<linux-kernel@...r.kernel.org>, <mingo@...e.hu>,
Daniel Walker <dwalker@...sta.com>,
USB list <linux-usb@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...e.de>
Subject: Re: [PATCH RFC] USB: Add HCD fastboot
On Wed, 6 Aug 2008 16:09:21 -0400 (EDT)
Alan Stern <stern@...land.harvard.edu> wrote:
> On Wed, 6 Aug 2008, Arjan van de Ven wrote:
>
> > On Wed, 6 Aug 2008 15:49:27 -0400 (EDT)
> > Alan Stern <stern@...land.harvard.edu> wrote:
> >
> > > On Wed, 6 Aug 2008, Simon Arlott wrote:
> > >
> > > > > Wouldn't it be much simpler, and less objectionable, to do
> > > > > what I suggested earlier? That is, add a 5-second delay at
> > > > > the start of hub_thread() in drivers/usb/core/hub.c. No
> > > > > messing with Makefiles, no changes to the initcall scheduling.
> > > >
> > > > Aside from 5 seconds being too long, and anything less being a
> > > > race between hub_thread() and driver initcalls, it doesn't
> > > > improve anything because it'll still have to wait for the
> > > > devices to finish initialising in userspace instead.
> > >
> > > Why is 5 seconds too long? Too long for what?
> >
> > because I'm done booting to full UI in that time.
> >
> > it's forever.
>
> This doesn't answer my question. Why does the fact that you're
> already in the UI after 5 seconds mean that 5 seconds is too long to
> delay the start of khubd?
because it means that while the rest of boot is done and the system
idle, the mouse and keyboard aren't going to work.
--
If you want to reach me at my work email, use arjan@...ux.intel.com
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists