From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
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: Fri, 12 Aug 2005 09:35:50 +0100 [thread overview]
Message-ID: <1123835751.22460.13.camel@localhost.localdomain> (raw)
In-Reply-To: <200508111707.30861.bjorn.helgaas@hp.com>
On Iau, 2005-08-11 at 17:07 -0600, Bjorn Helgaas wrote:
> So the scenario in question (correct me if I'm wrong) is that we
> have a PCI IDE device that is handed off in compatibility mode (and
> may only work in that mode). In that case, the PCI *device* still
> exists, so shouldn't the IDE PCI code claim that device, notice that
> it's in compatibility mode, and use the legacy ports and IRQs if
> necessary?
The PCI IDE code and legacy IDE code both find the device and they
realise its the same device so that it is driven by a suitable driver.
The legacy IDE driver is useful if your platform has an unsupported IDE
controller. It seems ot me the correct fix for IA64 is probably to set
your arch specific probe address function to only probe the standard PCI
legacy ports and to do any other appropriate checks, not to take an axe
to Kconfig.
Alan
next prev parent reply other threads:[~2005-08-12 8:09 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
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 [this message]
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=1123835751.22460.13.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=bjorn.helgaas@hp.com \
--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;
as well as URLs for NNTP newsgroup(s).