From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Warren <swarren@wwwdotorg.org>
Date: Wed, 24 Oct 2012 17:05:07 -0600
Subject: [U-Boot] Multiple stdin/out without CONFIG_CONSOLE_MUX?
Message-ID: <50887423.8060409@wwwdotorg.org>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Mathieu, John,

While looking into a CONFIG_CONSOLE_MUX-related issue, I noticed the
following:

include/configs/u8500_href.h:136:	"stdin=serial,usbtty\0"
include/configs/u8500_href.h:135:	"stdout=serial,usbtty\0"
include/configs/snowball.h:180:	"stdout=serial,usbtty\0"

Those all include multiple devices in the stdin/stdout definitions.
However, those config files don't set CONFIG_CONSOLE_MUX. I assume this
causes usbtty to be ignored, and only serial used?

Or perhaps U-Boot even fails to parse the variable at all, since
CONFIG_SYS_CONSOLE_IS_IN_ENV isn't set on those boards? Actually, there
are a few more boards with that problem:

> include/configs/km/keymile-common.h:258:	"stdout=serial\0"						\
> include/configs/MVBC_P.h:146:	"stdout=serial\0"					\
> include/configs/MVBLM7.h:460:	"stdout=serial\0"					\
> include/configs/MVSMR.h:129:	"stdout=serial\0"					\
> include/configs/sandbox.h:91:					"stdout=serial\0" \
> include/configs/snowball.h:180:	"stdout=serial,usbtty\0"					\
> include/configs/u8500_href.h:135:	"stdout=serial,usbtty\0"					\