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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 14 Oct 2012 06:52:45 -0400
From:	Mark Hounschell <dmarkh@....rr.com>
To:	Bruno Prémont <bonbons@...ux-vserver.org>
CC:	markh@...pro.net, linux-kernel@...r.kernel.org,
	Intel Graphics Development <intel-gfx@...ts.freedesktop.org>
Subject: Re: Intel graphics drm issue?

On 10/14/2012 04:41 AM, Bruno Prémont wrote:

>
> Your best solution is probably to write an EDID blob (or reuse one you find
> somewhere) that provides at least one mode matching your TV's native mode
> (probably full-HD).
>
> Google suggested the following document:
> http://www.jordansmanuals.com/ServiceManuals%5CLG%5CTV%5CLCD%5C42LB9DF%5C42LB9DF%20Service%20Manual.pdf
> which on page 13/14 shows the full EDID blob for the various HDMI outputs of the
> TV. You may want to read that document, convert the EDID blobs to 512 bytes binary
> files and hell DRM core to use the right one via module/kernel cmdline option:
>
>   drm_kms_helper.edid_firmware=edid/lg42lb9df.edid
> or
>   modprobe drm-kms-helper edid_firmware=edid/lg42lb9df.edid
>
> where
>   /lib/firmware/edid/lg42lb9df.edid
> is the 512-bytes EDID blob created according to data from above manual.
> (note, that will only work for intel, radeon and nouveau drivers but will
>   not work for closed drivers of AMD/nVidia)
>

This certainly looks doable. That firmware file, should it contain all 4 
tables or just the one for the port I'm connected to? Will it matter what 
order they were in?

Thanks
Mark

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