Re: [RFC] drm: add kernel-log renderer

[David Herrmann]

Hi

>> I don't think it makes sense to modify drm_log_ensure_size(). I mean,
>> the worst that can happen is that the *text*-backlog is twice as big
>> as required. But if you have a high-dpi display, you already require
>> like 10x as much space for each framebuffer than for the entire
>> log-buffer. The log-buffer requires 1 byte per *char*. The frambuffer
>> requires at least 8*16*4=512 bytes per char.
>
> That's fair, especially as drm_log_ensure_size() is grow-only.
>
>> Anyhow, integer-scaling should be fairly easy to get done.
>
> I thought providing the font to drm_log_draw() and express
> drm_log_ensure_size() in chars - or pass font to it as well - would be
> easier than scaling.

There are no real high-res fonts in ./lib/fonts/ so I don't think
that's an option. Besides, we don't want high-res fonts, we just want
bigger fonts so scaling seems fine.

Thanks
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/