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
| ||
|
Date: Wed, 25 Jan 2012 08:16:24 -0800 From: Keith Packard <keithp@...thp.com> To: intel-gfx@...ts.freedesktop.org Cc: linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org, Keith Packard <keithp@...thp.com> Subject: [PATCH 0/2] drm/i915: Use correct bpc computations for DisplayPort Here's a couple of patches that fix some bpc (bits per component) computation issues with DisplayPort. The problem was that the DisplayPort code tried to figure out the 'current' bpc by looking at the bpp stored in an associated crtc, but that was never right (as described in the message for the first patch). The first patch assumes that the display will run at 8bpc (24bpp) if the link has enough bandwidth, otherwise at 6bpc (18bpp). This is essentially what the existing code ends up doing at boot time; modes are computed before any crtc is assigned, so intel_dp_link_required would have used 24bpp for bandwidth computations. The second patch allows for arbitrary bpc values, computing the display bpc in both intel_dp_mode_fixup and the two crtc_mode_set functions. Obviously doing the computation once would be nice, but there isn't an obvious place to stick the result between those two functions as the bpc computation is also needed for non-DP encoders. This should fix problems where display port doesn't come back after resume for panels which need 6bpc modes. -- keith.packard@...el.com -- 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