mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: randy.dunlap@intel.com (Dunlap, Randy)
Cc: linux-kernel@vger.kernel.org
Subject: Re: USB init order dependencies.
Date: Sun, 5 Nov 2000 10:03:29 +0000 (GMT)	[thread overview]
Message-ID: <200011051003.eA5A3TW06863@flint.arm.linux.org.uk> (raw)
In-Reply-To: <D5E932F578EBD111AC3F00A0C96B1E6F07DBDC2C@orsmsx31.jf.intel.com> from "Dunlap, Randy" at Nov 04, 2000 05:36:51 PM

Dunlap, Randy writes:
> While Jeff and I basically agree on the short-term
> solution (if one is still needed, altho I'm not aware of
> any init order problems in USB in 2.4.0-test10), my
> recollection of Linus's preference (without
> looking it up) is to remove the calls from init/main.c
> and to use __initcalls.

The problem for ARM is that Linux does a lot of the initialisation for
some machines, which basically means the hardware isn't setup for access
to the USB device if the USB initialisation was placed in init/main.c
(this initialisation is done by the very first initcall on ARM).  However,
that said, we may be able to get away with only adding hw_sa1100_init()
before the USB call, but this is only one family of the ARM machine types.

BTW, I've long lost track of what the original problem that sparked off
this thread was, does someone have a quick reference to it?  (please
reply in private mail).  Thanks.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |         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/

  reply	other threads:[~2000-11-05 12:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-05  1:36 Dunlap, Randy
2000-11-05 10:03 ` Russell King [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-06 23:53 Dunlap, Randy
2000-11-07  7:26 ` Russell King
2000-11-07 18:27   ` David Woodhouse
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=200011051003.eA5A3TW06863@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®