LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Albrecht Dreß" <albrecht.dress@arcor.de>
To: sylvain.lamontagne@novariant.com
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Boot hang when setting console=none with MPC5200B custom board
Date: Fri, 23 Apr 2010 09:28:59 +0200 (CEST)	[thread overview]
Message-ID: <2011538478.344681272007739977.JavaMail.ngmail@webmail06.arcor-online.net> (raw)

Hi Sylvain:

> Humm I see, here is the node I'm creating in the initial ramdisk, so
> they are there before mdev is launched in one of my init scripts.
[snip]

I additionally have "tty0 c 4 0" which might be important here, plus a lot of other crap (should clean up there...;-).  I don't use a ramdisk, but have the /dev folder in the flash jffs2 image.  In the init script, I say

/bin/mount -t tmpfs ramfs /dev
mdev -s
mkdir /dev/pts
mkdir /dev/shm
chmod 1777 /dev/shm

and then tty0 is gone.  So to be honest I'm not absolutely sure it's necessary.

My inittab contains

::sysinit:/etc/init.d/rcS
::respawn:-/bin/sh 
::shutdown:/etc/init.d/rcS stop
::restart:/sbin/init
::respawn:/sbin/dropbear -F

With this, I can access the board through ssh (dropbear).  The dmesg output lists "console=tty0" as expected.  All PSC's are in the device tree, btw, and available as serial ports.

Hth,
Albrecht.

Traumziele - von Beschreibung bis Buchung jetzt kompakt auf den Reise-Seiten von Arcor.de! http://www.arcor.de/rd/footer.reise

             reply	other threads:[~2010-04-23  7:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-23  7:28 Albrecht Dreß [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-04-22 18:58 Boot hang when setting console=none with MPC5200B custom board Sylvain Lamontagne
2010-04-22 19:11 ` Grant Likely
2010-04-22 20:34   ` Sylvain Lamontagne
2010-04-22 19:25 ` Albrecht Dreß
2010-04-22 20:23   ` Sylvain Lamontagne

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=2011538478.344681272007739977.JavaMail.ngmail@webmail06.arcor-online.net \
    --to=albrecht.dress@arcor.de \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=sylvain.lamontagne@novariant.com \
    /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