From: "Kendall Bennett" <KendallB@scitechsoft.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Is the GIO_FONT ioctl() busted in Linux kernel 2.4?
Date: Thu, 27 Feb 2003 09:57:16 -0800 [thread overview]
Message-ID: <3E5DE0FC.29370.6FD7FC8B@localhost> (raw)
In-Reply-To: <3E5DDE8D.14024.6FCE7D82@localhost>
"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).
Can someone who is more experienced with the kernel describe how this can
be properly patched?
I have worked around the problem in my code by simply switching to the
new interface (KDFONTOP), but I would like to know what kernel version
this new interface showed up in. If it was in the 2.0 or even 2.2 kernels
that would be fine since that goes back far enough for the support we
need.
Regards,
---
Kendall Bennett
Chief Executive Officer
SciTech Software, Inc.
Phone: (530) 894 8400
http://www.scitechsoft.com
~ SciTech SNAP - The future of device driver technology! ~
next prev parent reply other threads:[~2003-02-27 17:47 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 [this message]
2003-02-28 1:02 ` H. Peter Anvin
-- 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=3E5DE0FC.29370.6FD7FC8B@localhost \
--to=kendallb@scitechsoft.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