From: eric@anholt•net (Eric Anholt)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 3/4] drm/pl111: Handle the RealView variant separately
Date: Mon, 05 Mar 2018 16:34:44 -0800 [thread overview]
Message-ID: <87vaeanisb.fsf@anholt.net> (raw)
In-Reply-To: <20180302090948.6399-4-linus.walleij@linaro.org>
Linus Walleij <linus.walleij@linaro•org> writes:
> We want to cut down the default bpp to 16 on the RealView so
> we can have a 1024x768 framebuffer console by default. The
> memory bandwidth limitations makes this not work with the
> PL111 default of 32bpp.
>
> This builds on top of the earlier patches making the
> framebuffer default bpp a per-variant variable.
>
> Signed-off-by: Linus Walleij <linus.walleij@linaro•org>
Reviewed-by: Eric Anholt <eric@anholt•net>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180305/0f62d6df/attachment.sig>
next prev parent reply other threads:[~2018-03-06 0:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 9:09 [PATCH 0/4] drm/pl111: RealView and Versatile Express Linus Walleij
2018-03-02 9:09 ` [PATCH 1/4] drm/pl111: Make the default BPP a per-variant variable Linus Walleij
2018-03-02 9:09 ` [PATCH 2/4] drm/pl111: Use max memory bandwidth for resolution Linus Walleij
2018-03-06 0:29 ` Eric Anholt
2018-03-02 9:09 ` [PATCH 3/4] drm/pl111: Handle the RealView variant separately Linus Walleij
2018-03-06 0:34 ` Eric Anholt [this message]
2018-03-02 9:09 ` [PATCH 4/4] drm/pl111: Support the Versatile Express Linus Walleij
2018-03-02 12:11 ` [PATCH 0/4] drm/pl111: RealView and " Robin Murphy
2018-03-02 12:37 ` Linus Walleij
2018-03-02 13:50 ` Robin Murphy
2018-03-02 15:43 ` Liviu Dudau
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=87vaeanisb.fsf@anholt.net \
--to=eric@anholt$(echo .)net \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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