linux-kernel - Re: Intel graphics drm issue?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20121014201941.22284249@neptune.home>
Date:	Sun, 14 Oct 2012 20:19:41 +0200
From:	Bruno Prémont <bonbons@...ux-vserver.org>
To:	dmarkh@....rr.com
Cc:	markh@...pro.net, linux-kernel@...r.kernel.org,
	Intel Graphics Development <intel-gfx@...ts.freedesktop.org>
Subject: Re: Intel graphics drm issue?

On Sun, 14 October 2012 Mark Hounschell <dmarkh@....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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/