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

[Sottek, M. J <mat...@in...>]

>No. fbdev app can leave hardware in any state.

Right, but the fbdev driver needs to save the full context between
VT's. The di portion saves all the mode info but you may have to
save a bunch of other context information if you are doing accel.

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

>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.

I like this better than blocking the app. Blocking can cause
unexpected behavior since almost no app is expecting to block on
a memory write.

-Matt