mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: 76306.1226@compuserve.com, linux-kernel@vger.kernel.org
Subject: Re: Problem: 2.4.20, 2.5.66 have different IDE channel order
Date: Tue, 15 Apr 2003 14:50:05 -0700	[thread overview]
Message-ID: <20030415145005.20383a70.rddunlap@osdl.org> (raw)
In-Reply-To: <1050439381.28591.15.camel@dhcp22.swansea.linux.org.uk>

On 15 Apr 2003 21:43:02 +0100 Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

| On Maw, 2003-04-15 at 19:33, Chuck Ebbert wrote:
| >   Well, that matches what 2.4 does:
| > 
| > 
| > 00:0d.1 IDE interface: Intel Corp. 82371SB PIIX3 IDE [Natoma/Triton II]
| > 00:10.0 Unknown mass storage controller: Promise Technology, Inc. 20268 (rev 02)
| > 01:0b.0 Unknown mass storage controller: Triones Technologies, Inc. HPT366 / HPT370 (rev 03)
| > 
| > 
| >   2.5 nonmodular seems to be doing it in BIOS order  -- the HPT370 BIOS
| > initializes before the Promise (and won't let it boot but I can deal
| > with that.)  I'll probably replace it with a PDC20262 before looking
| 
| Im a bit puzzled by this because it does look like a bug. Our pci scan code hasnt changed
| that materially. I assume the promise and hpt are both plug in cards >

but something also changed NIC interface ordering (according to davej et al)...
so maybe it's deep inside PCI bus scanning.

--
~Randy

  reply	other threads:[~2003-04-15 21:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-15 18:33 Chuck Ebbert
2003-04-15 20:43 ` Alan Cox
2003-04-15 21:50   ` Randy.Dunlap [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-17  8:43 Chuck Ebbert
2003-04-15  0:51 Chuck Ebbert
2003-04-15 11:23 ` Alan Cox

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=20030415145005.20383a70.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=76306.1226@compuserve.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 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®