All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Matt_Domsch@Dell.com, greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: Removal of pci_find_* in 2.5
Date: Sat, 13 Jul 2002 15:33:20 -0400	[thread overview]
Message-ID: <3D308080.20306@mandrakesoft.com> (raw)
In-Reply-To: 3D307F68.7080703@mandrakesoft.com

Jeff Garzik wrote:
> Everything you are saying here just convinces me more than we should do 
> this stuff in initramfs.  At the summit Linus endorsed using 
> /sbin/hotplug when storage devices appear... combine that with 
> initramfs, and you should have all you need to handle whatever complex 
> scenario you come up with.  It sounds straightforward to have some 
> find-the-root-device code in initramfs that can contain "if 
> (dell_mainboard)" code all over the place.



IOW, strive to make order of kernel device initialization irrelevant -- 
init the kernel drivers, then figure out the boot device.

	Jeff



  reply	other threads:[~2002-07-13 19:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-13  4:04 Removal of pci_find_* in 2.5 Matt_Domsch
2002-07-13  4:41 ` Jeff Garzik
2002-07-13  5:09   ` Greg KH
2002-07-13 14:35   ` Alan Cox
2002-07-13 15:37     ` Jeff Garzik
2002-07-13 17:06       ` Alan Cox
2002-07-13 19:28         ` Jeff Garzik
2002-07-13 19:33           ` Jeff Garzik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-16 19:23 Matt_Domsch
2002-07-13 13:13 Matt_Domsch
2002-07-13  0:36 Greg KH
2002-07-13  2:23 ` Alan Cox
2002-07-13  1:12   ` David S. Miller
2002-07-13 14:46     ` Alan Cox
2002-07-13 20:52       ` David S. Miller
2002-07-13 13:45         ` Benjamin Herrenschmidt
2002-07-15  5:25           ` David S. Miller
2002-07-16  0:26             ` Greg KH
2002-07-14 20:07 ` Eric W. Biederman
2002-07-16  0:25   ` Greg KH
2002-07-16 10:56     ` Eric W. Biederman
2002-07-16 17:33       ` Patrick Mochel
2002-07-17 12:41         ` Eric W. Biederman

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=3D308080.20306@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=Matt_Domsch@Dell.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.