From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from az33egw02.freescale.net (az33egw02.freescale.net [192.88.158.103]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "az33egw02.freescale.net", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTP id 1D059DE031 for ; Fri, 11 Jan 2008 06:20:24 +1100 (EST) Message-ID: <47866FDE.5070307@freescale.com> Date: Thu, 10 Jan 2008 13:19:58 -0600 From: Scott Wood MIME-Version: 1.0 To: Rune Torgersen Subject: Re: Help with device tree binding for SMC serial References: <4785246D.6090206@freescale.com> <47854AE1.7080802@freescale.com> <47854D6D.2010906@freescale.com> <20080110175348.GA4317@loki.buserror.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Rune Torgersen wrote: > Not sure what was wrong. We took a step back, and redid some stuff, and > now we have serial output from the boot-wrapper. > THe checkstop came from the wrapper grying to access the bcsr and doing > the chip select fixup. We don';t have a bcsr on our board, and the cs > layout is different. There's no bcsr access in the upstream bootwrapper (the mention of bcsr in cuboot-pq2.c is just one reason why some boards require us to do the CS programming), and the CS programming is chip-level, not board-level (it just requires that the device tree have a correct localbus node for the board). -Scott