[lkml]   [2003]   [Feb]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Is the GIO_FONT ioctl() busted in Linux kernel 2.4?
    Followup to:  <3E5DE0FC.29370.6FD7FC8B@localhost>
    By author: "Kendall Bennett" <>
    In newsgroup:
    > "Kendall Bennett" <> 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

    <> at work, <> 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
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:33    [W:0.020 / U:17.332 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site