From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [PATCH] video: bmp: Support 8bits BMP to 24/32 bits display
Date: Tue, 23 Jun 2020 13:51:03 +0200 [thread overview]
Message-ID: <20200623135103.21b42c57@crub> (raw)
In-Reply-To: <CAOMZO5CXQnh38WPm-j=+r4+MPjqTgafCJs57092=6vVoSTxNzQ@mail.gmail.com>
Hi Fabio,
On Thu, 18 Jun 2020 18:04:40 -0300
Fabio Estevam festevam at gmail.com wrote:
> Hi Anatolij,
>
> On Wed, Jun 10, 2020 at 6:53 AM Ye Li <ye.li@nxp.com> wrote:
> >
> > Update video bmp codes to support 8 bits BMP to 32 bits conversion
> > so that we can display 8 bits logo on 24 bits or 32 bits display
> >
> > Signed-off-by: Ye Li <ye.li@nxp.com>
>
> I haven't had a chance to test this yet, but it seems to solve an
> outstanding splash screen issue on mx6ul evk/mx7d sabresd boards.
>
> Maybe we should get this one and the other two from Ye Li to 2020.07?
yes, we need a fix for the release, I will look later this week
which patch should be merged (we have another older patch addressing
this issue).
--
Anatolij
next prev parent reply other threads:[~2020-06-23 11:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 9:52 [PATCH] video: vidconsole: avoid multiple lines overwrite logo Ye Li
2020-06-10 9:52 ` [PATCH] splash: Fix build warning on 64 bits CPU Ye Li
2020-06-17 7:09 ` Jagan Teki
2020-06-29 7:05 ` Anatolij Gustschin
2020-06-10 9:52 ` [PATCH] video: bmp: Support 8bits BMP to 24/32 bits display Ye Li
2020-06-17 7:10 ` Jagan Teki
2020-06-18 21:04 ` Fabio Estevam
2020-06-23 11:51 ` Anatolij Gustschin [this message]
2020-06-27 22:59 ` [PATCH v2] video: bmp: support 8bits BMP drawing on 24/32 bpp framebuffer Anatolij Gustschin
2020-06-29 7:04 ` Anatolij Gustschin
2020-06-17 7:11 ` [PATCH] video: vidconsole: avoid multiple lines overwrite logo Jagan Teki
2020-06-29 7:04 ` 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=20200623135103.21b42c57@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 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.