From: Doug Ledford <dledford@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Matt_Domsch@Dell.com, andmike@us.ibm.com, cliffw@osdl.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-megaraid-devel@Dell.com
Subject: Re: 2.5.44 compile problem: MegaRAID driver
Date: Mon, 21 Oct 2002 18:25:00 -0400 [thread overview]
Message-ID: <20021021222500.GK28914@redhat.com> (raw)
In-Reply-To: <1035239507.27309.259.camel@irongate.swansea.linux.org.uk>
On Mon, Oct 21, 2002 at 11:31:47PM +0100, Alan Cox wrote:
> On Mon, 2002-10-21 at 23:10, Matt_Domsch@Dell.com wrote:
> > The host reordering is to solve the same problem that EDD helps us solve now
> > - it makes sure that in systems with megaraid adapters that also have BIOS
> > enabled (thus have the bootable logical drive on that card) that it shows up
>
> You can fix the ordering up still if you want within cards of a given
> driver type. i2o does this to get its bios boot volume first. Just do it
> by probing your devices, then registering them in the order you want,
> not by mashing the list
This is, umm, a non-elegant way of handling things once you switch your
driver to the new PCI driver probe model :-(
Of course, I'm personally of the opinion that people need to quite
thinking in terms of host order anyway and let things like mount by volume
solve this issue anyway. It's cleaner, it works regardless of the driver,
and it puts the burden of finding the right root partition in user space
where it's easier to fix up should things change, etc. Just my opinion.
--
Doug Ledford <dledford@redhat.com> 919-754-3700 x44233
Red Hat, Inc.
1801 Varsity Dr.
Raleigh, NC 27606
next prev parent reply other threads:[~2002-10-21 22:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 22:10 2.5.44 compile problem: MegaRAID driver Matt_Domsch
2002-10-21 22:31 ` Alan Cox
2002-10-21 22:25 ` Doug Ledford [this message]
2002-10-21 22:29 ` Matt Domsch
2002-10-21 22:33 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-10-21 20:31 Cliff White
2002-10-21 21:28 ` Mike Anderson
2002-10-21 22:32 ` Cliff White
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=20021021222500.GK28914@redhat.com \
--to=dledford@redhat.com \
--cc=Matt_Domsch@Dell.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andmike@us.ibm.com \
--cc=cliffw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-megaraid-devel@Dell.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