From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [PATCH] tbs2910: migrate to DM_VIDEO
Date: Tue, 26 May 2020 22:13:11 +0200 [thread overview]
Message-ID: <20200526221311.752bc883@crub> (raw)
In-Reply-To: <eb4bf791-04dd-6597-6b6d-0e8893cd28dd@web.de>
On Sun, 24 May 2020 17:46:22 +0200
Soeren Moch smoch at web.de wrote:
> On 23.05.20 01:24, Anatolij Gustschin wrote:
> > Migration to DM_VIDEO driver is long overdue, configure it in
> > board config files. To enable the display set stdout like:
> >
> > setenv stdout serial,vidconsole
> >
> > Signed-off-by: Anatolij Gustschin <agust@denx.de>
> > ---
> > This is only build tested.
> I tested this on top of v2020.07-rc2 and your patch
> "video: extend stdout video console work-around for 'vga'"
>
> Works great. However, some comments below.
Thanks for testing!
...
> > +CONFIG_SYS_MALLOC_F_LEN=0x4000
> This is not necessary. The default 0x2000 also works fine.
Dropped in v2.
...
> Since DM_VIDEO requires vidconsole as output device, please also add
>
> ---8<---
> diff --git a/include/configs/tbs2910.h b/include/configs/tbs2910.h
> index 8ab3fcfe3e..82165a9ffe 100644
> --- a/include/configs/tbs2910.h
> +++ b/include/configs/tbs2910.h
> @@ -92,11 +92,11 @@
> ??????? "fan=gpio set 92\0" \
> ??????? "set_con_serial=setenv stdout serial; " \
> ??????????????????????? "setenv stderr serial\0" \
> -?????? "set_con_hdmi=setenv stdout serial,vga; " \
> -?????????????????????? "setenv stderr serial,vga\0" \
> -?????? "stderr=serial,vga\0" \
> +?????? "set_con_hdmi=setenv stdout serial,vidconsole; " \
> +?????????????????????? "setenv stderr serial,vidconsole\0" \
> +?????? "stderr=serial,vidconsole\0" \
> ??????? "stdin=serial,usbkbd\0" \
> -?????? "stdout=serial,vga\0"
> +?????? "stdout=serial,vidconsole\0"
> ?
> ?#define CONFIG_BOOTCOMMAND \
> ??????? "mmc rescan; " \
> ---8<---
>
> to avoid warnings for users with default environment.(not sure if
> whitespace is still correct in this snippet)
Done in v2.
> With this DM_VIDEO conversion the board comes very close to the size
> limit. While it works with my toolchain, there might be problems with
> others. So maybe not a good idea to merge this as fix immediately.
Yes, with GCC 9.2 it didn't work any more. I've submitted some DM_VIDEO
patches to disable more unused code to fix this.
> Since this depends on your above mentioned patch, do you plan to merge
> this via u-boot-video, or should this go as usual through the imx tree?
I'll merge this via u-boot-video tree. v2 patch depends on a few more
video patches which are under review/built-test currently.
--
Anatolij
next prev parent reply other threads:[~2020-05-26 20:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 23:24 [PATCH] tbs2910: migrate to DM_VIDEO Anatolij Gustschin
2020-05-23 7:55 ` Soeren Moch
2020-05-23 15:11 ` [PATCH] video: extend stdout video console work-around for 'vga' Anatolij Gustschin
2020-05-24 15:21 ` Soeren Moch
2020-05-25 2:14 ` Simon Glass
2020-05-26 18:08 ` Tom Rini
2020-06-19 13:55 ` Anatolij Gustschin
2020-07-01 13:01 ` Patrick DELAUNAY
2020-05-23 15:17 ` [PATCH] tbs2910: migrate to DM_VIDEO Anatolij Gustschin
2020-05-23 15:31 ` Soeren Moch
2020-05-24 15:46 ` Soeren Moch
2020-05-26 20:13 ` Anatolij Gustschin [this message]
2020-05-28 7:54 ` Soeren Moch
2020-05-28 8:07 ` Anatolij Gustschin
2020-05-30 16:01 ` Soeren Moch
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=20200526221311.752bc883@crub \
--to=agust@denx.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