History log of /dflybsd-src/sys/dev/drm/drm_edid_load.c (Results 1 – 4 of 4)
Revision Date Author Comments
# a85cb24f 27-Jul-2020 François Tigeot <ftigeot@wolfpond.org>

drm: Update to Linux 4.12.14

* Initial Geminilake support

* Support improvements and model-specific bug fixes for Broxton, Haswell,
Broadwell, Skylake and Kabylake hardware

* Various generic i91

drm: Update to Linux 4.12.14

* Initial Geminilake support

* Support improvements and model-specific bug fixes for Broxton, Haswell,
Broadwell, Skylake and Kabylake hardware

* Various generic i915 bug fixes, including page flipping and memory
corruption issues

* Minor radeon bug fixes

show more ...


# 794ee81f 29-Mar-2016 zrj <rimvydas.jasinskas@gmail.com>

drm: Allow early kms with monitor EDID override.

While firmware_put(fw, FIRMWARE_UNLOAD) works great when
fw can be loaded multiple times through kernel fw module,
this functionality breaks when loa

drm: Allow early kms with monitor EDID override.

While firmware_put(fw, FIRMWARE_UNLOAD) works great when
fw can be loaded multiple times through kernel fw module,
this functionality breaks when loading i915 and radeonkms
together with EDID override module from /boot/loader.conf

Since DRM reads EDID firmware multiple times, it is best
to delay FW_UNLOAD to at least when / is accessable.
Doing that allows to have an early kms with a monitor
reporting bad EDID information at a native resolution.

EDID fw is usually just 128 bytes and still can be unloaded
if it was autoloaded by loader.

Tested-on: early i915 with eDP and broken external LCD panels.

show more ...


# 19c468b4 23-Feb-2016 François Tigeot <ftigeot@wolfpond.org>

drm/i915: Update to Linux 4.2

* Work in progress atomic modesetting support

* Broadwell support improvements

* Skylake support improvements, including runtime power management.
Starting from Lin

drm/i915: Update to Linux 4.2

* Work in progress atomic modesetting support

* Broadwell support improvements

* Skylake support improvements, including runtime power management.
Starting from Linux 4.2, a separate firmware blob is required to save
and restore the state of display engines in some low-power modes. These
low-power modes have been forcibly disabled in the DragonFly version of
this driver in order to keep it blob-free.

* Basic Broxton (BXT) support

* Various Displayport improvements including optimized link training,
increased robustness, and automated support for compliance testing

* Execlist overhead reduced

* Frequency boost tuning

* Plenty of bugfixes all around

show more ...


# 819060d5 20-Nov-2015 zrj <rimvydas.jasinskas@gmail.com>

drm: Implement simple broken EDID override by loading firmware (v16)

Main differences between this variant and its gpl analogue:
* permissive license;
* no builtin generic EDID data blocks;

Gen

drm: Implement simple broken EDID override by loading firmware (v16)

Main differences between this variant and its gpl analogue:
* permissive license;
* no builtin generic EDID data blocks;

Generic EDID firmware can be used from new dports/sysutils/devedid-data port.
Still it is better to use monitor specific EDID block, either by modifying
generic variants or repairing dumped one or even better extracting from
working identical monitor if it is available (look for hex dump in Xorg.0.log).

Make sure that used fw.bin at least has correct resolutions and valid checksum.
This can be done with sysutils/edid-decode utility.

Tested with broken lcd panel returning corrupted EDID block on dvi port:
* radeonkms R7 240, dvi and dvi2hdmi cable adapter
echo 'drm.edid_firmware="DVI-D-1:edidfw_repaired"' >> /boot/loader.conf

* i915 Haswell i7-4712MQ laptop, dvi2hdmi cable adapter
echo 'drm.edid_firmware="HDMI-A-1:edidfw_1920x1080"' >> /boot/loader.conf
echo 'drm.video.hdmia1="e" # force enable on i915' >> /boot/loader.conf

While here, document tunables: drm.video.<connector> and new drm.edid_firmware.

show more ...