From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, akpm@osdl.org
Subject: Re: PATCH: IDE - sensible probing for PCI systems
Date: Tue, 21 Jun 2005 15:12:32 +0100 [thread overview]
Message-ID: <1119363150.3325.151.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61L.0506211422190.9446@blysk.ds.pg.gda.pl>
On Maw, 2005-06-21 at 14:42, Maciej W. Rozycki wrote:
> On Tue, 21 Jun 2005, Alan Cox wrote:
>
> > Old ISA/VESA systems sometimes put tertiary IDE controllers at addresses
> > 0x1e8, 0x168, 0x1e0 or 0x160. Linux thus probes these addresses on x86
> > systems. Unfortunately some PCI systems now use these addresses for
> > other purposes which leads to users seeing minute plus hangs during boot
> > or even crashes.
>
> Are these addresses visible in BARs?
Sometimes but often not. They tend to be below the PCI range used by the
systems but belonging to onboard "magic"
> FYI, for MIPS for machines with a PCI bus we only probe for ISA IDE ports
> on if there's a PCI-ISA or PCI-EISA bridge somewhere there. This might be
> a good idea for the i386 and probably any platform using PCI as well.
The primary/secondary ISA ports show up in PC systems because of the PCI
IDE class devices being in compatibility mode not native mode (so you
can still run old OS's). There are also a couple of older weird cases.
The PCI layer code is smart enough to figure out when a PCI and an ISA
probe find the same device and to put the entire thing together properly
so that aspect of it is ok.
For the 3rd and higher ports probing them isn't safe on a PCI box
regardless of the presence of ISA bridges so I don't think we need the
extra complexity - or am I missing something ?
next prev parent reply other threads:[~2005-06-21 14:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-21 12:23 Alan Cox
2005-06-21 13:42 ` Maciej W. Rozycki
2005-06-21 14:12 ` Alan Cox [this message]
2005-06-21 15:10 ` Maciej W. Rozycki
2005-06-21 18:46 ` Alan Cox
2005-06-23 18:22 ` Maciej W. Rozycki
2005-06-23 22:48 ` Alan Cox
2005-06-24 11:52 ` Maciej W. Rozycki
2005-06-24 22:41 ` Jeff Garzik
2005-06-27 14:18 ` Maciej W. Rozycki
2005-06-27 20:31 ` Bill Davidsen
2005-06-25 12:32 ` Alan Cox
2005-06-27 14:55 ` Maciej W. Rozycki
2005-06-27 16:24 ` Russell King
2005-06-27 19:54 ` 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=1119363150.3325.151.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.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
Powered by JetHome