lkml.org 
[lkml]   [2007]   [May]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: console font limits
    On Tue, 1 May 2007, Albert Cahalan wrote:
    > I'm having problems with a font I just created. It's a rather big one,
    > intended for a framebuffer console in UTF-8 mode. The strace program
    > reports that /bin/setfont fails on a KDFONTOP ioctl with EINVAL.
    > In reading the kernel code, I find this:
    >
    > vt.c:static int con_font_set(struct vc_data *vc, struct console_font_op *op)
    > vt.c-{
    > vt.c- struct console_font font;
    > vt.c- int rc = -EINVAL;
    > vt.c- int size;
    > vt.c-
    > vt.c- if (vc->vc_mode != KD_TEXT)
    > vt.c- return -EINVAL;
    > vt.c- if (!op->data)
    > vt.c- return -EINVAL;
    > vt.c- if (op->charcount > 512)
    > vt.c- return -EINVAL;
    >
    > Ouch. Why is the old VGA limit being applied to the framebuffer console?
    > Could this just get removed? I dearly hope we aren't still storing the
    > framebuffer data as two bytes per character+attribute pair.

    The shadow screen (accessed using scr_*()) still uses the old VGA
    format.

    Gr{oetje,eeting}s,

    Geert

    --
    Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

    In personal conversations with technical people, I call myself a hacker. But
    when I'm talking to journalists I just say "programmer" or something like that.
    -- Linus Torvalds
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2007-05-01 13:51    [W:0.021 / U:0.060 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site