genode

History

Norman Feske 366bba0227 Exclude higher-level repos from strict warnings This is a follow-up commit to "Increase default warning level", which overrides Genode's new default warning level for targets contained in higher-level repositories. By explicitly whitelisting all those targets, we can selectively adjust them to the new strictness over time - by looking out for 'CC_CXX_WARN_STRICT' in the target description files. Issue #465		2018-01-17 12:14:36 +01:00
..
include	intel_fb: support forced virtual framebuffer size	2017-10-05 17:39:59 +02:00
README	intel_fb_drv: make buffering mandatory	2016-06-28 11:09:27 +02:00
dummies.c	intel_fb: avoid assertion on X201	2017-10-05 17:40:00 +02:00
gen_dummy	dde_linux: update intel_fb to 4.4.3	2016-05-26 15:54:13 +02:00
i915_params.c	Adjust file headers to refer to the AGPLv3	2017-02-28 12:59:29 +01:00
lx_emul.cc	intel_fb: optionally respect connector hz config	2017-10-05 17:39:59 +02:00
lx_emul_c.c	Adjust file headers to refer to the AGPLv3	2017-02-28 12:59:29 +01:00
main.cc	ldso: defer execution of static constructors	2017-03-24 16:20:04 +01:00
target.mk	Exclude higher-level repos from strict warnings	2018-01-17 12:14:36 +01:00

README

This driver is for Intel i915 compatible graphic cards.

Default behaviour
~~~~~~~~~~~~~~~~~
When no configuration is provided to the driver, it will switch on all devices
the graphic card is initially connected to. It will use the best resolution as
provided by the BIOS or EDID information from the display devices for each
connector. The virtual resolution delivered to the client is the maximum in
width and height of the different connectors. The framebuffer memory is
directly exported to the client of the driver. When newly connected devices are
detected by the hardware, the new connectors are enabled, probed, and again the
'best' resolution will be chosen for the device. Nevertheless, it won't have an
effect on the virtual resolution.

Configuration
~~~~~~~~~~~~~
Each of the connector can be configured explicitly in terms of resolution and
whether it should be enabled or not. This looks like the following:

! <config>
!   <connector name="LVDS-11" width="1280" height="800" enabled="true"/>
! </config>

When the configuration changes during run-time, the driver will adapt to it. In
this case it will also change the current virtual resolution to the maximum of
the configured resolutions in width and height, and it will inform its client
about the change in resolution.

If you experience problems like hotplugging of connectors does not work, you
can force the driver to poll frequently for hotplug events by defining a period
in milliseconds like this:

! <config poll="1000"/>

If you define a period of zero, the driver won't poll at all, which is the
default value.

To present all available connectors and their possible resolutions to the user
the driver is able to export a corresponding report ROM. This has to be
configured too, like in the following:

! <config>
!   <report connectors="yes"/>
! </config>

The exported report has the following format:

! <connectors>
!   <connector name="LVDS-11" connected="1">
!     <mode width="1280" height="800" hz="60"/>
!     ...
!   </connector>
!   ...
! </connectors>