Bug 61783 - Test I2C read fail
Summary: Test I2C read fail
Status: CLOSED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
: 61659 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-03-04 08:29 UTC by Yin Peng
Modified: 2017-07-24 22:58 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Linux can only read 2 block EDID (34.49 KB, image/png)
2013-03-04 08:29 UTC, Yin Peng
no flags Details
Windows side can read 2 and 4 block EDID both. (37.95 KB, image/png)
2013-03-04 08:30 UTC, Yin Peng
no flags Details

Description Yin Peng 2013-03-04 08:29:29 UTC
Created attachment 75885 [details]
Linux can only read 2 block EDID

we are doing the HDMI Logo Requirement.

We find one issue on EE test I2C read.
Please refer to attached file. 
                                                                                 
Linux can only read 2 block EDID, failed on 4 block EDID. Windows side can read 2 and 4 block EDID both.

I think it caused by GFX Driver.
Comment 1 Yin Peng 2013-03-04 08:30:56 UTC
Created attachment 75886 [details]
Windows side can read 2 and 4 block EDID both.
Comment 2 Jani Nikula 2013-03-04 09:36:38 UTC
*** Bug 61659 has been marked as a duplicate of this bug. ***
Comment 3 Chris Wilson 2013-03-04 09:40:30 UTC
The EDID parser is not treating that EDID as conformant. Did you notice any warning in dmesg?
Comment 4 Daniel Vetter 2013-03-04 10:17:47 UTC
Note that support for reading 4 block edids is only implemented since

commit cd004b3f4cd4169815c82bf9e424fda06978898a
Author: Shirish S <s.shirish@samsung.com>
Date:   Thu Aug 30 07:04:06 2012 +0000

    drm: edid: add support for E-DDC

Which is merged into kernel 3.7. Have you tested with that?

Also please boot the linux machine with drm.debug=0xe added to your kernel commandline and attach the complete dmesg output when trying to read a 4 block edid.
Comment 5 Chris Wilson 2013-03-07 15:09:16 UTC
Non-conformant EDID:

cantiga:~/git/edid-decode (master)$ ./edid-decode 
00 ff ff ff ff ff ff 00 4d 29 48 44 01 00 00 00 0a 0d 01 03 80 50 2d 78 0a
0d c9 a0 57 47 98 27 12 48 4c 20 00 00 01 01 01 01 01 01 01 01 01 01 01 01
01 01 01 01 01 1d 80 18 71 1c 16 20 58 2c 25 00 20 c2 31 00 00 9e 8c 0a d0      8a 20 e0 2d 10 10 3e 96 00 13 8e 21 00 00 18 00 00 00 fc 00 48 44 4d 49 20
54 56 0a 20 20 20 20 20 00 00 00 fd 00 3B 3d 0f 2e 08 02 00 20 20 20 20 20
20 03 f1
Extracted contents:
header:          00 ff ff ff ff ff ff 00
serial number:   4d 29 48 44 01 00 00 00 0a 0d
version:         01 03
basic params:    80 50 2d 78 0a
chroma info:     0d c9 a0 57 47 98 27 12 48 4c
established:     20 00 00
standard:        01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
descriptor 1:    01 1d 80 18 71 1c 16 20 58 2c 25 00 20 c2 31 00 00 9e
descriptor 2:    8c 0a d0 8a 20 e0 2d 10 10 3e 96 00 13 8e 21 00 00 18
descriptor 3:    00 00 00 fc 00 48 44 4d 49 20 54 56 0a 20 20 20 20 20
descriptor 4:    00 00 00 fd 00 3b 3d 0f 2e 08 02 00 20 20 20 20 20 20
extensions:      03
checksum:        f1

Manufacturer: SII Model 4448 Serial Number 1
EDID version: 1.3
Digital display
Maximum image size: 80 cm x 45 cm
Gamma: 2.20
Supported color formats: RGB 4:4:4, YCrCb 4:2:2
First detailed timing is preferred timing
Established timings supported:
  640x480@60Hz
Standard timings supported:
Detailed mode: Clock 74.250 MHz, 800 mm x 450 mm
               1920 2008 2052 2200 hborder 0
                540  542  547  562 vborder 0
               +hsync +vsync interlaced
Detailed mode: Clock 27.000 MHz, 531 mm x 398 mm
                720  736  798  858 hborder 0
                480  489  495  525 vborder 0
               -hsync -vsync
Monitor name: HDMI TV
      Monitor ranges: 59-61Hz vertical, 15-46kHz horizontal, max dotclock 80MHz
Has 3 extension blocks
Checksum: 0xf1 (valid)
EDID block does not conform at all!
	Bad year of manufacture


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.