From: Bastian Blank <waldi@debian.org>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/lpar - defer prefered console setup
Date: Wed, 30 Jul 2008 08:23:13 +0200 [thread overview]
Message-ID: <20080730062313.GA26044@wavehammer.waldi.eu.org> (raw)
In-Reply-To: <1217385291.10646.2.camel@localhost>
On Wed, Jul 30, 2008 at 12:34:51PM +1000, Michael Ellerman wrote:
> On Mon, 2008-07-28 at 20:56 +0200, Bastian Blank wrote:
> * add_preferred_console - add a device to the list of preferred consoles.
> ...
> * The last preferred console added will be used for kernel messages
> * and stdin/out/err for init.
>
> The last console will be added by the console= parsing, and so that will
> be used. The console we add in the pseries setup is only used if nothing
> is specified on the command line.
Okay, then there is a completely different problem. In the case of
"console=hvc0 console=hvc1" it uses the _first_ add stdin/out bla and
ignores the second one completely.
Bastian
--
Four thousand throats may be cut in one night by a running man.
-- Klingon Soldier, "Day of the Dove", stardate unknown
next prev parent reply other threads:[~2008-07-30 6:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 18:56 [PATCH] powerpc/lpar - defer prefered console setup Bastian Blank
2008-07-29 3:06 ` Benjamin Herrenschmidt
2008-07-29 7:36 ` Bastian Blank
2008-07-29 7:43 ` Benjamin Herrenschmidt
2008-07-29 8:07 ` Bastian Blank
2008-07-29 9:00 ` Benjamin Herrenschmidt
2008-07-30 2:34 ` Michael Ellerman
2008-07-30 6:23 ` Bastian Blank [this message]
2008-07-30 6:29 ` Bastian Blank
2008-07-30 7:34 ` [PATCH] hvc - register all available consoles (was: Re: [PATCH] powerpc/lpar - defer prefered console setup) Bastian Blank
2008-07-30 9:13 ` Milton Miller
2008-07-30 10:07 ` Bastian Blank
2008-07-30 18:18 ` Milton Miller
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=20080730062313.GA26044@wavehammer.waldi.eu.org \
--to=waldi@debian.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
/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).