Re: Design for setting video modes, ownership of sysfs attributes

[Keith Packard <keithp@keithp.com>]

[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]


Around 12 o'clock on Sep 19, Jon Smirl wrote:

> This is going to require some more thought. Mode setting needs two
> things, a description of the mode timings and a location of the scan
> out buffer.  With multiple heads you can't just assume that the buffer
> starts at zero.  There also the problem of the buffer increasing in
> size and needing to be moved since it won't fit where it is.
> 
> Keith, how should this work for X?

I just need to know where the frame buffer lives; it can move or change 
pitch at any time.  I can even deal with the frame buffer moving without 
warning if necessary.  What I can't handle is off-screen memory suddenly 
disappearing on me; I need to be able to pull any off-screen data back to 
main memory before things get shuffled around.

This, of course, is related rather strongly with any memory management 
system, for which I'd like to have applications allocate main-memory space 
for any off-screen resources so that the kernel can pull things off the 
video card without needing cooperation from the X server at switch time.

-keith



[-- Attachment #2: Type: application/pgp-signature, Size: 228 bytes --]