From: "Albrecht Dreß" <albrecht.dress@arcor•de>
To: Sylvain Lamontagne <sylvain.lamontagne@novariant•com>
Cc: "linuxppc-dev@lists•ozlabs.org" <linuxppc-dev@lists•ozlabs.org>
Subject: Re: Boot hang when setting console=none with MPC5200B custom board
Date: Thu, 22 Apr 2010 21:25:49 +0200 [thread overview]
Message-ID: <1271964357.1672.1@antares> (raw)
In-Reply-To: <1271962721.12334.34.camel@slamon-laptop.novariant.com> (from sylvain.lamontagne@novariant.com on Thu Apr 22 20:58:41 2010)
[-- Attachment #1: Type: text/plain, Size: 815 bytes --]
Hi Sylvain:
Am 22.04.10 20:58 schrieb(en) Sylvain Lamontagne:
[snip]
> 1. Is it possible ?
Yes! I tried this with several kernel versions (currently 2.6.33), using the option 'console=tty0'. Works just fine...
> 2. Do you have any idea how it can be achieve ?
Hmmm, iirc, I also saw the effect you have. I *think* the solution was to ensure that all /dev/* files were created manually in the jffs image, not by running mdev (if you use busybox). But I might be wrong here, sorry. Being at home, I don't have access to the device, but I can re-check tomorrow.
> 3. Do you know a bug in 2.6.29.2 that could prevent this to work ?
Not sure if I used *exactly* that version w/o serial console, but (iirc) 2.6.28.something, and then many different up to .33 - they all work!
Best, Albrecht.
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2010-04-22 19:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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ß [this message]
2010-04-22 20:23 ` Sylvain Lamontagne
-- strict thread matches above, loose matches on Subject: below --
2010-04-23 7:28 Albrecht Dreß
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=1271964357.1672.1@antares \
--to=albrecht.dress@arcor$(echo .)de \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=sylvain.lamontagne@novariant$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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