From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Bjorn Helgaas <bjorn.helgaas@hp.com>,
B.Zolnierkiewicz@elka.pw.edu.pl, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: [PATCH] IDE: don't offer IDE_GENERIC on ia64
Date: Tue, 16 Aug 2005 15:05:52 +0100 [thread overview]
Message-ID: <1124201152.17555.36.camel@localhost.localdomain> (raw)
In-Reply-To: <58cb370e050816030248e6283c@mail.gmail.com>
On Maw, 2005-08-16 at 12:02 +0200, Bartlomiej Zolnierkiewicz wrote:
> On 8/11/05, Christoph Hellwig <hch@infradead.org> wrote:
> > On Thu, Aug 11, 2005 at 02:24:43PM -0600, Bjorn Helgaas wrote:
> > > IA64 boxes only have PCI IDE devices, so there's no need to blindly poke
> > > around in I/O port space. Poking at things that don't exist causes MCAs
> > > on HP ia64 systems.
> >
> > Maybe it should instead depend on those systems where it is available.
> > Anything but X86?
>
> Don't forget that arch specific drivers use IDE_GENERIC *indirectly*
> to probe for devices.
Just about everything wants IDE GENERIC. Most of them want the probe
address providing function to simply be "return 0" or the two 'magic'
PCI bus legacy addresses. Probably only ia-32 wants to poke other
addresses and even that now checks for non-PCI first
next prev parent reply other threads:[~2005-08-16 13:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 20:24 [PATCH] IDE: don't offer IDE_GENERIC on ia64 Bjorn Helgaas
2005-08-11 20:34 ` Christoph Hellwig
2005-08-11 20:37 ` Bjorn Helgaas
2005-08-12 19:41 ` Jan Engelhardt
2005-08-16 10:02 ` Bartlomiej Zolnierkiewicz
2005-08-16 14:05 ` Alan Cox [this message]
2005-08-11 20:36 ` Jeff Garzik
2005-08-11 20:45 ` Bjorn Helgaas
2005-08-11 20:56 ` Jeff Garzik
2005-08-11 21:42 ` Bjorn Helgaas
2005-08-11 21:48 ` Jeff Garzik
2005-08-11 21:56 ` Jeff Garzik
2005-08-11 23:07 ` Bjorn Helgaas
2005-08-11 23:49 ` Jeff Garzik
2005-08-12 8:35 ` Alan Cox
2005-08-12 10:33 ` Maciej W. Rozycki
2005-08-11 23:01 ` Jack Steiner
2005-08-11 23:08 ` Jack Steiner
2005-08-12 8:40 ` Alan Cox
2005-08-15 21:07 ` Bjorn Helgaas
2005-08-16 9:38 ` Bartlomiej Zolnierkiewicz
2005-08-16 9:54 ` Bartlomiej Zolnierkiewicz
2005-08-16 12:55 ` Alan Cox
2005-08-16 12:59 ` Bartlomiej Zolnierkiewicz
2005-08-16 13:40 ` Matthew Wilcox
2005-08-16 13:49 ` Bartlomiej Zolnierkiewicz
2005-08-16 19:16 ` Bjorn Helgaas
2005-08-16 20:16 ` Bartlomiej Zolnierkiewicz
2005-08-16 20:25 ` Alan Cox
2005-08-16 20:42 ` Bartlomiej Zolnierkiewicz
2005-08-16 21:48 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2005-08-11 21:58 Luck, Tony
2005-08-11 22:03 ` Jeff Garzik
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=1124201152.17555.36.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=bjorn.helgaas@hp.com \
--cc=bzolnier@gmail.com \
--cc=hch@infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).