> On Mon, 20 Jan 2003, Fabio Alemagna wrote: > > > On Mon, 20 Jan 2003, Brian S. Julin wrote: > > > > Stupid question from an outsider: couldn't it be possible to make the > > application still run by making it use an offscreen buffer while not > > "visible" because of VT switching? It would be really annoying, imho, > > if the application stopped altogether... > > Yeah, nice... My 32 MB Matrox deals with 4 devices, which means you need > 4x32 MB = 128 MB offscreen for that one alone. Glad I don't own a 128 MB > ATI 9700 ... my box got only 256 MB... > > And now serious: Nice idea, but doesn't work. As you can see above, fake > framebuffers are no good but for text modes. If we really want to make a > chance to make it in any kernel, we should come up with something better.
How about using the memory target within libggi's kgi-target, when the application runs in background? This "background mode" can be done by copying first waiting until the accel is idle, then copying the framebuffer content into the userspace memory obtained by the memory target. Then the application can continue reading/ writing from/to the "framebuffer" in the background. Once it falls into foreground again, simply copy the emulated framebuffer to the real framebuffer. In short words: Framebuffer access should happen by transparent proxy from the GGI applications view. "Transparently", because this proxy mechanism is within the kgi-target and thus hidden to the GGI application. The big question is, if this will still work, once libggiovl becomes useable and the GGI apps requests overlay resources such as hw-sprites and/or YUV-viewports... -- CU, Christoph Egger E-Mail: [EMAIL PROTECTED] +++ GMX - Mail, Messaging & more http://www.gmx.net +++ NEU: Mit GMX ins Internet. Rund um die Uhr für 1 ct/ Min. surfen!
