linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Galassi <mgalassi@c-cor.com>
To: Zoltan HERPAI <wigyori@uid0.hu>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Serial problem with MPC8241-based board
Date: Sun, 03 Sep 2006 09:42:24 -0700	[thread overview]
Message-ID: <200609031642.k83GgOuo089969@penguin.ncube.com> (raw)
In-Reply-To: Your message of "Sun, 03 Sep 2006 17:36:47 +0200." <44FAF68F.1080206@uid0.hu>

>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

  reply	other threads:[~2006-09-03 16:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-03 15:36 Serial problem with MPC8241-based board Zoltan HERPAI
2006-09-03 16:42 ` Michael Galassi [this message]
2006-09-03 18:13   ` Zoltan HERPAI
2006-09-03 19:58 ` Guennadi Liakhovetski
2006-09-05 18:49   ` Mark A. Greer

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=200609031642.k83GgOuo089969@penguin.ncube.com \
    --to=mgalassi@c-cor.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=wigyori@uid0.hu \
    /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;
as well as URLs for NNTP newsgroup(s).