public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kendall Bennett" <KendallB@scitechsoft.com>
To: linux-kernel@vger.kernel.org
Subject: Is the GIO_FONT ioctl() busted in Linux kernel 2.4?
Date: Thu, 27 Feb 2003 09:46:53 -0800	[thread overview]
Message-ID: <3E5DDE8D.14024.6FCE7D82@localhost> (raw)

Hi,

I have some old code that used to work great on older Linux 2.2 kernels 
that is now giving me a perror() error message of 'no space left on 
device' (ie: ENOSPC) when I call ioctl(GIO_FONT) to save the current 
console font.

>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). From my quick look at the code, the ENOSPC 
error must be coming because when the new code attempts to save the 
console font it must have more than 256 characters or bigger than 8x32 
pixels for the font glyphs (which is what the old font interface 
supported).

I know I can switch to the new console interfaces (which I will do once I 

determine how to do a runtime check for a 2.4 kernel so I can still use 
the old code for 2.2 and earlier kernels), but it seems to me that this 
bug should be fixed. Is anyone more familiar with the console code able 
to provide some feedback on this?

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! ~


             reply	other threads:[~2003-02-27 17:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-27 17:46 Kendall Bennett [this message]
2003-02-27 17:57 ` Is the GIO_FONT ioctl() busted in Linux kernel 2.4? Kendall Bennett
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=3E5DDE8D.14024.6FCE7D82@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