Configuring OpenWF Display Server
You configure the OpenWF Display server from the wfd device 1
section of your
graphics configuration (e.g., graphics.conf) file.
When you're running Screen and OpenWF Display Server on your system, you must start wfd-server before Screen by using the -c option and specifying the same graphics configuration file.
Configuring wfd device 1
section
In your configuration file, you need to specify the parameters that are related to
your display device and the OpenWF Display server. In the wfd device
1
section, ensure that you have the appropriate pipelines and libraries
specific to your display. For example,
...
begin wfd device 1
wfd-server-config-device1 = 1,2,3,4,5,6,7,9,10,11,12,13,14,15,16
wfd-server-config-device2 = 8
wfd-server-config-device2-power-ports = 1 ,2
wfd-server-config-device3-writeback-ports = 1,2
wfd-server-alloc-config = jacinto7-alloc
wfd-dlls = libWFDclient.so
wfd-server-wfd-dlls = libwfdcfg-generic.so libWFDjacinto7.so
end wfd device
...
Parameters
The following are parameters that you can configure under the wfd device 1
subsection for
OpenWF Display Server:
Parameter | Description | Type | Example/Notes |
---|---|---|---|
wfd-server-alloc-config |
The name of the platform-specific module that's used for buffer allocation. The OpenWF Display Server uses the following
algorithm to determine the allocater module to load:
Note:
|
String |
|
wfd-server-config-device%d |
Pipelines that are available for the client specified by %d to
post buffers directly to the display controller via WFD API and extensions.
Note:
Specify the client identifier %d as an integer in the range of [1..(WFD_MAX_INT-1)].
where WFD_MAX_INT is 16777216. Screen must be configured as
wfd-server-config-device1.
If you specify a pipeline identifier that's not supported by the WFD driver on your
hardware platform, wfd-server won't start. Use the -e option
to wfd-server to see a list of pipeline identifiers that are supported on
your target platform.
Use wfd-server-info for information on the current setup. |
Integer list
(comma- separated) |
Range varies based on your display device. |
wfd-server-config-device %d-power-ports |
Ports that the client specified by %d can control the power of. For example, if you specify
in your configuration,
this allows the client application that's identified as device 3 to be able to call
wfdSetPortAttribi() to set the WFD_PORT_POWER_MODE attribute
on ports 1 or 2. Otherwise, if multiple client applications are using the same port,
wfd-server may not permit a client application to change the power on that port.
Specify %d as an integer in the range of [1..(WFD_MAX_INT-1)]. where WFD_MAX_INT is 16777216. Screen must be configured as wfd-server-config-device1. |
Integer list
(comma- separated) |
Range varies based on your display device. |
wfd-server-config-device %d-writeback-ports |
Ports that the client specified by %d can use for writeback. For example, if you specify
in your configuration, this allows the client application
that's associated with device 3 to be able to use ports 1 and 2 for writeback.
Note:
Writeback support is available only to client applications that are rendering using image buffers. Writeback isn't
supported for Screen applications.
Specify %d as an integer in the range of [1..(WFD_MAX_INT-1)]. where WFD_MAX_INT is 16777216. |
Integer list
(comma- separated) |
Range varies based on your display device. |
wfd-dlls | The OpenWF Display Client library. You must specify libWFDClient.so for this parameter when you're using wfd-server. Otherwise, specify the platform-specific WFD drivers and Wfdcfg library for Screen. | String |
|
wfd-server-wfd-dlls | The platform-specific WFD drivers when you're using wfd-server. | String |
|
On your target, all platform-specific libraries that you specify in this wfd device
subsection of your
configuration file should be accessible in your library search path.
For more information on the graphics configuration file, refer to the Configuring Screen
chapter of the Screen Developer's Guide.