|
From: Geert U. <ge...@li...> - 2002-12-22 08:44:36
|
On 15 Dec 2002, Antonino Daplas wrote:
> On Fri, 2002-12-13 at 15:09, Petr Vandrovec wrote:
> > Current interface just supports only cfb, and only very bad for my needs.
> > And because of matroxfb supports also other modes (such as native text
> > mode, or loading font into accelerator), bye-bye. For now I recommend you
> > either to not upgrade, or use vesafb. Besides that accel_putcs() does not
> > call fb_sync when using font width which is not multiple of 8, and that
> Can you explain why an fb_sync is needed for every character?
>
> > with fonts greater than 16*16 pixels (I believe that such fonts are still
> > supported...) it will corrupt memory...
>
> I agree. To be more specific, buffer overruns will occur if (xres *
> fontheight/8 > 8192). The pixmap needs to be dynamically allocated and
> resized somewhere in the fbcon layer (ideally in accel_setup(), but this
> was removed). For those concerned about this problem, you can try this
> patch as a temporary measure until fbcon is fixed. It should not cause
> to much slowdown:
What about making putcs() check for overflows? I.e. large putcs() will just be
split in multiple image blit calls.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...
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
|