From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vgacon: Workaround for resize bug in some chipsets
Date: Sun, 13 Nov 2005 19:32:08 -0800 (PST) [thread overview]
Message-ID: <dl90fo$nj2$1@terminus.zytor.com> (raw)
In-Reply-To: 4377CDD8.1000509@gmail.com
Followup to: <4377CDD8.1000509@gmail.com>
By author: "Antonino A. Daplas" <adaplas@gmail.com>
In newsgroup: linux.dev.kernel
> >>
> >>
> > I think vgacon doesn't touch the 8/9 pixel setting, so the fonts are hw
> > extended to 9 pixels by VGA in many modes.
> >
>
> It's not a hardware limitation, but vgacon is hardcoded to accept fonts that are
> only 8 pixels wide. You can try it by doing a setfont.
>
The *font* is always 8 pixels wide. Whether or not you display it in
8- or 9-pixel mode is irrelevant to the formatting of the font.
In general, for vgacon, it should use the 9-pixel mode, at least by default.
-hpa
next prev parent reply other threads:[~2005-11-14 3:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <58c2Z-8jG-23@gated-at.bofh.it>
2005-11-13 19:41 ` [PATCH] vgacon: Workaround for resize bug in some chipsets Bodo Eggert
2005-11-13 22:11 ` Antonino A. Daplas
2005-11-13 22:26 ` Mika Penttilä
2005-11-13 23:35 ` Antonino A. Daplas
2005-11-14 3:32 ` H. Peter Anvin [this message]
2005-11-13 22:24 ` Samuel Thibault
2005-11-16 17:58 Jason Dravet
2005-11-16 23:52 ` Samuel Thibault
2005-11-17 1:37 ` Jason Dravet
[not found] <58DvZ-6en-1@gated-at.bofh.it>
2005-11-14 9:24 ` Bodo Eggert
2005-11-14 15:27 ` Jason Dravet
2005-11-14 16:32 ` Bodo Eggert
2005-11-16 0:05 ` Samuel Thibault
2005-11-16 1:50 ` Jason Dravet
2005-11-16 2:25 ` Samuel Thibault
-- strict thread matches above, loose matches on Subject: below --
2005-11-14 3:46 Jason Dravet
2005-11-12 22:20 Antonino A. Daplas
2005-11-13 10:23 ` Martin Mares
2005-11-13 11:06 ` Samuel Thibault
2005-11-13 14:33 ` Antonino A. Daplas
2005-11-13 22:25 ` Samuel Thibault
2005-11-13 23:37 ` Antonino A. Daplas
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='dl90fo$nj2$1@terminus.zytor.com' \
--to=hpa@zytor.com \
--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