From: "Bruno Prémont" <bonbons@linux-vserver.org>
To: dmarkh@cfl.rr.com
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 20:19:41 +0200 [thread overview]
Message-ID: <20121014201941.22284249@neptune.home> (raw)
In-Reply-To: <507AFE69.70405@cfl.rr.com>
On Sun, 14 October 2012 Mark Hounschell <dmarkh@cfl.rr.com> wrote:
> >> And could I ask if this simple pgm might work to build the file I need?
> >
> > It looks fine. You can also check the output with hexdump just to
> > make sure it looks sane.
>
> Did that and the data looks swapped compared to the array written, but I
> guess that's normal?
That might very well be presentation issue, how did you call hexdump?
When called with no arguments but filename it groups bytes as words and
those look swapped (on little-endian), but `hexdump -C $file` is fine,
dumping each byte individually.
> > If it's broken kernel will tell you that checksum does not match.
> >
>
> So the check sum is actually already in the data provided by the service
> manual then.
Yes, checksum byte is part of the EDID blob.
Bruno
> > In any case the (successful) loading of edid should be visible in kernel
> > log.
> >
>
> I'll be trying this a little later in the day.
>
> Thanks again
> Mark
next prev parent reply other threads:[~2012-10-14 18:20 UTC|newest]
Thread overview: 26+ 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 10:34 ` Mark Hounschell
2012-10-14 10:52 ` Mark Hounschell
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 [this message]
2012-10-14 18:57 ` Mark Hounschell
2012-10-14 20:40 ` Bruno Prémont
2012-10-15 9:58 ` Mark Hounschell
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: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=20121014201941.22284249@neptune.home \
--to=bonbons@linux-vserver.org \
--cc=dmarkh@cfl.rr.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox