From: Mark Hounschell <dmarkh@cfl.rr.com>
To: "Bruno Prémont" <bonbons@linux-vserver.org>
Cc: markh@compro.net, linux-kernel@vger.kernel.org,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: Intel graphics drm issue?
Date: Sun, 14 Oct 2012 06:52:45 -0400 [thread overview]
Message-ID: <507A997D.7070508@cfl.rr.com> (raw)
In-Reply-To: <20121014104138.7e8a9c59@neptune.home>
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
next prev parent reply other threads:[~2012-10-14 10:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 12:54 Intel graphics drm issue? Mark Hounschell
2012-10-12 21:14 ` Bruno Prémont
2012-10-13 18:57 ` Mark Hounschell
2012-10-13 19:17 ` Mark Hounschell
2012-10-14 8:41 ` Bruno Prémont
2012-10-14 8:41 ` Bruno Prémont
2012-10-14 10:34 ` Mark Hounschell
2012-10-14 10:52 ` Mark Hounschell [this message]
2012-10-14 11:03 ` Bruno Prémont
2012-10-14 11:03 ` Bruno Prémont
2012-10-14 16:54 ` Mark Hounschell
2012-10-14 17:22 ` Bruno Prémont
2012-10-14 18:03 ` Mark Hounschell
2012-10-14 18:19 ` Bruno Prémont
2012-10-14 18:19 ` Bruno Prémont
2012-10-14 18:57 ` Mark Hounschell
2012-10-14 20:40 ` Bruno Prémont
2012-10-14 20:40 ` Bruno Prémont
2012-10-15 9:58 ` Mark Hounschell
2012-10-14 8:58 ` Daniel Vetter
2012-10-14 8:58 ` [Intel-gfx] " Daniel Vetter
2012-10-14 10:20 ` Mark Hounschell
2012-10-14 11:26 ` Daniel Vetter
2012-10-14 11:26 ` [Intel-gfx] " Daniel Vetter
2012-10-14 11:39 ` Mark Hounschell
2012-10-14 14:19 ` Mark Hounschell
2012-10-14 14:40 ` Daniel Vetter
2012-10-14 15:41 ` Mark Hounschell
2012-10-14 15:53 ` Daniel Vetter
2012-10-14 15:55 ` Bruno Prémont
2012-10-14 16:09 ` Mark Hounschell
2012-10-14 16:13 ` Mark Hounschell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=507A997D.7070508@cfl.rr.com \
--to=dmarkh@cfl.rr.com \
--cc=bonbons@linux-vserver.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@compro.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.