RE: [Linux-fbdev-devel] API prototype doc

[Petr V. <VAN...@vc...>]

On  5 Dec 01 at 10:43, Sottek, Matthew J wrote:

> The dri works this way already but on a per client basis, we need
> it on a per VT basis.

All commands your fbdev API presents are not context sensitive. At least
it looks that way to me. After console switch all on-screen and off-screen
memory is lost. 

Only thing we can do is that if app told us that it uses new semantic 
(/dev/null mmap replacing, f.e.), after framebuffer returns back it 
must confirm it with some action (mmaping of /dev/fb, or some fb API 
action), and until it confirms it, decline to execute any of commands
submitted, as it is 100% sure that app did not restore its context yet.

> >I think that replacing mapping with /dev/null one (and delivering
> >signal) is better
> 
> So you are saying, instead of blocking the app when it writes, just
> map it over to /dev/null and allow the app the continue.

Yes.
                                                Petr Vandrovec
                                                van...@vc...