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]

Date:	Sun, 14 Oct 2012 19:22:53 +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?

Hi Mark,

On Sun, 14 October 2012 Mark Hounschell <dmarkh@....rr.com> wrote:
> I've taken the EDID data from that service manual. I've looked at the 
> EDID-Howto for how to specify the connector but all I see is:
> 
> "An EDID data set will only be used for a particular connector,
>   if its name and a colon are prepended to the EDID name."
> 
> Where can I find the connector names?

Those are the ones you see under /sys/class/drm/, without the card0-
prefix.

E.g. on my system I have:

# ls /sys/class/drm/
card0  card0-DVI-I-1  card0-LVDS-1  card0-VGA-1  controlD64  version

Thus I have connectors "DVI-I-1", "LVDS-1" and "VGA-1" (note that your
HDMI connector might not be named HDMI-1, if you are not sure which one
it is, you can look at the files below (edid, enabled, status) which
should help your find the right connector).


In addition, if you rmmod i915 and modprobe it again connectors will get
increased suffix numbers. So don't expect them to remain the same if you
have multiple GPUs detected in random order or if you rebind them to
their driver. (though except during testing or for special systems you
don't have to worry about this)

> 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.
If it's broken kernel will tell you that checksum does not match.

In any case the (successful) loading of edid should be visible in kernel
log.


Bruno


> int32_t main(int argc, char **argv)
> {
>          FILE *fd;
>          const char *path = "/lib/firmware/edid/lg42lb9df.edid";
>          const char *mode = "w+";
>          uint8_t firmware[1024] = {
> 
>                  0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, 0x1E, 
> 0x6D, 0x01, 0x00, 0x01, 0x01, 0x01, 0x01,
>                  0x0E, 0x10, 0x01, 0x03, 0x80, 0x73, 0x41, 0x96, 0x0A, 
> 0xCF, 0x74, 0xA3, 0x57, 0x4C, 0xB0, 0x23,
>                  0x09, 0x48, 0x4C, 0xAF, 0xCF, 0x00, 0x31, 0x40, 0x45, 
> 0x40, 0x61, 0x40, 0x81, 0x80, 0xA9, 0x40,
>                  0xD1, 0xC0, 0x01, 0x01, 0x01, 0x01, 0x02, 0x3A, 0x80, 
> 0x18, 0x71, 0x38, 0x2D, 0x40, 0x58, 0x2C,
>                  0x45, 0x00, 0xC4, 0x8E, 0x21, 0x00, 0x00, 0x1E, 0x66, 
> 0x21, 0x50, 0xB0, 0x51, 0x00, 0x1B, 0x30,
>                  0x40, 0x70, 0x36, 0x00, 0xC4, 0x8E, 0x21, 0x00, 0x00, 
> 0x1E, 0x00, 0x00, 0x00, 0xFD, 0x00, 0x38,
>                  0x4B, 0x1F, 0x44, 0x0F, 0x00, 0x0A, 0x20, 0x20, 0x20, 
> 0x20, 0x20, 0x20, 0x00, 0x00, 0x00, 0xFC,
>                  0x00, 0x4C, 0x47, 0x20, 0x54, 0x56, 0x0A, 0x20, 0x20, 
> 0x20, 0x20, 0x20, 0x20, 0x20, 0x01, 0x15,
> 
>                  0x02, 0x03, 0x1B, 0xF1, 0x4C, 0x20, 0x22, 0x10, 0x1F, 
> 0x01, 0x02, 0x03, 0x04, 0x05, 0x12, 0x93,
>                  0x14, 0x23, 0x15, 0x07, 0x50, 0x65, 0x03, 0x0C, 0x00, 
> 0x10, 0x00, 0x01, 0x1D, 0x00, 0x72, 0x51,
>                  0xD0, 0x1E, 0x20, 0x6E, 0x28, 0x55, 0x00, 0xC4, 0x8E, 
> 0x21, 0x00, 0x00, 0x1E, 0x01, 0x1D, 0x80,
>                  0x18, 0x71, 0x1C, 0x16, 0x20, 0x58, 0x2C, 0x25, 0x00, 
> 0xC4, 0x8E, 0x21, 0x00, 0x00, 0x9E, 0x8C,
>                  0x0A, 0xD0, 0x90, 0x20, 0x40, 0x31, 0x20, 0x0C, 0x40, 
> 0x55, 0x00, 0x4C, 0x6C, 0x42, 0x00, 0x00,
>                  0x18, 0x01, 0x1D, 0x00, 0xBC, 0x52, 0xD0, 0x1E, 0x20, 
> 0xB8, 0x28, 0x55, 0x40, 0x4C, 0x6C, 0x42,
>                  0x00, 0x00, 0x1E, 0x01, 0x1D, 0x80, 0xD0, 0x72, 0x1C, 
> 0x16, 0x20, 0x10, 0x2C, 0x25, 0x80, 0x4C,
>                  0x6C, 0x42, 0x00, 0x00, 0x9E, 0x00, 0x00, 0x00, 0x00, 
> 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xED
>          };
> 
>          fd = fopen(path, mode);
>          if (fd == NULL) {
>                  perror("/lib/firmware/edid/lg42lb9df.edid failed: ");
>                  return 1;
>          }
> 
>          fwrite(&firmware, 1024, 1, fd);
> 
>          fclose(fd);
> 
>          printf("Wrote 1024 bytes of edid data to %s\n", path);
> 
>          return 0;
> }
> 
> Thanks very much
> 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/