From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-in-03.arcor-online.net (mail-in-03.arcor-online.net [151.189.21.43]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx.arcor.de", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTP id C25FADDD0D for ; Thu, 22 Feb 2007 17:50:12 +1100 (EST) In-Reply-To: References: <20070220020837.GF17818@localhost.localdomain> <20070220021235.DC02DDDD06@ozlabs.org> <9696D7A991D0824DBA8DFAC74A9C5FA302A58C89@az33exm25.fsl.freescale.net> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <2b8d25463127d2c665da879c0ec234e2@kernel.crashing.org> From: Segher Boessenkool Subject: Re: [PATCH 12/14] Add device tree for Ebony Date: Thu, 22 Feb 2007 07:49:53 +0100 To: Segher Boessenkool Cc: linuxppc-dev@ozlabs.org, Yoder Stuart-B08248 , David Gibson List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , >> Since UIC1 is cascaded off UIC0 in the interrupt tree, >> UIC1 should have an interrupt-parent pointing to UIC0 >> so the interrupt tree can be traversed to the root. > > Not necessary if UIC0 is the device tree parent of UIC1. For the archives: this is wrong, all interrupt controllers (except the root one) are required to have an "interrupt-parent" property -- this is how the root interrupt controller is determined. Segher