Re: [U-Boot] [PATCH 2/2] pdm360ng: add EDID property to FDT display node

Dear Anatolij Gustschin,

In message 1281963128-13777-2-git-send-email-agust@denx.de you wrote:

PDM360NG board uses this functionality to pass display timing info to the Linux Framebuffer driver.

thanks for these patches.

I have one (probably stupid) question:

+static unsigned char edid_buf[128] = {

• 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00,
• 0x42, 0xC9, 0x34, 0x12, 0x01, 0x00, 0x00, 0x00,
• 0x0A, 0x0C, 0x01, 0x03, 0x80, 0x98, 0x5B, 0x78,
• 0xCA, 0x7E, 0x50, 0xA0, 0x58, 0x4E, 0x96, 0x25,
• 0x1E, 0x50, 0x54, 0x00, 0x00, 0x00, 0x01, 0x01,
• 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01,
• 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x80, 0x0C,
• 0x20, 0x00, 0x31, 0xE0, 0x2D, 0x10, 0x2A, 0x80,
• 0x12, 0x08, 0x30, 0xE4, 0x10, 0x00, 0x00, 0x18,
• 0x00, 0x00, 0x00, 0xFD, 0x00, 0x38, 0x3C, 0x1F,
• 0x3C, 0x04, 0x0A, 0x20, 0x20, 0x20, 0x20, 0x20,
• 0x20, 0x20, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x50,
• 0x4D, 0x30, 0x37, 0x30, 0x57, 0x4C, 0x33, 0x0A,
• 0x0A, 0x0A, 0x0A, 0x0A, 0x00, 0x00, 0x00, 0xFF,
• 0x00, 0x41, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30,
• 0x30, 0x30, 0x30, 0x30, 0x30, 0x31, 0x00, 0xD4,

+};

Is there a way to make these magic numbers readbale for a mere human?

How do you generate these?

Best regards,

Wolfgang Denk