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-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1263502711.16937.5.camel@pcjc2lap>
Date:	Thu, 14 Jan 2010 20:58:31 +0000
From:	Peter Clifton <pcjc2@....ac.uk>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	Nick Bowler <nbowler@...iptictech.com>, airlied@...ux.ie,
	intel-gfx@...ts.freedesktop.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Pekka Enberg <penberg@...helsinki.fi>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: disable LVDS downclock by default

On Thu, 2010-01-14 at 12:48 -0800, Jesse Barnes wrote:
> Many platform support this feature, and it can provide significant
> power savings when the reduced refresh rate is low.  However, on some
> platforms a secondary (reduced) timing is provided but not actually
> supported by the hardware.  This results in undesirable flicker at
> runtime.
> 
> So disable the feature by default, but allow users to opt-in to the
> reduced clock behavior with a new module parameter, lvds_downclock,
> that can be set to 1 to enable the feature.

Would it not be a better idea to turn this feature on by default, then
use quirks to disable it on the afflicted borken machines?

Requiring special module parameters to enable the feature, almost
guarantees that no normal end-users will end up benefiting from the
feature. Many of whom will have bought machines which don't have screwey
BIOS implementations.

I think (on a general note) that vendors supplying defective BIOSen or
config should be "named and shamed" in quirk tables - so eventually they
will get something done about the problems for future models.



--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