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>
Subject: Re: PATCH: IDE - sensible probing for PCI systems
Date: Thu, 23 Jun 2005 23:48:14 +0100 [thread overview]
Message-ID: <1119566026.18655.30.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61L.0506231903170.31113@blysk.ds.pg.gda.pl>
On Iau, 2005-06-23 at 19:22, Maciej W. Rozycki wrote:
> Besides, does a modern i386 really require them? DOS compatibility is no
> longer an issue for commodity hardware and the ISA bridge is gone.
Untrue on both counts
> Apparently the only legacy device still not replaced by anything else is
> the RTC, which is rather surprising as there seems to be a lot of
> reasonable alternatives for I2C available these days and i386 boxes have
> had I2C for quite a while now.
DMA controller, floppy controller, keyboard, serial, mouse, parallel,
some video ports, random other objects on the lpc bus, miscellaneous
motherboard gunge.
> Both IDE and video are distinct PCI devices these days, so there is no
> need for them to hide their decoded address ranges. I've thought that has
> been sorted out.
We still support older machines that are pre PCI even. Most PC systems
also have ranges of non-PCI decoded space that appears in no PCI bar.
Alan
next prev parent reply other threads:[~2005-06-23 22:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-21 12:23 PATCH: IDE - sensible probing for PCI systems Alan Cox
2005-06-21 13:42 ` Maciej W. Rozycki
2005-06-21 14:12 ` Alan Cox
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 [this message]
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=1119566026.18655.30.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.