James Dickson II wrote:
> Denis
> I have implemented the gfxdriver and a special system module to do
> reads/writes from the surface created by our usb hardware.
Great, how is it performing, especially df_dok and df_andi?
> But we still have a question on primary screens and to register a layer
> on it from our system module.
>
> I see that some system modules create the screen and register a primary
> layer.
>
> registering for screen functions is understandable (Especially
> returning the screen size and supporting power modes), But what would be
> the main purpose of creating a primary layer on top of the screen?
You did not register a layer implementation?
The core should have said:
(!) IDirectFB_Construct: No layers available! Missing driver?
At least one layer is required to show anything on the screen, but it can
also be registered by the graphics driver, e.g. using the devmem system
module requires that, while the fbdev system module provides a common
implementation for the primary layer via /dev/fb with additional layers
optionally registered by the drivers, though they can also replace the
dirty fbdev layer with something more sophisticated and architecturally
cleaner, especially when there are additional layers in the driver anyhow.
Did you make sure that your system module and driver got selected?
--
Best regards,
Denis Oliver Kropp
.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/ |
"------------------------------------------"
_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
