public inbox for linux-fbdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Pavel Nikulin <pavel@noa-labs.com>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-fbdev@vger.kernel.org,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Simona Vetter <simona@ffwll.ch>
Subject: Re: [PATCH v5 RESEND] Fonts: Adding all Terminus fronts from 12 to 32 in bold, and normal versions
Date: Tue, 10 Mar 2026 17:56:23 +0100	[thread overview]
Message-ID: <5b04fe68-e953-44a5-8d3f-ac826242e332@gmx.de> (raw)
In-Reply-To: <20260310123327.9172-2-pavel@noa-labs.com>

Hello Pavel,

On 3/10/26 13:24, Pavel Nikulin wrote:
>> Why are both bold and non-bold fonts needed?
> 
> Because people have different screen densities. On those 4k 10 inch screens, people would probably go for bolder versions regardless of how much text they want to fit in.

Yes, but is there so much difference between 10x18, 10x18b,10x20,10x20b ?
I mean, this is a whole lot of source code (bloat?) which we would add to the kernel sources.
Even more worse, if most people won't even compile it then....

Just looking at the number of possible fonts, I wouldn't know which one to use myself:

  lib/fonts/font_ter10x18.c  | 6412 ++++++++----------------------------
  lib/fonts/font_ter10x18b.c | 1305 ++++++++
  lib/fonts/font_ter10x20.c  | 1305 ++++++++
  lib/fonts/font_ter10x20b.c | 1305 ++++++++
  lib/fonts/font_ter11x22.c  | 1561 +++++++++
  lib/fonts/font_ter11x22b.c | 1561 +++++++++
  lib/fonts/font_ter12x24.c  | 1561 +++++++++
  lib/fonts/font_ter12x24b.c | 1561 +++++++++
  lib/fonts/font_ter14x28.c  | 1817 ++++++++++
  lib/fonts/font_ter14x28b.c | 1817 ++++++++++
  lib/fonts/font_ter16x32.c  | 4107 +++++++++++------------
  lib/fonts/font_ter16x32b.c | 2073 ++++++++++++
  lib/fonts/font_ter6x12.c   |  537 +++
  lib/fonts/font_ter8x14.c   |  537 +++
  lib/fonts/font_ter8x14b.c  |  537 +++
  lib/fonts/font_ter8x16.c   |  537 +++
  lib/fonts/font_ter8x16b.c  |  537 +++

>> They may be loaded after bootup via userspace too.

And I still believe, that the fbconsole usually is used for:
a) older historic machines which can't use DRM/DRI, and
b) simple devices / embedded devices which still use fbdev, and
c) probably the majority: new x86 machines with DRM where it's only used shortly for bootup until graphical login appears.

For a) I believe the current fonts are sufficient (and mimic the architecture).
For b) I believe one of the current fonts will be hardcoded by the vendor.
For c) I think most people don't care about the additional fonts.

> Too many fonts are already baked into the kernel, and I would've
> advocated for eventually adding a function for PSFs to be more
> easily added at config, or boot time.

Yes, a function to compile in some PSF-font at build-time would
probably be more useful?

All that said, my believe is that we already ship enough fonts
and don't need a whole bunch of additional fonts.

Any opinions from dri-devel folks on that?

> Terminus is a good font for the kernel for the reason that it covers a very wide range of font sizes.
> 
> On the sidenote, the previously incorporated Terminus font patch seemingly has a wrong FONTDATAMAX value

Do you want to send a patch?

Helge

  parent reply	other threads:[~2026-03-10 16:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260226073404.13511-1-pavel@noa-labs.com>
2026-02-27 20:59 ` [PATCH v5] Fonts: Adding all Terminus fronts from 12 to 32 in bold, and normal versions Helge Deller
2026-03-10 12:24   ` [PATCH v5 RESEND] " Pavel Nikulin
2026-03-10 12:24     ` [PATCH v5] " Pavel Nikulin
2026-03-10 16:56     ` Helge Deller [this message]
2026-03-11  7:53   ` Thomas Zimmermann

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=5b04fe68-e953-44a5-8d3f-ac826242e332@gmx.de \
    --to=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@noa-labs.com \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.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