Graphics driver for Fujitsu Coral chipsets
io-graphics -d coral vid=[0x]vendor_id,did=[0x]device_id [option[,option...]] ... &
ARMLE, PowerPC, SH, x86
For the general io-graphics options that you can use with this driver, see io-graphics.
Options specific to this driver:
- The full path to the configuration file for the driver. The sample file is /usr/photon/config/coral.conf.
The devg-coral.so driver provides accelerated 2D support for the Fujitsu Coral graphics controller.
|If you install the Advanced Graphics TDK, this driver is replaced with an updated driver that works with io-display. See the Advanced Graphics TDK documentation for updated information about this driver.|
You can edit the configuration file to enable devg-coral.so to run on your board. Follow the editing instructions in the sample file, /usr/photon/config/coral.conf, to specify the correct configuration for the required display mode. (For a more detailed explanation of the display settings, see the appropriate Fujitsu documentation.)
If you use a configuration file for this driver, you must use the mode_opts option of io-graphics to specify its location. For example, mode_opts=/usr/photon/config/coral.conf.
- Fujitsu MB86294 Coral B
- Fujitsu MB86295 Coral P
- Fujitsu MB86296 Coral PA
|DPMS (power saving)||Yes|
|Display size (pixels):||Refresh rate(Hz):||Color depth (bits per pixel):|
a Requires a driver configuration file.
- You can use the driver-configuration file to specify other resolutions and refresh rates.
The coral.conf file provides additional control over the driver, including dual-head support (dual-head display is supported by Coral-PA-based devices only). This file is also required for providing additional configuration for panel displays. The file (by default located in /usr/photon/config/) contains a description of each option, and several pre-configured command-lines for various Coral device and display combinations.
For dual-head configurations, both displays will run at the same resolution/refresh rate - independent control is not available.
In coral.conf there are three parameters of note:
- dlayers -- SC0en & SC1en fields for Multi-Display Control register
- dmode -- Dual Display mode (0 = single display, 1 = dual parallel mode, 2 = dual multiplexed mode)
- dcm -- Display Clock. This needs to be configured to twice the value as would be required single display. For example, to run two 640x480 displays, change dcm=0x700 to dcm=0x300
In the Coral-PA Documentation (section 7.10 Dual Display), you'll see that the SC0-en field of the Multi-Display Control register defines which layers and cursors are included in screen 0, and the SC1-en field defines which layers and cursors are included in screen 1. A layer or cursor can be included in one or both screens.
SC0en and SC1en are 8-bit values. The dlayers parameter is 16-bit with SC1 being the top 8-bits. A 1 indicates the layer is included in the display.
The bit layout for the dlayers parameter is as follows:
|0||L0 is included in screen 0|
|1||L1 is included in screen 0|
|2||L2 is included in screen 0|
|3||L3 is included in screen 0|
|4||L4 is included in screen 0|
|5||L5 is included in screen 0|
|6||Cursor0 is included in screen 0|
|7||Cursor1 is included in screen 0|
|8||L0 is included in screen 1|
|9||L1 is included in screen 1|
|10||L2 is included in screen 1|
|11||L3 is included in screen 1|
|12||L4 is included in screen 1|
|13||L5 is included in screen 1|
|14||Cursor 0 is included in screen 1|
|15||Cursor 1 is included in screen 1|
To include all layers and cursors on both displays, set dlayers=0xFFFF (This is the default). The driver default for dmode is 0 for single display.
There are two modes to output two screens. In parallel mode, one screen is output at digital RGB while another is output at analog RGB. In multiplex mode, two screens are multiplexed and output at digital RGB. Which version is used will depend on hardware and requirements.
For example, to run in parallel mode with Layers 0, 1 and Cursor 0 on screen 0 and the rest of the layers on screen 1 you would set:
The application code needs to then connect and draw to the proper layers.
This driver needs the following at run time:
- Software rasterization library.