From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Matt Sealey <matt@genesi-usa.com>
Cc: Chuck Ebbert <cebbert@redhat.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: IDE broken on Pegasos PPC platform
Date: Tue, 25 Sep 2007 19:24:25 +1000 [thread overview]
Message-ID: <1190712265.31978.10.camel@localhost.localdomain> (raw)
In-Reply-To: <46F82BCF.1020702@genesi-usa.com>
On Mon, 2007-09-24 at 22:27 +0100, Matt Sealey wrote:
> Yeah I'll ack it if it matters, although I'd make a nit about the
> fixing of device tree entries in prom_init and have it moved to
> nvramrc or a Forth script or boot loader..
>
> Pegasos IDE quirks have been "fixed" so many times now in Linux,
> this code's going to get reshuffled again in other changes, I
> think the device tree should be fixed at the firmware level and
> not in the kernel.
In that case though, OF contains correct values for the interrupts, it's
more of an issue related to the device being in legacy mode and the
pci_dev only carrying one interrupt anyway.
Ben.
prev parent reply other threads:[~2007-09-25 9:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 19:10 IDE broken on Pegasos PPC platform Chuck Ebbert
2007-09-24 20:38 ` Alan Cox
2007-09-24 20:58 ` libata broken on Pegasos PPC platform (was: Re: IDE broken on Pegasos PPC platform) Bartlomiej Zolnierkiewicz
2007-09-24 21:10 ` Alan Cox
2007-09-25 9:22 ` Olaf Hering
2007-09-24 21:27 ` IDE broken on Pegasos PPC platform Matt Sealey
2007-09-25 9:24 ` Benjamin Herrenschmidt [this message]
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=1190712265.31978.10.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=cebbert@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@genesi-usa.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).