public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Dan Hopper <ku4nf@austin.rr.com>
Cc: Andre Hedrick <andre@linux-ide.org>, linux-kernel@vger.kernel.org
Subject: Re: Promise 20265 IDE chip gets detected in wrong order 2.4.x
Date: Wed, 20 Mar 2002 11:32:19 +0100	[thread overview]
Message-ID: <3C986533.3000008@evision-ventures.com> (raw)
In-Reply-To: <20020320045535.GA2242@yoda.dummynet> <Pine.LNX.4.10.10203192105490.525-100000@master.linux-ide.org> <20020320052336.GA2220@yoda.dummynet>

Dan Hopper wrote:
> Andre Hedrick <andre@linux-ide.org> remarked:
> 
>>append="ide=reverse"
> 
> 
> You're right, this works, too, and is a lot easier to remember than
> the override I used before.  
> 
> 
>>Various Mainboard manufacturers do things to place the FAKE-RAID in front
>>of the the legacy south bridge.  This is classic Windows spoofing.
>>
>>
>>>PDC20265: IDE controller on PCI bus 00 dev 68
>>>VP_IDE: IDE controller on PCI bus 00 dev 89
>>
> 
> So, the I/O port assignments don't in fact properly determine the
> assignment order?  I'm gathering from what you're saying that the
> current behavior is related to PCI bus location?

Precisely: The PCI bus detection order matters.


  reply	other threads:[~2002-03-20 10:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-20  4:55 Promise 20265 IDE chip gets detected in wrong order 2.4.x Dan Hopper
2002-03-20  5:10 ` Andre Hedrick
2002-03-20  5:23   ` Dan Hopper
2002-03-20 10:32     ` Martin Dalecki [this message]
2002-03-20 11:15       ` Andre Hedrick
2002-03-20 11:26         ` Martin Dalecki
2002-03-20 11:51           ` Andre Hedrick

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=3C986533.3000008@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=andre@linux-ide.org \
    --cc=ku4nf@austin.rr.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox