Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Masters <jonathan@jonmasters.org>
To: James Courtier-Dutton <james.dutton@gmail.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [bisected] offset display bug in i915
Date: Mon, 08 Nov 2010 06:38:55 -0500	[thread overview]
Message-ID: <1289216335.3916.407.camel@constitution.bos.jonmasters.org> (raw)
In-Reply-To: <AANLkTinOeu28+uJ=4KwKtn5CPZJyo=VuyhvuNUOgbe+L@mail.gmail.com>

On Mon, 2010-11-08 at 11:33 +0000, James Courtier-Dutton wrote:
> On 8 November 2010 10:54, Jon Masters <jonathan@jonmasters.org> wrote:
> >
> > Here is the EDID output after booting:
> >
> > [jcm@monticello ~]$ hexdump /sys/class/drm/card0-LVDS-1/edid
> > 0000000 ff00 ffff ffff 00ff 6422 03e9 8544 0001
> > 0000010 141c 0301 1680 780d 860a 9426 5157 2790
> > 0000020 4f21 0054 0000 0101 0101 0101 0101 0101
> > 0000030 0101 0101 0101 1194 b000 5840 2019 2335
> > 0000040 0045 81dc 0000 1900 1416 d800 5840 2026
> > 0000050 235d 0415 81dc 0000 0000 0000 fe00 0000
> > 0000060 0000 0000 0000 0000 0000 0000 0000 fe00
> > 0000070 0000 0000 0000 0000 0100 0000 0000 f200
> > 0000080
> >
> hexdump -C  is a little easier to read and compare with other hexdumps.

Yea, but I already ran edid-decode for Chris.

Chris: I suggest your idea of hacking up edid-decode to also take
hexdumps is a good idea for the future. That way you can feed it the
output from xrandr, or from people who like me don't realize that it's
preferred to post the interpreted output.

Jon.

  reply	other threads:[~2010-11-08 11:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-08 10:18 [bisected] offset display bug in i915 Jon Masters
2010-11-08 10:20 ` Jon Masters
2010-11-08 10:27 ` Chris Wilson
2010-11-08 10:54   ` Jon Masters
2010-11-08 11:22     ` Jon Masters
2010-11-08 11:29       ` Jon Masters
2010-11-08 11:36         ` Jon Masters
2010-11-08 12:13         ` Chris Wilson
2010-11-08 17:58           ` Jon Masters
2010-11-08 23:08           ` Jon Masters
2010-11-08 23:23             ` [OT] avoid preformatting in Evolution (was: [bisected] offset display bug in i915) Paul Menzel
2010-11-08 11:33     ` [bisected] offset display bug in i915 James Courtier-Dutton
2010-11-08 11:38       ` Jon Masters [this message]
2010-11-08 11:26   ` James Courtier-Dutton
2010-11-08 11:34     ` Jon Masters

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=1289216335.3916.407.camel@constitution.bos.jonmasters.org \
    --to=jonathan@jonmasters.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=james.dutton@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox