[PATCH 0/3] Provide workarounds to use DRM/KMS with broken graphics hardware

In the good old days when graphics parameters were configured explicitly in a file called xorg.conf, even broken hardware could be managed. Today, with the advent of Kernel Mode Setting, a graphics board is either correctly working because all components follow the standards - or the computer is u

[PATCH 3/3] drivers-gpu-drm-i915-invert-backlight-brightness

affected notebook usable again. Signed-off-by: Carsten Emde --- Documentation/kernel-parameters.txt |9 + drivers/gpu/drm/i915/intel_panel.c | 14 ++ 2 files changed, 23 insertions(+) Index: linux-3.3-rc6/Documentation/kernel-parameters.txt

[PATCH 2/3] drivers-gpu-drm-add-disable-enable-connector.patch

put HDMI2 disconnected (II) intel(0): Output DP2 disconnected (II) intel(0): Using exact sizes for initial modes (II) intel(0): Output VGA1 using initial mode 1280x1024 +0+0 Signed-off-by: Carsten Emde --- Documentation/kernel-parameters.txt | 13 drivers/gpu/drm/drm_crtc.c

[PATCH 1/3] drivers-gpu-drm-allow-to-load-edid-firmware.patch

at may not apply to a particular monitor and even crash it. Ideally, EDID data of the connected monitor should be used. They may be obtained through the drm/cardX/cardX-/edid entry in the /sys/devices PCI directory of a correctly working graphics adapter. Signed-off-by: Carsten Emde --- Docu

Re: [PATCH 2/3] drivers-gpu-drm-add-disable-enable-connector.patch

On 03/11/2012 08:20 AM, Dave Airlie wrote: On Sat, Mar 10, 2012 at 8:20 PM, Carsten Emde wrote: Some recent integrated graphics chipset, notably Intel's "Pineview", also provide on-chip LVDS support. As an extra service, the LVDS interface supplies EDID data - irrespective of

Re: [PATCH 1/3] drivers-gpu-drm-allow-to-load-edid-firmware.patch

On 03/11/2012 02:44 PM, Alan Cox wrote: This patch allows to load an EDID data set via the firmware interface. It contains data sets of frequently used screen resolutions (1024x768, 1280x1024, 1680x1050 and 1920x1080). The requested EDID data are specified as a module parameter of the drm_kms_hel

Re: [PATCH 1/3] drivers-gpu-drm-allow-to-load-edid-firmware.patch

Signed-off-by: Carsten Emde --- Documentation/kernel-parameters.txt | 10 + drivers/gpu/drm/Kconfig | 11 + drivers/gpu/drm/Makefile|3 drivers/gpu/drm/drm_crtc_helper.c |8 + drivers/gpu/drm/drm_edid.c |4 drivers/gpu/drm/drm_edid_load.c

[V2 PATCH 0/2] Provide workarounds to use DRM/KMS with broken graphics hardware

This is V2 of a patchset to use DRM/KMS with broken graphics hardware. As a major change from V1, generic EDID data are now built-in into the drm_kms_helper module as proposed by Alan. To help people building their own EDID data and to understand how the binary EDID blobs in drivers/gpu/drm/drm_ed

[V2 PATCH 2/2] drivers-gpu-drm-i915-invert-backlight-brightness

affected notebook usable again. Signed-off-by: Carsten Emde --- Documentation/kernel-parameters.txt |9 + drivers/gpu/drm/i915/intel_panel.c | 14 ++ 2 files changed, 23 insertions(+) Index: linux-3.3-rc6/Documentation/kernel-parameters.txt

[V2 PATCH 1/2] drivers-gpu-drm-allow-to-load-edid-firmware.patch

ady running X server. Signed-off-by: Carsten Emde --- Documentation/EDID/1024x768.S | 44 ++ Documentation/EDID/1280x1024.S | 44 ++ Documentation/EDID/1680x1050.S | 44 ++ Documentation/EDID/1920x1080.S | 44 ++ Documentation/EDID/HOWTO.txt|

[V3 PATCH 2/2] drivers-gpu-drm-i915-quirk-backlight-inverted.patch

