From: Soeren Moch <smoch@web.de>
To: u-boot@lists.denx.de
Subject: [PATCH] board: tbs2910: Fix video output with existing environments
Date: Thu, 30 Jul 2020 14:11:57 +0200 [thread overview]
Message-ID: <20200730121157.5305-1-smoch@web.de> (raw)
Migration to DM_VIDEO changed the output device name (in stout, stderr)
from 'vga' to 'vidconsole'. This also was adapted in the default environment.
However, existing user defined environments still use 'vga'. Enable this
workaround to map the 'vga' name to 'vidconsole'. So we get HDMI video
output also with existing legacy environments.
Signed-off-by: Soeren Moch <smoch@web.de>
---
Cc: Stefano Babic <sbabic@denx.de>
Cc: Fabio Estevam <festevam@gmail.com>
Cc: Anatolij Gustschin <agust@denx.de>
Cc: u-boot at lists.denx.de
There was an automatic fix in the original DM_VIDEO conversion for this
case. Apparently this fix was lost on the way to v2020.10-rc1. So we need
to enable this explicitly here.
This patch was created on top of f7d0ae9 ("configs: Resync with
savedefconfig"), directly after v2020.10-rc1.
---
configs/tbs2910_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/configs/tbs2910_defconfig b/configs/tbs2910_defconfig
index b4eaf9d162..c15a173d91 100644
--- a/configs/tbs2910_defconfig
+++ b/configs/tbs2910_defconfig
@@ -100,6 +100,7 @@ CONFIG_DM_VIDEO=y
# CONFIG_VIDEO_ANSI is not set
CONFIG_SYS_WHITE_ON_BLACK=y
# CONFIG_PANEL is not set
+CONFIG_VIDCONSOLE_AS_LCD=y
CONFIG_I2C_EDID=y
CONFIG_VIDEO_IPUV3=y
# CONFIG_GZIP is not set
--
2.17.1
next reply other threads:[~2020-07-30 12:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 12:11 Soeren Moch [this message]
2020-08-04 7:44 ` [PATCH] board: tbs2910: Fix video output with existing environments Anatolij Gustschin
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=20200730121157.5305-1-smoch@web.de \
--to=smoch@web.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox