From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [PATCH 2/2] video: make BPP and ANSI configs optional
Date: Thu, 5 Dec 2019 19:32:45 +0100 [thread overview]
Message-ID: <20191205193245.6e0eadd1@crub> (raw)
In-Reply-To: <20191205171549.15170-2-agust@denx.de>
On Thu, 5 Dec 2019 18:15:49 +0100
Anatolij Gustschin agust at denx.de wrote:
> Many boards do not use all selected framebuffer depth
> configurations, for such boards there is some unused
> code in video and console uclass routines. Make depth
> specific code optional to avoid dead code and slightly
> reduce binary size. Also make ANSI code optional for
> the same reason. When i.e. using only VIDEO_BPP16 the
> code size shrinks (below values when using gcc-7.3.0):
>
> $ ./tools/buildman/buildman -b video-wip -sS wandboard
> ...
> 01: Merge git://git.denx.de/u-boot-sh
> 02: video: add guards around 16bpp/32bbp code
> 03: video: make BPP and ANSI configs optional
> arm: (for 1/1 boards) all -776.0 bss -8.0 text -768.0
>
> Also adjust defconfigs of DM_VIDEO enabled boards to select
> actually used BPP values.
Forgot to CC board maintainers. Maybe you could review or test these
two patches [1],[2] on your board to confirm that these don't break
frame buffer support.
[1] http://patchwork.ozlabs.org/patch/1204707
[2] http://patchwork.ozlabs.org/patch/1204704
Thanks,
Anatolij
next prev parent reply other threads:[~2019-12-05 18:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 17:15 [PATCH 1/2] video: add guards around 16bpp/32bbp code Anatolij Gustschin
2019-12-05 17:15 ` [PATCH 2/2] video: make BPP and ANSI configs optional Anatolij Gustschin
2019-12-05 18:32 ` Anatolij Gustschin [this message]
2019-12-09 14:46 ` Steffen Dirkwinkel
2019-12-06 13:44 ` Eugen.Hristev at microchip.com
2019-12-06 14:21 ` Patrice CHOTARD
2019-12-10 10:27 ` Anatolij Gustschin
2019-12-10 10:25 ` [PATCH 1/2] video: add guards around 16bpp/32bbp code 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=20191205193245.6e0eadd1@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