From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: U-Boot Logo showing incorrect colors with eLCDIF
Date: Sat, 25 Jan 2020 19:36:38 +0100 [thread overview]
Message-ID: <20200125193638.38f504fb@crub> (raw)
In-Reply-To: <CAOMZO5DXKkpM17bdsKRw=+mjN41A6ye47SWXFdDzMYDjHawe=A@mail.gmail.com>
Hi Fabio,
On Fri, 24 Jan 2020 16:26:26 -0300
Fabio Estevam festevam at gmail.com wrote:
> > Do you have 'bits-per-pixel' property in your display node in DT?
> > Is suitable CONFIG_VIDEO_BPPxx option enabled in your board_defconfig ?
>
> Yes, I have it, but it has the wrong value. It should be 24bpp instead of 16bpp.
>
> I did the following change:
>
> --- a/arch/arm/dts/imx6ul-14x14-evk-u-boot.dtsi
> +++ b/arch/arm/dts/imx6ul-14x14-evk-u-boot.dtsi
> @@ -4,7 +4,6 @@
> */
>
> display0: display at 0 {
> - bits-per-pixel = <16>;
> + bits-per-pixel = <24>;
> bus-width = <24>;
>
> display-timings {
>
> And now I see the U-Boot strings showing with a correct white color.
>
> However, the logo does not print and I have the following error:
>
> Error: 32 bit/pixel mode, but BMP has 8 bit/pixel
>
> How can I fix this mismatch?
Now I see that bitmap rendering code for video-uclass driver
doesn't support displaying 8bpp bitmaps on 24bpp frame buffer.
Before DM_VIDEO conversion cfb_console driver was used and
it supports such rendering. I'm working on a fix for this.
Thanks for testing!
--
Anatolij
next prev parent reply other threads:[~2020-01-25 18:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 13:19 U-Boot Logo showing incorrect colors with eLCDIF Fabio Estevam
2020-01-23 14:36 ` Anatolij Gustschin
2020-01-24 19:26 ` Fabio Estevam
2020-01-25 18:36 ` Anatolij Gustschin [this message]
2020-01-26 12:26 ` Fabio Estevam
2020-02-03 15:15 ` Fabio Estevam
2020-02-05 17:00 ` Anatolij Gustschin
2020-02-05 17:45 ` Fabio Estevam
2020-02-24 12:38 ` Fabio Estevam
2020-02-24 12:51 ` Anatolij Gustschin
2020-06-29 7:31 ` Anatolij Gustschin
2020-06-29 11:56 ` Fabio Estevam
2020-01-23 15:46 ` Oleksandr Suvorov
2020-01-25 17:31 ` Fabio Estevam
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=20200125193638.38f504fb@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