public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: "Richard F. Rebel" <rrebel@whenu.com>
Cc: kwhite@austin.ibm.com, linux-scsi@vger.kernel.org
Subject: Re: Boot order of LSI MPT Fusion devices controllable?
Date: Tue, 30 Nov 2004 19:59:32 +0000	[thread overview]
Message-ID: <20041130195932.GA29035@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <1101843791.1779.1048.camel@rebel.corp.whenu.com>

On Tue, Nov 30, 2004 at 02:43:11PM -0500, Richard F. Rebel wrote:
> Earlier someone responded to the tune that I needed to change the PCI
> boot order, and unless the bios allows me to change that,  I have to
> move the cards around in the chassis.  I have a cage monkey trying that
> now.

I think you misunderstood.  The PCI ID is determined by how the PCI
slot is wired up -- there's nothing the BIOS can do to affect that.

[hmm.  if you're particularly perverse, i suppose you could route the
select lines through a chip that the BIOS could reprogram ... never
seen it done though.]

-- 
"Next the statesmen will invent cheap lies, putting the blame upon 
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince 
himself that the war is just, and will thank God for the better sleep 
he enjoys after this process of grotesque self-deception." -- Mark Twain

  reply	other threads:[~2004-11-30 19:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-30 17:20 Boot order of LSI MPT Fusion devices controllable? Richard F. Rebel
2004-11-30 17:54 ` Matthew Wilcox
2004-12-01  3:31 ` kwhite
2004-11-30 19:40   ` Christoph Hellwig
2004-11-30 19:43   ` Richard F. Rebel
2004-11-30 19:59     ` Matthew Wilcox [this message]
2004-11-30 20:48     ` Mike Anderson
2004-11-30 21:55       ` Richard F. Rebel
  -- strict thread matches above, loose matches on Subject: below --
2004-11-30 22:15 todd.reichert

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=20041130195932.GA29035@parcelfarce.linux.theplanet.co.uk \
    --to=matthew@wil.cx \
    --cc=kwhite@austin.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rrebel@whenu.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