From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Curtis Wald <CWald@WatchGuardVideo.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] POWERPC 4xx: Fix PCI in AMCC 440EP Yosemite DTS
Date: Fri, 4 Dec 2009 07:07:44 -0500 [thread overview]
Message-ID: <20091204120744.GI2937@zod.rchland.ibm.com> (raw)
In-Reply-To: <13F6A75BE29CE44F801B912901C3EF270233B6A4@wgv4.watchguardvideo.local>
On Mon, Nov 30, 2009 at 09:25:51AM -0600, Curtis Wald wrote:
>Josh,
>Here is a resend of the Yosemite.dts patch, deleting tabs and spaces in
>the IDSEL section that should look better when viewing as 80 column.
Something is still eating your patches when you send them out. They get
corrupted to the point of being unusable as you can see here:
http://patchwork.ozlabs.org/patch/39810/
However, your intentions are pretty clear. Could you look at the patch below
and see if it was what you intended? If so, I'll include it in my 'next'
branch today.
josh
---
diff --git a/arch/powerpc/boot/dts/yosemite.dts b/arch/powerpc/boot/dts/yosemite.dts
index 1fa3cb4..6492324 100644
--- a/arch/powerpc/boot/dts/yosemite.dts
+++ b/arch/powerpc/boot/dts/yosemite.dts
@@ -282,20 +282,10 @@
/* Inbound 2GB range starting at 0 */
dma-ranges = <0x42000000 0x0 0x0 0x0 0x0 0x0 0x80000000>;
- /* Bamboo has all 4 IRQ pins tied together per slot */
interrupt-map-mask = <0xf800 0x0 0x0 0x0>;
interrupt-map = <
- /* IDSEL 1 */
- 0x800 0x0 0x0 0x0 &UIC0 0x1c 0x8
-
- /* IDSEL 2 */
- 0x1000 0x0 0x0 0x0 &UIC0 0x1b 0x8
-
- /* IDSEL 3 */
- 0x1800 0x0 0x0 0x0 &UIC0 0x1a 0x8
-
- /* IDSEL 4 */
- 0x2000 0x0 0x0 0x0 &UIC0 0x19 0x8
+ /* IDSEL 12 */
+ 0x6000 0x0 0x0 0x0 &UIC0 0x19 0x8
>;
};
};
next prev parent reply other threads:[~2009-12-04 12:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 17:36 [PATCH] POWERPC 4xx: Fix PCI in AMCC 440EP Yosemite DTS Curtis Wald
2009-11-30 13:41 ` Josh Boyer
2009-11-30 15:25 ` Curtis Wald
2009-12-04 12:07 ` Josh Boyer [this message]
2009-12-04 14:19 ` Curtis Wald
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=20091204120744.GI2937@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=CWald@WatchGuardVideo.com \
--cc=linuxppc-dev@ozlabs.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