All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Mendham <petermendham@computing.dundee.ac.uk>
To: Peter Korsgaard <jacmet@sunsite.dk>
Cc: John Linn <John.Linn@xilinx.com>, linuxppc-embedded@ozlabs.org
Subject: Re: Linux on Virtex board with ARCH=powerpc
Date: Wed, 02 Jul 2008 09:49:38 +0100	[thread overview]
Message-ID: <486B4122.90909@computing.dundee.ac.uk> (raw)
In-Reply-To: <874p7eeodw.fsf@macbook.be.48ers.dk>

Hi,

Peter Korsgaard wrote:
> Hi,
>
>  Peter> I now have a new and rather bizarre problem, which maybe you
>  Peter> or someone else has met before.  I have a simple FPGA design
>  Peter> with memory, a sysace and a uart16550 on an ML405 (I've put my
>  Peter> hardware to one side for the moment).  It works just fine.  If
>  Peter> I swap the uart16550 for a uartlite (remaking the kernel with
>  Peter> the correct device tree) I see all the boot messages and the
>  Peter> kernel seems to start OK, the root partition is mounted but
>  Peter> then I see nothing from /sbin/init.  This is the same root fs
>  Peter> that I was using with the uart16550 example I just mentioned.
>
> Did you remember to change your inittab to use /dev/ttyUL0?
>   
Yes, I'm using a buildroot/busybox system and have changed inittab and 
securetty for ttyUL0.  From what I understand, initialisation lines in a 
busybox inittab that do not specify a tty at the beginning go out on 
/dev/console.  To collaborate this, if I set my hardware up for a 
uart16550 and leave the inittab specifying ttyUL0, I see the messages 
from the init scripts (which must be going to console) but then I 
messages (again on console I guess) saying that ttyUL0 doesn't exist.  
When I try things the other way round, I don't see anything at all (none 
of the stuff that I think is going to console) and it doesn't moan at 
me.  Which I guess means something is wrong with /dev/console?

-- Peter

The University of Dundee is a Scottish Registered Charity, No. SC015096.

  reply	other threads:[~2008-07-02  8:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24  9:02 Linux on Virtex board with ARCH=powerpc Peter Mendham
2008-06-24 14:03 ` John Linn
2008-06-24 19:21   ` Peter Mendham
2008-06-24 19:50     ` John Linn
2008-06-25 16:17       ` Peter Mendham
2008-06-25 20:34         ` John Linn
2008-06-26 13:24           ` Peter Mendham
2008-06-26 13:29             ` John Linn
2008-06-27 12:30               ` Peter Mendham
2008-06-27 13:25                 ` John Linn
2008-06-27 15:06                   ` Peter Mendham
2008-06-27 15:18                 ` Aaron Sells
2008-06-27 15:24                   ` Peter Mendham
2008-06-27 18:14                 ` Peter Korsgaard
2008-07-02  8:49                   ` Peter Mendham [this message]
2008-06-24 19:50     ` Stephen Neuendorffer

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=486B4122.90909@computing.dundee.ac.uk \
    --to=petermendham@computing.dundee.ac.uk \
    --cc=John.Linn@xilinx.com \
    --cc=jacmet@sunsite.dk \
    --cc=linuxppc-embedded@ozlabs.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.