From: Russell King <rmk@arm.linux.org.uk>
Message-Id: <200011070726.eA77QfC20051@flint.arm.linux.org.uk>
Subject: Re: USB init order dependencies.
To: randy.dunlap@intel.com (Dunlap, Randy)
Date: Tue, 7 Nov 2000 07:26:41 +0000 (GMT)
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <D5E932F578EBD111AC3F00A0C96B1E6F07DBDC46@orsmsx31.jf.intel.com> from "Dunlap, Randy" at Nov 06, 2000 03:53:26 PM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org

Dunlap, Randy writes:
> I'm not following your argument very well.  I've read it
> and reread it several times.
> Does adding a call to usb_init() in init/main.c cause
> USB to be init 2 times?

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().

I hope this helps you understand the problem.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |         Russell King        rmk@arm.linux.org.uk      --- ---
  | | | | http://www.arm.linux.org.uk/personal/aboutme.html   /  /  |
  | +-+-+                                                     --- -+-
  /   |               THE developer of ARM Linux              |+| /|\
 /  | | |                                                     ---  |
    +-+-+ -------------------------------------------------  /\\\  |
-
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/