From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Hounschell Subject: Re: Intel graphics drm issue? Date: Sun, 14 Oct 2012 06:52:45 -0400 Message-ID: <507A997D.7070508@cfl.rr.com> References: <507812E8.3060607@compro.net> <20121012231459.166e29fd@neptune.home> <5079B97C.7020401@cfl.rr.com> <5079BE5C.8020401@cfl.rr.com> <20121014104138.7e8a9c59@neptune.home> Reply-To: dmarkh@cfl.rr.com Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <20121014104138.7e8a9c59@neptune.home> Sender: linux-kernel-owner@vger.kernel.org To: =?UTF-8?B?QnJ1bm8gUHLDqW1vbnQ=?= Cc: markh@compro.net, linux-kernel@vger.kernel.org, Intel Graphics Development List-Id: intel-gfx@lists.freedesktop.org On 10/14/2012 04:41 AM, Bruno Pr=C3=A9mont wrote: > > Your best solution is probably to write an EDID blob (or reuse one yo= u 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%5C42LB9D= =46%5C42LB9DF%20Service%20Manual.pdf > which on page 13/14 shows the full EDID blob for the various HDMI out= puts 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 cmdlin= e option: > > drm_kms_helper.edid_firmware=3Dedid/lg42lb9df.edid > or > modprobe drm-kms-helper edid_firmware=3Dedid/lg42lb9df.edid > > where > /lib/firmware/edid/lg42lb9df.edid > is the 512-bytes EDID blob created according to data from above manua= l. > (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=20 tables or just the one for the port I'm connected to? Will it matter wh= at=20 order they were in? Thanks Mark