public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: "Dunlap, Randy" <randy.dunlap@intel.com>,
	"'David Woodhouse'" <dwmw2@infradead.org>,
	torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: USB init order dependencies.
Date: Sat, 04 Nov 2000 03:24:39 -0500	[thread overview]
Message-ID: <3A03C7C7.87CE750F@mandrakesoft.com> (raw)
In-Reply-To: <200011031038.eA3Accj30162@flint.arm.linux.org.uk>

Russell King wrote:
> 
> Dunlap, Randy writes:
> > David is entitled to his opinion (IMO).
> > And I dislike this patch, as he and I have already discussed.
> >
> > Short of fixing the link order, I like Jeff's suggestion
> > better (if it actually works, that is):  go back to the
> > way it was a few months ago by calling usb_init()
> > from init/main.c and making the module_init(usb_init);
> > in usb.c conditional (#ifdef MODULE).
> 
> However, that breaks the OHCI driver on ARM.  Unless we're going to start
> putting init calls back into init/main.c so that we can guarantee the order
> of init calls which Linus will not like, you will end up with a lot of ARM
> guys complaining.
> 
> Linus, your opinion would be helpful at this point.

Back when some of the initial USB initcall stuff started appearing,
there were similar discussions, similar problems, and similar
solutions.  I was also wondering how fbdev (which needs to give you a
console ASAP) would work with initcalls, etc.  At the time (~6 months
ago?), Linus' opinion was basically "if the link order hacking starts to
get ugly, just put it in init/main.c"  So, Randy really should be
calling the quoted text above "Linus' suggestion" ;-)

Putting a call into init/main.c isn't a long term solution, but it
should get us there for 2.4.x...  init/main.c is also the best solution
for ugly cross-directory link order dependencies.  I would say the link
order of foo.o's in linux/Makefile is the most delicate/fragile of all
the Makefiles...  touching linux/Makefile link order this close to 2.4.0
is asking for trouble.  Compared to that, adding a few lines to
init/main.c isn't so bad.

IMHO,

	Jeff


-- 
Jeff Garzik             | Dinner is ready when
Building 1024           | the smoke alarm goes off.
MandrakeSoft            |	-/usr/games/fortune
-
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-04  8:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-31 18:10 USB init order dependencies Dunlap, Randy
2000-11-03 10:38 ` Russell King
2000-11-04  8:24   ` Jeff Garzik [this message]
2000-11-04 14:38     ` Russell King
2000-11-04 15:30       ` Jeff Garzik
  -- 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-11-05  1:36 Dunlap, Randy
2000-11-05 10:03 ` Russell King
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=3A03C7C7.87CE750F@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@intel.com \
    --cc=rmk@arm.linux.org.uk \
    --cc=torvalds@transmeta.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