From: Carsten Emde <C.Emde@osadl.org>
To: David Airlie <airlied@linux.ie>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Valdis Kletnieks <Valdis.Kletnieks@vt.edu>,
Thomas Gleixner <tglx@linutronix.de>,
Carsten Emde <C.Emde@osadl.org>,
DRI <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [V2 PATCH 0/2] Provide workarounds to use DRM/KMS with broken graphics hardware
Date: Thu, 15 Mar 2012 00:35:44 +0100 [thread overview]
Message-ID: <20120314233544.629616190@osadl.org> (raw)
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_edid_load.c have been created, the entire material
went into the Documentation tree as suggested by Valdis. Finally, David
showed a much better way to explicitly disable and enable a particular
connector, so patch 02/03 could go.
The two remaining patches
- introduce a mechanism to define or load EDID data instead of letting the
controller probe for it,
- add a parameter to the i915 module to invert the sense of the backlight
brightness variable for broken controllers that require this.
-Carsten.
next reply other threads:[~2012-03-14 23:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 23:35 Carsten Emde [this message]
2012-03-14 23:35 ` [V2 PATCH 1/2] drivers-gpu-drm-allow-to-load-edid-firmware.patch Carsten Emde
2012-03-15 7:13 ` Paul Menzel
2012-03-15 10:08 ` Thomas Gleixner
2012-03-18 10:54 ` Using quilt to send patches (was: [V2 PATCH 1/2] drivers-gpu-drm-allow-to-load-edid-firmware.patch) Paul Menzel
2012-03-18 10:56 ` Paul Menzel
2012-03-14 23:35 ` [V2 PATCH 2/2] drivers-gpu-drm-i915-invert-backlight-brightness Carsten Emde
2012-03-15 2:42 ` Keith Packard
2012-03-15 7:16 ` Paul Menzel
2012-03-15 7:24 ` Paul Menzel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120314233544.629616190@osadl.org \
--to=c.emde@osadl.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=airlied@linux.ie \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox