From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: 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: Thu, 11 Aug 2005 14:45:41 -0600 [thread overview]
Message-ID: <200508111445.41428.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <42FBB6C5.2070404@pobox.com>
On Thursday 11 August 2005 2:36 pm, Jeff Garzik wrote:
> 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.
> >
> > Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
> >
> > Index: work-vga/drivers/ide/Kconfig
> > ===================================================================
> > --- work-vga.orig/drivers/ide/Kconfig 2005-08-10 14:57:47.000000000 -0600
> > +++ work-vga/drivers/ide/Kconfig 2005-08-10 14:58:02.000000000 -0600
> > @@ -276,6 +276,7 @@
> >
> > config IDE_GENERIC
> > tristate "generic/default IDE chipset support"
> > + depends on !IA64
>
> hmmmmmmmmm. Are you POSITIVE that the legacy IDE ports are never enabled?
>
> In modern Intel chipsets, this still occurs with e.g. combined mode.
I don't know about combined mode. If the legacy IDE ports are
enabled, shouldn't they be described via ACPI, and hence usable
via the ide_pnp - PNPACPI - ACPI path?
next prev parent reply other threads:[~2005-08-11 20:45 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
2005-08-11 20:36 ` Jeff Garzik
2005-08-11 20:45 ` Bjorn Helgaas [this message]
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=200508111445.41428.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=jgarzik@pobox.com \
--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).