I am pursuing my research into directFB - I have some questions:
Q. Is there any examples of providing DLCAPS_WINDOWS ?
My understanding is that normally dfb will render down all windows'
surfaces to the layer's surface and the gfxdriver will be requested to
present the new page (region).
What happens if DLCAPS_WINDOWS is set? Any caveats in using hardware
windowing?
Q. Currently I am setting DLCAPS_SURFACE and using surfaces for my layer
content. How would I provide my own content to a layer?
i.e. I note this comment: "/* The layer has a surface that can
be drawn to. This may not be provided by layers that display realtime data,
e.g. from an MPEG decoder chip. Playback control may be provided by an
external API. */"
Specifically, I am considering how I might architect the following using
directFB:
DirectFB
--> Layer1 (Surface) --> GfxDriver --> Screen
--> Layer2 (Surface) --> GfxDriver --> Screen
--> Layer3 (Surface) --> GfxDriver --> Screen
In this set up I have a GUI that composites 3 layers. But Layer2 is to
contain a DRM surface. How do I attach my private surface to a layer?
To achieve this I'd (notionally) like to be able to create a CoreSurface
that represents a private allocation that is not managed by dfb's manager
and that is not valid for software read/writes.
I'd then like to 'attach' this to a layer such that my GfxDriver/Hardware
can resolve the arrangement while still preserving security on the Layer2
contents.
Is this possible using existing interfaces? If not, is there any other
existing or better way to achieve this?
Regards,
Jason Barstow.
Notice
The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
message by anyone else is unauthorized. If you are not the intended
recipient, any disclosure, copying or distribution of the message, or
any action taken by you in reliance on it, is prohibited and may be
unlawful. If you have received this message in error, please delete it
and contact the sender immediately. Thank you.
_______________________________________________
directfb-dev mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