BLC_PWM_CTL I915 register. This problem was introduced in kernel version 2.6.38 when the PCI device of this system was first supported by the i915 KMS module. This patch adds a quirk to invert the sense of the brightness variable in case an Acer Aspire 5734Z is encountered. Signed-off-by: Carsten

[V3 PATCH 1/2] drivers-gpu-drm-allow-to-load-edid-firmware.patch

ady running X server. Signed-off-by: Carsten Emde --- Documentation/EDID/1024x768.S | 44 ++ Documentation/EDID/1280x1024.S | 44 ++ Documentation/EDID/1680x1050.S | 44 ++ Documentation/EDID/1920x1080.S | 44 ++ Documentation/EDID/HOWTO.txt|

Re: [V3 PATCH 1/2] drivers-gpu-drm-allow-to-load-edid-firmware.patch

Bastien, Broken monitors and/or broken graphic boards may send erroneous or no EDID data. This also applies to broken KVM devices that are unable to correctly forward the EDID data of the connected monitor but invent their own fantasy data. This patch allows to specify an EDID data set to be us

[V3 PATCH 0/2] Provide workarounds to use DRM/KMS with broken graphics hardware

Changes from V2 to V3: 1. The help text of the DRM_LOAD_EDID_FIRMWARE Kconfig item and the related explanation in Documentation/kernel-parameters.txt now contain a pointer to the documentation as suggested by Paul. 2. Removed the "brightness_inverted" parameter of the i915 module and replaced it b

[V4 PATCH 0/2] Provide workarounds to use DRM/KMS with broken graphics hardware

Changes from V3 to V4: Reverted the removal of the "brightness_inverted" parameter of the i915 module as suggested by Chris. Inversion of the sense of the brightness variable is now enabled, if either the quirked notebook is encountered or the "brightness_inverted" module parameter switch is set.

[V4 PATCH 2/2] drivers-gpu-drm-i915-backlight-brightness-inverted.patch

a parameter of the i915 module to enable inversion of the brightness variable (i915 brightness_inverted). Signed-off-by: Carsten Emde --- Documentation/kernel-parameters.txt |9 + drivers/gpu/drm/i915/i915_drv.h |1 + drivers/gpu/drm/i915/intel_display.c | 12

[V4 PATCH 1/2] drivers-gpu-drm-allow-to-load-edid-firmware.patch

ady running X server. Signed-off-by: Carsten Emde --- Documentation/EDID/1024x768.S | 44 ++ Documentation/EDID/1280x1024.S | 44 ++ Documentation/EDID/1680x1050.S | 44 ++ Documentation/EDID/1920x1080.S | 44 ++ Documentation/EDID/HOWTO.txt|

[V5 PATCH 0/4] Provide workarounds to use DRM/KMS with broken graphics hardware

Changes from V4 to V5: 1. Split the previous patch 2/2 into three patches to separately i) add the module parameter, ii) add the quirk infrastructure, and iii) actually quirk the related machine. 2. Rename the module parameter variable to i915_panel_invert_brightness. 3. Make the module paramete

[V5 PATCH 1/4] drivers-gpu-drm-allow-to-load-edid-firmware.patch

ady running X server. Signed-off-by: Carsten Emde --- Documentation/EDID/1024x768.S | 44 ++ Documentation/EDID/1280x1024.S | 44 ++ Documentation/EDID/1680x1050.S | 44 ++ Documentation/EDID/1920x1080.S | 44 ++ Documentation/EDID/HOWTO.txt|

[V5 PATCH 4/4] drivers-gpu-drm-i915-panel-invert-brightness-acer-aspire-5734z.patch

Mark the Acer Aspire 5734Z that this machines requires the module to invert the panel backlight brightness value after reading from and prior to writing to the PCI configuration space. Signed-off-by: Carsten Emde --- drivers/gpu/drm/i915/intel_display.c |6 +- 1 file changed, 5

[V5 PATCH 3/4] drivers-gpu-drm-i915-panel-invert-brightness-via-quirk.patch

