From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [PATCH] IDE on CHRP LongTrail
Date: 24 Dec 2002 08:40:32 +0100 [thread overview]
Message-ID: <1040715633.1966.32.camel@zion> (raw)
In-Reply-To: <Pine.GSO.4.21.0212232301330.1694-100000@vervain.sonytel.be>
On Mon, 2002-12-23 at 23:13, Geert Uytterhoeven wrote:
>
> This patch enables the SL82C105 IDE interface in the W83C553 PCI/ISA bridge on
> my CHRP LongTrail.
>
> There are 2 ways to configure the IDE interface:
> - Legacy mode, using IRQ 14 for the primary channel, and IRQ 15 for the
> secondary channel
> - Native mode, using IRQ 32 (OpenPIC IRQ 16) for both channels
>
> Apparently Open Firmware left the IDE interface in legacy mode, while the
> interrupt property of the device pointed to the OpenPIC interrupt. Of course
> this mix of legacy and native mode didn't work well and no interrupts came
> through.
>
> With the patch below, the SL82C105 is configured for native mode and both IDE
> channels work. The patch applies to 2.4.21-pre2 as well, but there IDE seems to
> be broken on PPC in general.
I'd rather use a pci quirk here... also, why not make this generic to
all PPCs with a W83c553 ? I know the briQ at least will need something
similar.
Regarding 2.4.21-pre2, did you check the linuxppc_2_4 tree ?
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-12-24 7:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-23 22:13 [PATCH] IDE on CHRP LongTrail Geert Uytterhoeven
2002-12-24 7:40 ` Benjamin Herrenschmidt [this message]
2002-12-24 9:09 ` Geert Uytterhoeven
2002-12-24 9:52 ` Geert Uytterhoeven
2002-12-24 10:00 ` Benjamin Herrenschmidt
2002-12-26 13:18 ` Geert Uytterhoeven
2002-12-26 16:17 ` Gabriel Paubert
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=1040715633.1966.32.camel@zion \
--to=benh@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.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).