From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp01.megaweb.hu (ivymike.megaweb.hu [195.228.155.87]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id 74C2267BB9 for ; Mon, 4 Sep 2006 04:13:33 +1000 (EST) Message-ID: <44FB1B4A.3040001@uid0.hu> Date: Sun, 03 Sep 2006 20:13:30 +0200 From: Zoltan HERPAI MIME-Version: 1.0 To: Michael Galassi Subject: Re: Serial problem with MPC8241-based board References: <200609031642.k83GgOuo089969@penguin.ncube.com> In-Reply-To: <200609031642.k83GgOuo089969@penguin.ncube.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Cc: linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , None of the iterations worked with the Sandpoint and Linkstation setups. Is there some way to test basic serial communication within the kernel, to at least see if the CPU initialization is done correctly? -w- Michael Galassi wrote: >> I've recently acquired an Allnet 6250 NAS, which has an MPC8241-based >> board. Since its GPL tarball is not available fully, I began to build a >> toolchain based on gcc-3.4.6 and binutils-2.16.1, and an up-to-date >> kernel for it. PPCboot states that this is a Sandpoint 8241 Unity board, >> so the platforms/sandpoint.* was chosen as a starting point, however, >> after rewriting the irq and ioport values in sandpoint.h to the ones >> (irq 137, ioport 0x80004500), no output came out of the serial port. >> After a few days of tweaking around with variables is sandpoint.h, a >> google session revealed that this board is 99% the same as the Buffalo >> Linkstation's is, which has a 2.6.x port also, but those kernels are >> also failing to display any output. >> Can anyone shed some light on what points should I check and what may I >> have done wrong? >> > > I've recently spent a bunch of time chasing after display issues related > to the goofy way Linux handles consoles early on. Try removing console= > from your boot arguments and see where that puts you. > > -michael > >