Hi,
I got it to work, thanks. It's now proudly working with multiple
processes :)
Sorin
Niels Roest wrote:
Hi Sorin.
The master/slave distinction is your own decision.
For software-handling, there is no difference. There is just locking
to prevent applications writing at the same time.
If you have a piece of hardware that can be opened only once, you need
to put the hardware handling in the master process, but the "soft"
handling, like checking, and changing data structures, can be done in
the slaves too.
The functions should have an implementation both in the master and the
slave, the graphics driver is itself responsible for passing data
around using shared memory and synchronising using locking or calls.
Greets
Niels
Sorin Otescu wrote:
Hi,
I'm trying to rewrite my DirectFB 1.4.2 driver to make it work with
multiple processes. It's going well, but it's not clear to me exactly
what layer functions are required in the slave processes. It is my
understanding that the master is the one who configures the hardware;
the slaves shouldn't even touch the layer configuration. Is it legal
for the slaves to configure layers themselves? SaWMan seems to be
doing precisely that.
If I don't implement any layer functions in the slave (just set NULL
pointers for every function) will it work? Is it even correct?
Thanks,
Sorin
_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
