From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: Missing BMP 565RGB video support
Date: Tue, 1 Sep 2020 13:07:45 +0200 [thread overview]
Message-ID: <20200901130745.68f9aa3d@crub> (raw)
In-Reply-To: <DB7PR03MB3770912AF3430298098CAC6CA0520@DB7PR03MB3770.eurprd03.prod.outlook.com>
Hi,
On Fri, 28 Aug 2020 10:44:55 +0000
Trommel, Kees (Contractor) kees.trommel.contractor at draeger.com wrote:
> Hi Agust,
>
> The latest version of the U-Boot does not support conversion from
> 24BPP BMP to a 16BPP 565RGB encoded frame buffer. It uses always
> 555RGB encoding (see function video_bmp_display in video_bmp.c).
> Older versions of the U-Boot (e.g. 2015.04) supported this because
> the platform specific device driver passed not only the BPP but
> also the encoding.
in recent U-Boot we do not use old cfb_console driver which
supported 24bpp bitmaps. The DM video console driver still
dosn't support some framebuffer/bitmap BPP combinations, or
maybe your board config file does not define CONFIG_BMP_24BPP.
> Do you know whether this lost support was done on purpose
> or lost by accident?
This is probably due to DM video conversion, not all BPP
variants have been implemented with this yet.
> I encountered this issue when trying to display a 24BPP BMP
> splash screen at an i.MX6 platform.
Did you define CONFIG_BMP_24BPP in your board config file?
If not, could you do so and test the result? Thanks.
--
Anatolij
next prev parent reply other threads:[~2020-09-01 11:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 10:44 Missing BMP 565RGB video support Trommel, Kees
2020-09-01 11:07 ` Anatolij Gustschin [this message]
2020-09-02 8:29 ` Trommel, Kees
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=20200901130745.68f9aa3d@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