-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable FONT_TER16x32
for better high-dpi support in VTs?
#6652
Comments
Our usual question when is feature is requested that may be only wanted by a small number, is what is the cost? Simplest is memory - after the config option is added what is the change in size of kernel8.img? Perhaps something like:
run from console in a mode that uses the new font. (before and after). Are you able to build the kernel and test this? |
Alright, I built the kernel with defaults using the
The only thing of note that I can see is the doubling of time for your suggested File size results (0.4kB smaller compressed, 65kB bigger uncompressed):
Memory:Default kernel, after fresh boot:
Built with
Default kernel, after
Built with
|
The dmesg time doubling is strange - it'll be printing the same number of lines, but twice as many vertical pixels. Is console output waiting for vsync for each line/page/weird quantum? |
Describe the bug
Could kernel config option
FONT_TER16x32
please be enabled by default?It adds in a larger font (double the size of the default) and, if compiled in, will be automatically used on high resolution displays, improving readability when needing to use a VT.
Steps to reproduce the behaviour
N/A
Device (s)
Raspberry Pi 4 Mod. B
System
OS:
Firmware:
Kernel:
Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: