From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bruno =?UTF-8?B?UHLDqW1vbnQ=?= <bonbons@linux-vserver.org>
Subject: Re: Intel graphics drm issue?
Date: Sun, 14 Oct 2012 20:19:41 +0200
Message-ID: <20121014201941.22284249@neptune.home>
References: <507812E8.3060607@compro.net>
	<20121012231459.166e29fd@neptune.home>
	<5079B97C.7020401@cfl.rr.com> <5079BE5C.8020401@cfl.rr.com>
	<20121014104138.7e8a9c59@neptune.home>
	<507A997D.7070508@cfl.rr.com>
	<20121014130323.06f0225d@neptune.home>
	<507AEE4A.1000907@cfl.rr.com>
	<20121014192253.5a7517ef@neptune.home> <507AFE69.70405@cfl.rr.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org>
Received: from smtprelay.restena.lu (smtprelay.restena.lu [158.64.1.62])
	by gabe.freedesktop.org (Postfix) with ESMTP id B66769E753
	for <intel-gfx@lists.freedesktop.org>;
	Sun, 14 Oct 2012 11:20:41 -0700 (PDT)
In-Reply-To: <507AFE69.70405@cfl.rr.com>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/intel-gfx>,
	<mailto:intel-gfx-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/intel-gfx>
List-Post: <mailto:intel-gfx@lists.freedesktop.org>
List-Help: <mailto:intel-gfx-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/intel-gfx>,
	<mailto:intel-gfx-request@lists.freedesktop.org?subject=subscribe>
Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org
Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org
To: dmarkh@cfl.rr.com
Cc: markh@compro.net, Intel Graphics Development <intel-gfx@lists.freedesktop.org>, linux-kernel@vger.kernel.org
List-Id: intel-gfx@lists.freedesktop.org

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