[Top][All Lists]

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

Re: Fwd: [PATCH 1/2] Framebuffer split

From: Michal Suchanek
Subject: Re: Fwd: [PATCH 1/2] Framebuffer split
Date: Sat, 1 Aug 2009 16:50:59 +0200

2009/8/1 Robert Millan <address@hidden>:
> On Fri, Jul 31, 2009 at 10:31:07PM +0200, Vladimir 'phcoder' Serbinenko wrote:
>> > Well, that fits the definition of backend.
>> >
>> But there are other backends too - network backend, opengl backend, ...
>> Framebuffer is a term often used to designated memory ranged which is
>> mapped to the screen.
> Ok then.  I think I got confused by the common usage of this term, which
> often refers to the whole thing.  I'm fine with it, as long as it's used
> consistently.

Yes, I can agree with "framebuffer" being used for the memory storing
the display data, X has fb library, many other graphics libraries have
bf handling routines but the most well known one is the Linux
"framebuffer console" - the console using the Linux framebuffer

>> May we stop discussing about names and rather either commit or discuss
>> technical details?
> Names are very important.  When someone who's not familiar with the code
> is trying to figure it out, if the name of a function or an interface
> inmediately evokes an idea of what it does, that person won't have to
> check.  It makes working with GRUB much more efficient.

For me backend is just something generic that can do just about
anything (even compilers have a backend) but framebuffer evokes the
thought of rectangular memory area storing the picture shown on the



reply via email to

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