From: David Miller <davem@davemloft.net>
To: greg@kroah.com
Cc: david-b@pacbell.net, linux-usb-users@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: OHCI root_port_reset() deadly loop...
Date: Mon, 08 Oct 2007 21:47:27 -0700 (PDT) [thread overview]
Message-ID: <20071008.214727.48799757.davem@davemloft.net> (raw)
In-Reply-To: <20071009043909.GA4940@kroah.com>
From: Greg KH <greg@kroah.com>
Date: Mon, 8 Oct 2007 21:39:09 -0700
> No, nothing cute in udev itself, but it seems that all distros that I
> know of have a "load these modules now" type setting in their init
> scripts that can be used here.
>
> I can't think of a way to enforce this load order on the modules
> themselves due to the fact that OHCI might not even be needed for EHCI
> devices on UHCI (Intel) based chipsets :(
>
> Can anyone else?
The three modules perhaps should be a bundle of whatever ones you have
enabled, and internally we can dispatch the initialization to occur in
the correct order from a top-level module_init().
If the devices need to be initialized in a certain order in a
situation like this, it really seems like it is the kernel's job to
enforce it.
next prev parent reply other threads:[~2007-10-09 4:47 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-07 6:53 OHCI root_port_reset() deadly loop David Miller
2007-10-07 7:31 ` David Brownell
2007-10-07 7:51 ` David Miller
2007-10-08 23:54 ` David Miller
2007-10-09 3:10 ` Greg KH
2007-10-09 3:16 ` David Miller
2007-10-09 3:34 ` David Brownell
2007-10-09 3:42 ` David Miller
2007-10-09 4:39 ` Greg KH
2007-10-09 4:47 ` David Miller [this message]
2007-10-09 5:11 ` Benjamin Herrenschmidt
2007-10-09 6:06 ` Greg KH
2007-10-09 19:22 ` [linux-usb-devel] " David Brownell
2007-10-10 15:32 ` Alan Stern
2007-10-09 5:00 ` David Brownell
2007-10-09 5:23 ` David Miller
2007-10-09 6:43 ` Benjamin Herrenschmidt
2007-10-09 18:48 ` David Brownell
2007-10-09 16:01 ` [Linux-usb-users] " Alan Stern
2007-10-09 17:39 ` Greg KH
2007-10-09 18:42 ` Alan Stern
2007-10-09 18:59 ` David Brownell
2007-10-09 21:27 ` David Miller
2007-10-09 21:43 ` David Brownell
2007-10-09 22:00 ` David Miller
2007-10-10 4:35 ` David Miller
2007-10-15 22:01 ` David Miller
2007-10-15 23:39 ` David Brownell
2007-10-15 23:58 ` David Miller
2007-10-16 15:23 ` Alan Stern
2007-10-16 22:06 ` David Miller
2007-10-16 22:20 ` Greg KH
2007-10-17 15:56 ` Alan Stern
2007-10-16 22:08 ` David Miller
2007-10-17 15:51 ` Alan Stern
2007-10-17 23:03 ` David Miller
2007-10-18 14:28 ` Alan Stern
2007-10-16 18:26 ` David Brownell
2007-10-09 4:09 ` David Brownell
2007-10-09 5:13 ` Benjamin Herrenschmidt
2007-10-09 5:26 ` David Miller
2007-10-09 6:37 ` Benjamin Herrenschmidt
2007-10-09 4:36 ` David Brownell
2007-10-09 4:44 ` David Miller
2007-10-09 16:38 ` David Brownell
2007-10-09 20:41 ` David Miller
2007-10-09 20:46 ` Greg KH
2007-10-09 21:05 ` David Brownell
2007-10-09 21:09 ` David Brownell
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=20071008.214727.48799757.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-users@lists.sourceforge.net \
/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.