From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [PATCH 1/5] video: x86: Enable 32-bit graphics by default
Date: Fri, 3 Jan 2020 17:16:49 +0100 [thread overview]
Message-ID: <20200103171649.714dc921@crub> (raw)
In-Reply-To: <CAEUhbmWaPn+q=qKKUA3fouoGJxpANK8LWAH1nZ8Q_bBNKQ3MCA@mail.gmail.com>
Hi all,
On Fri, 3 Jan 2020 23:41:49 +0800
Bin Meng bmeng.cn at gmail.com wrote:
> Hi Simon,
>
> On Fri, Jan 3, 2020 at 11:24 AM Simon Glass <sjg@chromium.org> wrote:
> >
> > Hi Bin,
> >
> > On Thu, 2 Jan 2020 at 19:41, Bin Meng <bmeng.cn@gmail.com> wrote:
> > >
> > > Hi Simon,
> > >
> > > On Fri, Jan 3, 2020 at 10:30 AM Simon Glass <sjg@chromium.org> wrote:
> > > >
> > > > Hi Anatolij,
> > > >
> > > > On Thu, 2 Jan 2020 at 07:34, Anatolij Gustschin <agust@denx.de> wrote:
> > > > >
> > > > > Hi Simon,
> > > > >
> > > > > On Fri, 20 Dec 2019 18:10:33 -0700
> > > > > Simon Glass sjg at chromium.org wrote:
> > > > >
> > > > > > Most x86 boards that use video make use of 32bpp graphics. Enable this by
> > > > > > default. This fixes missing graphics output on some x86 boards.
> > > > >
> > > > > Must this patch be applied for v2010.01 release?
> > > >
> > > > I think so since these boards don't work for me at present.
> > > >
> > > > What do you think, Bin?
> > > >
> > >
> > > Which board is currently broken due to missing this config? Should it
> > > be safer to move this to board defconfig?
> >
> > I think any x86 board with graphics would need this. Those that don't
> > enable VIDEO won't get the change anyway.
>
> OK, thanks. I had a test with QEMU x86 and looks good.
>
> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
> Tested-by: Bin Meng <bmeng.cn@gmail.com>
Thanks for testing. I've submitted a pull request for this series
and Tom already merged the patches in master.
--
Anatolij
next prev parent reply other threads:[~2020-01-03 16:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-21 1:10 [PATCH 0/5] video: Avoid #ifdef to increase build coverage Simon Glass
2019-12-21 1:10 ` [PATCH 1/5] video: x86: Enable 32-bit graphics by default Simon Glass
[not found] ` <20200102153306.59fd28f9@crub>
2020-01-03 2:29 ` Simon Glass
2020-01-03 2:41 ` Bin Meng
2020-01-03 3:24 ` Simon Glass
2020-01-03 15:41 ` Bin Meng
2020-01-03 16:16 ` Anatolij Gustschin [this message]
2019-12-21 1:10 ` [PATCH 2/5] video: Avoid using #ifdef in video blitting code Simon Glass
2019-12-21 1:10 ` [PATCH 3/5] video: Avoid using #ifdef in console_rotate.c Simon Glass
2019-12-21 1:10 ` [PATCH 4/5] video: Avoid using #ifdef in vidconsole-uclass.c Simon Glass
2019-12-21 1:10 ` [PATCH 5/5] video: Avoid using #ifdef in video-uclass.c Simon Glass
2020-01-04 10:45 ` [PATCH 0/5] video: Avoid #ifdef to increase build coverage 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=20200103171649.714dc921@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