[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACVXFVMeUmLh=Tu3PHbgHQNX+c-z50_CoAkdJS_uCw=E3dO2dw@mail.gmail.com>
Date: Sat, 18 Aug 2012 08:58:39 +0800
From: Ming Lei <tom.leiming@...il.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Alan Stern <stern@...land.harvard.edu>,
Fengguang Wu <fengguang.wu@...el.com>,
Bjørn Mork <bjorn@...k.no>,
Oliver Neukum <oneukum@...e.de>,
Sarah Sharp <sarah.a.sharp@...ux.intel.com>,
linux-kernel@...r.kernel.org,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
"Lan, Tianyu" <tianyu.lan@...el.com>
Subject: Re: BUG: unable to handle kernel paging request in usb_match_id()
On Fri, Aug 17, 2012 at 10:42 PM, Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
> On Fri, Aug 17, 2012 at 10:38:16AM -0400, Alan Stern wrote:
>> On Fri, 17 Aug 2012, Ming Lei wrote:
>>
>> > But, if HOTPLUG is not enabled, should device_add() trigger driver probe
>> > further after kernel init is completed? Or even devices should be allowed
>> > to add into system?
>>
>> Indeed, does it make any sense to have USB support at all if HOTPLUG
>> isn't enabled? Should USB select HOTPLUG?
>
> Well, a long time ago people wanted to use USB but not have HOTPLUG
> enabled in their systems for various (odd) embedded systems. As it's
> pretty hard to even turn off HOTPLUG these days, I'd be more likely to
> just remove CONFIG_HOTPLUG entirely given the dynamic nature of almost
> all systems.
It should make sense, otherwise all device id table should not use
__devinit* markings. There are lots of pci driver usage on it.
Thanks,
--
Ming Lei
--
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