From wookey@wookware.org Thu Nov 15 15:07:20 2007 Received: from [213.165.225.113] (helo=knossos.aleph1.co.uk ident=Debian-exim) by stoneboat.aleph1.co.uk with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1IsgJ9-0007Ff-1z for balloon@balloonboard.org; Thu, 15 Nov 2007 15:07:20 +0000 Received: from wookey by knossos.aleph1.co.uk with local (Exim 4.63) (envelope-from ) id 1IsgIw-0003zM-Jq for balloon@balloonboard.org; Thu, 15 Nov 2007 15:06:54 +0000 Date: Thu, 15 Nov 2007 15:06:54 +0000 From: Wookey To: balloon@balloonboard.org Message-ID: <20071115150654.GZ28705@knossos.aleph1.co.uk> Mail-Followup-To: balloon@balloonboard.org References: <473C4C88.8030006@tuckley.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <473C4C88.8030006@tuckley.org> User-Agent: Mutt/1.5.13 (2006-08-11) X-Aleph_One-MailScanner: Found to be clean X-Aleph_One-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-2.595, required 6, autolearn=not spam, AWL 0.01, BAYES_00 -2.60, NO_RELAYS -0.00) X-Aleph_One-MailScanner-From: wookey@wookware.org X-SA-Exim-Connect-IP: 213.165.225.113 X-SA-Exim-Mail-From: wookey@wookware.org X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on stoneboat.aleph1.co.uk X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.3 X-SA-Exim-Version: 4.2.1 (built Tue, 09 Jan 2007 17:23:22 +0000) X-SA-Exim-Scanned: Yes (on stoneboat.aleph1.co.uk) Subject: Re: [Balloon] Balloon 2 DRAM - turn off bank 1 if it is enabled but there is no dram there X-BeenThere: balloon@balloonboard.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Balloon List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Nov 2007 15:07:20 -0000 On 2007-11-15 13:41 +0000, Colin Tuckley wrote: > I have been working on re-building the loon-2 boot loader with a modern > compiler. > > We have come across what appears to be a timing related oddity. > > The following code is executed during the Linux boot phase, if the call to > fixup_dram_bank1() is executed then the bootldr crashes > > With the call commented out the boot into Linux works. If we put some debug > print statements in that part of the code then it also boots ok, but the > printing immediately after the fixup call is garbled. It also works OK if built with gcc4.1.3 instead of 4.2.3, which is quite odd. Perhaps supports the theory that this is timing related and the two compilers arrnage the code differently (we've not yet compared objdumps) Wookey -- Principal hats: Balloonz - Toby Churchill - Aleph One - Debian http://wookware.org/