From: David Woodhouse <dwmw2@infradead.org>
To: Russell King <rmk@arm.linux.org.uk>
Cc: randy.dunlap@intel.com (Dunlap, Randy), linux-kernel@vger.kernel.org
Subject: Re: USB init order dependencies.
Date: Tue, 07 Nov 2000 18:27:37 +0000 [thread overview]
Message-ID: <14241.973621657@redhat.com> (raw)
In-Reply-To: <200011070726.eA77QfC20051@flint.arm.linux.org.uk>
In-Reply-To: <200011070726.eA77QfC20051@flint.arm.linux.org.uk>
rmk@arm.linux.org.uk said:
> No. As I said elsewhere in this thread, the USB OHCI chip is not
> accessible until other board-specific initialisation has happened.
> This is done via an initcall. Unfortunately, moving usb_init() back
> into init/main.c will mean that USB is again initialised before any
> initcalls, which means for these boards USB will be non-functional
> without additional changes over and above just moving usb_init().
But OHCI init isn't called from usb_init() is it?
The proposal is only to move the single call to usb_init() back into
init/main.c - not to move all the USB initcalls back.
--
dwmw2
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-07 18:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-06 23:53 USB init order dependencies Dunlap, Randy
2000-11-07 7:26 ` Russell King
2000-11-07 18:27 ` David Woodhouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-07 19:02 Dunlap, Randy
2000-11-07 18:48 Dunlap, Randy
2000-11-07 18:50 ` David Woodhouse
2000-11-05 1:36 Dunlap, Randy
2000-11-05 10:03 ` Russell King
2000-10-31 18:10 Dunlap, Randy
2000-11-03 10:38 ` Russell King
2000-11-04 8:24 ` Jeff Garzik
2000-11-04 14:38 ` Russell King
2000-11-04 15:30 ` Jeff Garzik
2000-10-31 17:58 David Woodhouse
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=14241.973621657@redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@intel.com \
--cc=rmk@arm.linux.org.uk \
/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.