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,
Tony Luck <tony.luck@intel.com>
Subject: Re: [PATCH] IDE: don't offer IDE_GENERIC on ia64
Date: Thu, 11 Aug 2005 21:42:07 +0000 [thread overview]
Message-ID: <200508111542.07851.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <42FBBB6F.1030306@pobox.com>
On Thursday 11 August 2005 2:56 pm, Jeff Garzik wrote:
> Bjorn Helgaas wrote:
> > On Thursday 11 August 2005 2:36 pm, Jeff Garzik wrote:
> >>Bjorn Helgaas wrote:
> >>> 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?
>
> No idea... that's more for platform IA64 people to answer :/
OK, well, I assert that failure to describe an IDE device that
uses legacy ports would be an ACPI defect.
Tony, others, does this change give you any heartburn? On
the 460GX and 870 boxes I have, IDE is a PCI device.
(I have been told that the SGI ia64 simulator depends on
IDE_GENERIC. But it really should make the IDE device
appear in PCI (or describe it via ACPI)).
next prev parent reply other threads:[~2005-08-11 21:42 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 13:42 ` Alan Cox
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 [this message]
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 21:58 ` Luck, Tony
2005-08-11 22:03 ` Jeff Garzik
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 19:59 ` Alan Cox
2005-08-16 20:42 ` Bartlomiej Zolnierkiewicz
2005-08-16 21:48 ` Alan Cox
2005-08-16 20:16 ` Bartlomiej Zolnierkiewicz
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=200508111542.07851.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 \
--cc=tony.luck@intel.com \
/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