A machine may need to invert the panel backlight brightness value. This patch adds the infrastructure for a quirk to do so. Signed-off-by: Carsten Emde --- Documentation/kernel-parameters.txt | 17 +++-- drivers/gpu/drm/i915/i915_drv.h |1 + drivers/gpu/drm/i915

[V5 PATCH 2/4] drivers-gpu-drm-i915-panel-invert-brightness-via-parameter.patch

BLC_PWM_CTL I915 register. This problem was introduced in kernel version 2.6.38 when the PCI device of this system was first supported by the i915 KMS module. This patch adds a parameter to the i915 module to enable inversion of the brightness variable (i915.invert_brightness). Signed-off-by: Carsten

Re: [V5 PATCH 1/4] drivers-gpu-drm-allow-to-load-edid-firmware.patch

Dear Thomas, your proposal will not lead to a satisfying solution for those people that suffer from monitors and other HW devices that provide wrong EDIDs. Oops, why not? Before fetching the display modes, all drm devices will try to detect the monitor. If EDID data is not correct (checksum),

[V6 PATCH 0/1] Provide workarounds to use DRM/KMS with broken graphics hardware

Changes from V5 to V6: 1. The use of a particular EDID data set can now be restricted to a given connector using the syntax edid_firmware=[:] as suggested by Thomas Reim. 2. The patches to introduce a module parameter and a quirk to cope with an inverted brightness variable of some i915 graphic

[V6 PATCH 1/1] drivers-gpu-drm-allow-to-load-edid-firmware.patch

lay settings dialog is opened in an already running X server. Signed-off-by: Carsten Emde --- Documentation/EDID/1024x768.S | 44 ++ Documentation/EDID/1280x1024.S | 44 ++ Documentation/EDID/1680x1050.S | 44 ++ Documentation/EDID/1920x1080.S |

Re: [PATCH 1/3] drivers-gpu-drm-allow-to-load-edid-firmware.patch

Michael, On Sun, 11 Mar 2012 22:23:22 +0100, Carsten Emde wrote: On 03/11/2012 02:44 PM, Alan Cox wrote: This patch allows to load an EDID data set via the firmware interface. It contains data sets of frequently used screen resolutions (1024x768, 1280x1024, 1680x1050 and 1920x1080). The

[PATCH 0/1] Improve documentation to create an EDID data set

