From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] [v2] powerpc: 'monitor' environment variable contains full video configuration
Date: Tue, 15 Mar 2011 15:48:12 -0500 [thread overview]
Message-ID: <4D7FD08C.2020406@freescale.com> (raw)
In-Reply-To: <20110315204152.F1DD81538EF@gemini.denx.de>
Wolfgang Denk wrote:
>> > What is the standard mechanism for enabling the console on the video display?
>> > From what I can tell, if video_hw_init() returns non-NULL, then the console is
>> > set to the video display, regardless as to what the "stdout" environment
>> > variable says.
> That's the default. Users can overwrite it, for example in "preboot".
> See also CONFIG_ENV_OVERWRITE
Then I'm confused, because video_hw_init() is what configures and enables the
video display. So if that function succeeds (i.e. returns non-NULL), then
U-Boot will put the console onto the video display. You said you wanted me to
implement some mechanism where I enable the display, based on the value of the
video-mode variable, without putting console on the display. However, from you
just said, it appears that this mechanism already exists.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2011-03-15 20:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 20:19 [U-Boot] [PATCH] [v2] powerpc: 'monitor' environment variable contains full video configuration Timur Tabi
2011-03-14 23:33 ` Wolfgang Denk
2011-03-14 23:39 ` Tabi Timur-B04825
2011-03-15 9:05 ` Wolfgang Denk
2011-03-15 14:50 ` Timur Tabi
2011-03-15 15:15 ` Wolfgang Denk
2011-03-15 15:21 ` Timur Tabi
2011-03-15 15:47 ` Wolfgang Denk
2011-03-15 15:52 ` Timur Tabi
2011-03-15 19:02 ` Wolfgang Denk
2011-03-15 19:09 ` Timur Tabi
2011-03-15 19:38 ` Wolfgang Denk
2011-03-15 19:49 ` Timur Tabi
2011-03-15 20:41 ` Wolfgang Denk
2011-03-15 20:48 ` Timur Tabi [this message]
2011-03-15 21:47 ` Wolfgang Denk
2011-03-15 22:32 ` Timur Tabi
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=4D7FD08C.2020406@freescale.com \
--to=timur@freescale.com \
--cc=u-boot@lists.denx.de \
/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.