[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: New patch for video subsystem...

From: Vesa Jääskeläinen
Subject: Re: New patch for video subsystem...
Date: Thu, 09 Mar 2006 22:43:22 +0200
User-agent: Thunderbird 1.5 (Windows/20051201)

Vesa Jääskeläinen wrote:
> Yoshinori K. Okuji wrote:
>> On Friday 03 March 2006 15:23, Vesa Jääskeläinen wrote:
>>> Nowadays 1024x768 is a normal standard resolution.
>> Even if it is very popular, since the boot loader is a critical part of an 
>> operation system, the default should be set to something really safe. So I 
>> prefer 640x480. It is up to the user (or the vendor shipping GRUB) to change 
>> it to something more comfortable.
> Ok. I will change the default to that. I will only make new patch if
> there are issues to be solved before commit.

While waiting for more comments or approval I have made some changes,
but I will commit them after we have initial set of patches in.

1. Added simple caching to font manager. Implemented as a "pageing", in
initial page there is 128 entries to hold glyphs, if it there is need
for more glyphs new page will be allocated to and added as a next page.
When finding for cached glyph, it first scans root page and then
advances to next pages.

2. Added simple buffering to videoterm. If there is enough memory for
buffer layer it will allocate it and use it. When rendering, all
operations in videoterm goes first to buffer layer, and when all layers
has been rendered to it, then it renders buffer to display. If it is not
available, we will notice some flickering.

I think the next step here would be to either add bitmap loading support
(and implement rendering for it) or add more optimal rendering
possibilities to VBE driver. Is there a nice way to split vbe driver to
more source files without causing generation of more modules. I was
thinking that "optimized" versions of some blitting operations would be
good to place on some other file as source might grow to quite large.

I am open to proposals what to implement next (it could even be
something not listed here).

Also we need to decide should there be functional changes when user has
chosen indexed color modes instead of RGB mode. (Both work now, but
indexed color mode more slowly as it tries to find best indexes for RGB
values for EVERY drawn pixel :)

Vesa Jääskeläinen

reply via email to

[Prev in Thread] Current Thread [Next in Thread]