Among the (predominantly positive) feedback to the EDID firmware loader (http://lists.freedesktop.org/archives/dri-devel/2012-March/020292.html), there was a complaint that the documentation could be clearer how to create a particular EDID data set from timing data in X11 format. This patch adds a

[PATCH 1/1] Load EDID: Explain better how to write your own EDID firmware

A description was lacking how to write an EDID firmware file that corresponds to a given X11 setting. Signed-off-by: Carsten Emde --- Documentation/EDID/HOWTO.txt | 27 +++ 1 file changed, 23 insertions(+), 4 deletions(-) Index: linux-3.4.4-rt13/Documentation/EDID

Re: [PATCH] drm/edid: Fix potential memory leak in edid_load()

On 08/07/2012 02:23 PM, Alexey Khoroshilov wrote: Do not leak memory by updating pointer with potentially NULL realloc return value. Found by Linux Driver Verification project (linuxtesting.org). Thanks, Alexey! Reviewed-by: Carsten Emde Signed-off-by: Alexey Khoroshilov --- drivers/gpu

[PATCH 0/1] drm: Add built-in EDID set of another common screen resolution

Several users were complaining that 1600x1200 screen resolution was lacking. Here is it. -Carsten. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel

[PATCH 1/1] drm: Add 1600x1200 (UXGA) screen resolution to the built-in EDIDs

The 1600x1200 (UXGA) screen resolution was lacking in the set of built-in selectable EDID screen resolutions that can be used to repair misbehaving monitor firmware. This patch adds the related data set and expands the documentation. Signed-off-by: Carsten Emde --- Documentation/EDID

[PATCH 0/1] drm-set-default-noedid-res.patch

Hi, Some monitors and, more often, kvm switches do not provide working EDID data. KMS based X configurations in recent server versions no longer allow to override the screen resolution which makes it impossible to correctly adapt the screen resolution to the monitor in use. This patch allows to d

[PATCH 1/1] drm-set-default-noedid-res.patch

A default resolution of 1024x768 is used, if there are no EDID data. However, this may not always be appropriate. This patch introduces the kernel parameter drm.noedidres that has the format "x". If specified, it will override the default. Example: drm.noedidres=1280x1024 Signed-off-b

Re: [PATCH 0/1] drm-set-default-noedid-res.patch

Dave, Some monitors and, more often, kvm switches do not provide working EDID data. KMS based X configurations in recent server versions no longer allow to override the screen resolution which makes it impossible to correctly adapt the screen resolution to the monitor in use. This patch allows t

[RFC] Re: [PATCH 0/1] drm-set-default-noedid-res.patch

e with the observation that EDID related functionality appears to fade out of X drivers. Does this make sense? Carsten. Use the firmware interface to load binary EDID data from a file and use them to assign monitor data to a video connector. Signed-off-by: Carsten Emde --- drivers/gpu/drm/drm_crt

[PATCH 1/3] drivers-gpu-drm-allow-to-load-edid-firmware.patch

Michael, > On Sun, 11 Mar 2012 22:23:22 +0100, Carsten Emde wrote: >> On 03/11/2012 02:44 PM, Alan Cox wrote: >>>> This patch allows to load an EDID data set via the firmware interface. >>>> It contains data sets of frequently used screen resolutions (1024x7

[PATCH] drm/edid: Fix potential memory leak in edid_load()

On 08/07/2012 02:23 PM, Alexey Khoroshilov wrote: > Do not leak memory by updating pointer with potentially > NULL realloc return value. > > Found by Linux Driver Verification project (linuxtesting.org). Thanks, Alexey! Reviewed-by: Carsten Emde > Signed-off-by: Ale

[PATCH 0/1] drm-set-default-noedid-res.patch

Hi, Some monitors and, more often, kvm switches do not provide working EDID data. KMS based X configurations in recent server versions no longer allow to override the screen resolution which makes it impossible to correctly adapt the screen resolution to the monitor in use. This patch allows to d

[PATCH 1/1] drm-set-default-noedid-res.patch

An embedded and charset-unspecified text was scrubbed... Name: drm-set-default-noedid-res.patch URL:

[PATCH 0/1] drm-set-default-noedid-res.patch

Dave, >> Some monitors and, more often, kvm switches do not provide working >> EDID data. KMS based X configurations in recent server versions no >> longer allow to override the screen resolution which makes it >> impossible to correctly adapt the screen resolution to the monitor >> in use. This p

[RFC] Re: [PATCH 0/1] drm-set-default-noedid-res.patch

Dave, >> Some monitors and, more often, kvm switches do not provide working >> EDID data. KMS based X configurations in recent server versions no >> longer allow to override the screen resolution which makes it >> impossible to correctly adapt the screen resolution to the monitor >> in use. This p

[PATCH 0/1] drm: Add built-in EDID set of another common screen resolution

Several users were complaining that 1600x1200 screen resolution was lacking. Here is it. -Carsten.

[PATCH 1/1] drm: Add 1600x1200 (UXGA) screen resolution to the built-in EDIDs

An embedded and charset-unspecified text was scrubbed... Name: drivers-gpu-drm-edid-load-firmware-add-1600x1200.patch URL:

[PATCH 0/1] Improve documentation to create an EDID data set

Among the (predominantly positive) feedback to the EDID firmware loader (http://lists.freedesktop.org/archives/dri-devel/2012-March/020292.html), there was a complaint that the documentation could be clearer how to create a particular EDID data set from timing data in X11 format. This patch adds a

[PATCH 1/1] Load EDID: Explain better how to write your own EDID firmware

An embedded and charset-unspecified text was scrubbed... Name: edid-howto-explain-timing-vars-better.patch URL:

[PATCH 0/3] Provide workarounds to use DRM/KMS with broken graphics hardware

In the good old days when graphics parameters were configured explicitly in a file called xorg.conf, even broken hardware could be managed. Today, with the advent of Kernel Mode Setting, a graphics board is either correctly working because all components follow the standards - or the computer is u

[PATCH 3/3] drivers-gpu-drm-i915-invert-backlight-brightness

An embedded and charset-unspecified text was scrubbed... Name: drivers-gpu-drm-i915-invert-backlight-brightness.patch URL:

[PATCH 2/3] drivers-gpu-drm-add-disable-enable-connector.patch

An embedded and charset-unspecified text was scrubbed... Name: drivers-gpu-drm-add-disable-enable-connector.patch URL:

[PATCH 1/3] drivers-gpu-drm-allow-to-load-edid-firmware.patch

An embedded and charset-unspecified text was scrubbed... Name: drivers-gpu-drm-allow-to-load-edid-firmware.patch URL:

[PATCH 2/3] drivers-gpu-drm-add-disable-enable-connector.patch

On 03/11/2012 08:20 AM, Dave Airlie wrote: > On Sat, Mar 10, 2012 at 8:20 PM, Carsten Emde wrote: >> Some recent integrated graphics chipset, notably Intel's "Pineview", also >> provide on-chip LVDS support. As an extra service, the LVDS interface >> sup

[PATCH 1/3] drivers-gpu-drm-allow-to-load-edid-firmware.patch

On 03/11/2012 02:44 PM, Alan Cox wrote: >> This patch allows to load an EDID data set via the firmware interface. >> It contains data sets of frequently used screen resolutions (1024x768, >> 1280x1024, 1680x1050 and 1920x1080). The requested EDID data are >> specified as a module parameter of the d

[PATCH 1/3] drivers-gpu-drm-allow-to-load-edid-firmware.patch

Alan, >> This patch allows to load an EDID data set via the firmware interface. >> It contains data sets of frequently used screen resolutions (1024x768, >> 1280x1024, 1680x1050 and 1920x1080). The requested EDID data are >> specified as a module parameter of the drm_kms_helper module, e.g. >> opt

[V2 PATCH 0/2] Provide workarounds to use DRM/KMS with broken graphics hardware

This is V2 of a patchset to use DRM/KMS with broken graphics hardware. As a major change from V1, generic EDID data are now built-in into the drm_kms_helper module as proposed by Alan. To help people building their own EDID data and to understand how the binary EDID blobs in drivers/gpu/drm/drm_ed

[V2 PATCH 2/2] drivers-gpu-drm-i915-invert-backlight-brightness

An embedded and charset-unspecified text was scrubbed... Name: drivers-gpu-drm-i915-invert-backlight-brightness.patch URL:

[V2 PATCH 1/2] drivers-gpu-drm-allow-to-load-edid-firmware.patch

An embedded and charset-unspecified text was scrubbed... Name: drivers-gpu-drm-allow-to-load-edid-firmware.patch URL:

[V3 PATCH 2/2] drivers-gpu-drm-i915-quirk-backlight-inverted.patch

An embedded and charset-unspecified text was scrubbed... Name: drivers-gpu-drm-i915-quirk-backlight-inverted.patch URL:

[V3 PATCH 1/2] drivers-gpu-drm-allow-to-load-edid-firmware.patch

An embedded and charset-unspecified text was scrubbed... Name: drivers-gpu-drm-allow-to-load-edid-firmware.patch URL:

[V3 PATCH 1/2] drivers-gpu-drm-allow-to-load-edid-firmware.patch

Bastien, >> Broken monitors and/or broken graphic boards may send erroneous or no >> EDID data. This also applies to broken KVM devices that are unable to >> correctly forward the EDID data of the connected monitor but invent >> their own fantasy data. >> >> This patch allows to specify an EDID da

[V3 PATCH 0/2] Provide workarounds to use DRM/KMS with broken graphics hardware

Changes from V2 to V3: 1. The help text of the DRM_LOAD_EDID_FIRMWARE Kconfig item and the related explanation in Documentation/kernel-parameters.txt now contain a pointer to the documentation as suggested by Paul. 2. Removed the "brightness_inverted" parameter of the i915 module and replaced it b

[V4 PATCH 0/2] Provide workarounds to use DRM/KMS with broken graphics hardware

Changes from V3 to V4: Reverted the removal of the "brightness_inverted" parameter of the i915 module as suggested by Chris. Inversion of the sense of the brightness variable is now enabled, if either the quirked notebook is encountered or the "brightness_inverted" module parameter switch is set.

[V4 PATCH 2/2] drivers-gpu-drm-i915-backlight-brightness-inverted.patch

An embedded and charset-unspecified text was scrubbed... Name: drivers-gpu-drm-i915-backlight-brightness-inverted.patch URL:

[V4 PATCH 1/2] drivers-gpu-drm-allow-to-load-edid-firmware.patch

An embedded and charset-unspecified text was scrubbed... Name: drivers-gpu-drm-allow-to-load-edid-firmware.patch URL:

[V5 PATCH 0/4] Provide workarounds to use DRM/KMS with broken graphics hardware

Changes from V4 to V5: 1. Split the previous patch 2/2 into three patches to separately i) add the module parameter, ii) add the quirk infrastructure, and iii) actually quirk the related machine. 2. Rename the module parameter variable to i915_panel_invert_brightness. 3. Make the module paramete

