[lcdproc] Bug: Framebuffer Allocation

[joris@robijn.net]

> Only one did the "right" thing: it freed the framebuffer and reallocated
> it, because the framebuffer was the wrong size.

The framebuffer is a queer thing. Appertly the driver and the server 
can freely read and write it. I would more like to see some 
separation. 

If it's in the driver, only the driver should be able to access it 
directly. The server should then do so by calling functions to read 
and write it. 

Another way to go would be the framebuffer in the server. If you 
want to think deeper about this, keep in mind that we might want to 
go to graph-lcds one day, and that text-lcds have different 
character sizes. So the fb-stuff needs a lot of thought anyway.

All this requires work, and maybe it's better to keep this for 0.5

Anyway, it's good to see that you have already made a start by 
cleaning up the allocation thing. It's the top of the fb-iceberg (not 
meant to discourage you, but it might do so ;).

Joris

-- 
 Joris Robijn <joris@robijn.net>
 Home: 053 4311 553
 Mobile: 06 288 41 964

 // To understand recursion, we must first understand recursion


-----------------------------------------------------------
To unsubscribe from this list send a blank message to
lcdproc-unsubscribe@lists.omnipotent.net