Hm, if we both had the same idea seperately, it must be right :-)

I don't understand your point about the display communicating with the DSP. It must be the player that finds out when to update the screen, and does an ioctl to the /dev/display.

You say that the /dev/dísplay is used as a memory-mapped device. But the device is accesed like a file, wouldn't it be possible to mimic this behaviour in a daemon of some sort. I should monitor /dev/display1 for contents, and when a program does an ioctl to this 'file' it should copy the contents to /dev/display and repeat the ioclt (presumed that we want to display this screen).

So the question would be, is it required that the /dev/display0 is monitored by a kernel device driver, or could this be done in a daemon?

Also, is there any special requirements for a file to be mapped into memory?


Lars Karlslund