[V5 PATCH 1/4] drivers-gpu-drm-allow-to-load-edid-firmware.patch

An embedded and charset-unspecified text was scrubbed... Name: drivers-gpu-drm-allow-to-load-edid-firmware.patch URL:

[V5 PATCH 4/4] drivers-gpu-drm-i915-panel-invert-brightness-acer-aspire-5734z.patch

An embedded and charset-unspecified text was scrubbed... Name: drivers-gpu-drm-i915-panel-invert-brightness-acer-aspire-5734z.patch URL:

[V5 PATCH 3/4] drivers-gpu-drm-i915-panel-invert-brightness-via-quirk.patch

An embedded and charset-unspecified text was scrubbed... Name: drivers-gpu-drm-i915-panel-invert-brightness-via-quirk.patch URL:

[V5 PATCH 2/4] drivers-gpu-drm-i915-panel-invert-brightness-via-parameter.patch

An embedded and charset-unspecified text was scrubbed... Name: drivers-gpu-drm-i915-panel-invert-brightness-via-parameter.patch URL:

[V5 PATCH 1/4] drivers-gpu-drm-allow-to-load-edid-firmware.patch

Dear Thomas, > your proposal will not lead to a satisfying solution for those people > that suffer from monitors and other HW devices that provide wrong > EDIDs. Oops, why not? > Before fetching the display modes, all drm devices will try to detect > the monitor. If EDID data is not correct (chec

[V6 PATCH 0/1] Provide workarounds to use DRM/KMS with broken graphics hardware

Changes from V5 to V6: 1. The use of a particular EDID data set can now be restricted to a given connector using the syntax edid_firmware=[:] as suggested by Thomas Reim. 2. The patches to introduce a module parameter and a quirk to cope with an inverted brightness variable of some i915 graphic

[V6 PATCH 1/1] drivers-gpu-drm-allow-to-load-edid-firmware.patch

An embedded and charset-unspecified text was scrubbed... Name: drivers-gpu-drm-allow-to-load-edid-firmware.patch URL:

[OSADL QA 3.18.9-rt4 #1] Radeon driver hangs

(About 30 OSADL QA Farm systems are now running 3.18.9-rt4. BTW: To check out what kernels are under test you may sort the kernel list (https://www.osadl.org/?id=933) by kernel version (https://www.osadl.org/?id=1001) and scroll down the page.) The most striking problem of kernel 3.18.9-rt4 aff

[OSADL QA 3.18.9-rt4 #1] Radeon driver hangs

Hi Michel, >> [..] >> The most striking problem of kernel 3.18.9-rt4 affects all systems that >> are equipped with Radeon graphics (irrespective whether PCIe cards or >> APUs with on-chip graphics). They suffer from a hanging radeon driver. >> The block occurs when accelerated graphics load is cre

[OSADL QA 3.18.9-rt4 #1] Radeon driver hangs

Hi Michel, [..] The most striking problem of kernel 3.18.9-rt4 affects all systems that are equipped with Radeon graphics (irrespective whether PCIe cards or APUs with on-chip graphics). They suffer from a hanging radeon driver. The block occurs when accelerated graphics l