From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Is the GIO_FONT ioctl() busted in Linux kernel 2.4?
Date: 27 Feb 2003 17:02:29 -0800 [thread overview]
Message-ID: <b3mcf5$629$1@cesium.transmeta.com> (raw)
In-Reply-To: 3E5DE0FC.29370.6FD7FC8B@localhost
Followup to: <3E5DE0FC.29370.6FD7FC8B@localhost>
By author: "Kendall Bennett" <KendallB@scitechsoft.com>
In newsgroup: linux.dev.kernel
>
> "Kendall Bennett" <KendallB@scitechsoft.com> wrote:
>
> > From looking at the 2.4 kernel source code that comes with Red
> > Hat 8.0, it is clear that these functions are implemented on top
> > of a new console font interface that supports 512 characters and
> > up to 32x32 pixel fonts (obviously for fb consoles).
>
> Yep, after further investigation the problem is that the VGA console is
> configured to run with 512 characters, yet the 'old' interface code is
> trying to save/restore only 256 characters so it fails. It could be fixed
> if it was changed to save/restore 512 characters, but I don't know if
> that will break old code (it won't break mine as I always uses a 64K
> buffer to save/restore the font tables).
>
It will break old code. That's why you've been supposed to use
GIO_FONTX (and GIO_UNISCRNMAP) since the 1.3.1 kernel days (which is
when 512-character support was introduced.)
You're *way* behind the times.
man 4 console_ioctl
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: cris ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
next prev parent reply other threads:[~2003-02-28 0:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 17:46 Is the GIO_FONT ioctl() busted in Linux kernel 2.4? Kendall Bennett
2003-02-27 17:57 ` Kendall Bennett
2003-02-28 1:02 ` H. Peter Anvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-26 21:53 Kendall Bennett
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='b3mcf5$629$1@cesium.transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.