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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 15 Mar 2012 15:56:23 +0100
From:	Carsten Emde <C.Emde@...dl.org>
To:	David Airlie <airlied@...ux.ie>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Valdis Kletnieks <Valdis.Kletnieks@...edu>,
	Thomas Gleixner <tglx@...utronix.de>,
	Keith Packard <keithp@...thp.com>,
	Paul Menzel <paulepanter@...rs.sourceforge.net>,
	Chris Wilson <chris@...is-wilson.co.uk>,
	Carsten Emde <C.Emde@...dl.org>,
	DRI <dri-devel@...ts.freedesktop.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: [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 parameter variable tristate to either ignore the
quirk, consider the quirk, if any, or force inversion.

4. Print an instruction along the description of the module parameter to
encourage people sending machine data, should another machine be found
that needs to be quirked.

5. Introduce the function intel_panel_compute_brightness where the
brightness calculation is handled.

Thanks, Chris, for these very valuable suggestions.

	-Carsten.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/