From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Helge Deller <deller@gmx.de>
Cc: linux-kernel@vger.kernel.org, Daniel Vetter <daniel@ffwll.ch>,
Alexey Gladkov <legion@kernel.org>,
Jiry Slaby <jirislaby@kernel.org>,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] fbcon: Increase maximum font width x height to 64 x 64
Date: Sat, 16 Mar 2024 01:12:52 +0100 [thread overview]
Message-ID: <20240316001251.l3ifu5exkrjmbhoe@begin> (raw)
In-Reply-To: <d7ca4ae3-4bcc-49f0-a819-4ad88907b93c@gmx.de>
Hello,
Helge Deller, le ven. 15 mars 2024 10:35:40 +0100, a ecrit:
> You should have marked this patch with "v2"...
The actual changes were exactly the same.
> On 3/13/24 17:59, Samuel Thibault wrote:
> > This remains relatively simple by just enlarging integers.
>
> I like the patch, but I still see some u32...
> drivers/video/fbdev/vt8623fb.c: info->pixmap.blit_x = (bpp == 4) ? (1 << (8 - 1)) : (~(u32)0);
> drivers/video/fbdev/arkfb.c: info->pixmap.blit_x = (bpp == 4) ? (1 << (8 - 1)) : (~(u32)0);
> drivers/video/fbdev/core/fbmem.c: fb_info->pixmap.blit_x = ~(u32)0;
> drivers/video/fbdev/s3fb.c: info->pixmap.blit_x = (bpp == 4) ? (1 << (8 - 1)) : (~(u32)0);
Oops, I missed including these modifications indeed.
> > It wouldn't be that simple to get to the console's 64x128 maximum, as it would
> > require 128b integers.
>
> How realistic are fonts > 64x64 pixels ?
With 4K displays, 64x128 brings 60x16 text console, which is useful for
people with low vision.
> If they are, using the bitmap_xx functions (include/linux/bitmap.h)
> now instead would be better.
Ok, I have now done this in v2. We'll be able to easily increase the
font size when 8K displays get out :)
Samuel
next prev parent reply other threads:[~2024-03-16 0:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 16:59 [PATCH] fbcon: Increase maximum font width x height to 64 x 64 Samuel Thibault
2024-03-15 9:35 ` Helge Deller
2024-03-16 0:12 ` Samuel Thibault [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-12 21:39 Samuel Thibault
2024-03-13 16:45 ` Luca Ceresoli
2024-03-13 16:55 ` Samuel Thibault
2024-03-13 17:06 ` Samuel Thibault
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=20240316001251.l3ifu5exkrjmbhoe@begin \
--to=samuel.thibault@ens-lyon.org \
--cc=daniel@ffwll.ch \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=jirislaby@kernel.org \
--cc=legion@kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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