From: Dzmitry Sankouski <dsankouski@gmail.com>
To: u-boot@lists.denx.de
Cc: Dzmitry Sankouski <dsankouski@gmail.com>,
Anatolij Gustschin <agust@denx.de>,
Simon Glass <sjg@chromium.org>
Subject: [PATCH v5 0/1] vidconsole: refactoring and support for wider fonts
Date: Mon, 20 Feb 2023 13:49:00 +0300 [thread overview]
Message-ID: <20230220104901.1256731-1-dsankouski@gmail.com> (raw)
Version 5 contain minor changes:
- move common functions to console-core.c file
- remove static keyword from shared functions
In version 4, only first patch sent, because review fixes to this would add
large rebase & patch formatting overhead. When it'll receive reviewed tag,
I'll resent entire rebased series.
Modern mobile phones typically have high pixel density.
Bootmenu is hardly readable on those with 8x16 font.
This patch series aims to add wider fonts for devices with high ppi.
Add 16x32, 12x22 fonts from linux, and allow font size configuration.
There was significant changes in version 2:
- fix video tests failures
- add runtime font size configuration
- add test for 12x22 font
In version 3,
'video console: add select font logic to vidconsole uclass driver'
patch was removed in favor of already merged patch
'video: Add font functions to the vidconsole API'
Dzmitry Sankouski (1):
video console: refactoring and optimization
drivers/video/Makefile | 6 +
drivers/video/console_core.c | 141 +++++++++++++
drivers/video/console_normal.c | 150 ++++----------
drivers/video/console_rotate.c | 308 ++++------------------------
drivers/video/vidconsole_internal.h | 95 +++++++++
5 files changed, 324 insertions(+), 376 deletions(-)
create mode 100644 drivers/video/console_core.c
create mode 100644 drivers/video/vidconsole_internal.h
--
2.30.2
next reply other threads:[~2023-02-20 10:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 10:49 Dzmitry Sankouski [this message]
2023-02-20 10:49 ` [PATCH v5 1/1] video console: refactoring and optimization Dzmitry Sankouski
2023-02-21 16:00 ` Simon Glass
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=20230220104901.1256731-1-dsankouski@gmail.com \
--to=dsankouski@gmail.com \
--cc=agust@denx.de \
--cc=sjg@chromium.org \
--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