{"action":"created","issue":{"url":"https://api.github.com/repos/raspberrypi/firmware/issues/776","repository_url":"https://api.github.com/repos/raspberrypi/firmware","labels_url":"https://api.github.com/repos/raspberrypi/firmware/issues/776/labels{/name}","comments_url":"https://api.github.com/repos/raspberrypi/firmware/issues/776/comments","events_url":"https://api.github.com/repos/raspberrypi/firmware/issues/776/events","html_url":"https://github.com/raspberrypi/firmware/issues/776","id":216259658,"number":776,"title":"EDID can be read for RPi3B, but not CM3L+CMIO3","user":{"login":"JinShil","id":6023641,"avatar_url":"https://avatars2.githubusercontent.com/u/6023641?v=3","gravatar_id":"","url":"https://api.github.com/users/JinShil","html_url":"https://github.com/JinShil","followers_url":"https://api.github.com/users/JinShil/followers","following_url":"https://api.github.com/users/JinShil/following{/other_user}","gists_url":"https://api.github.com/users/JinShil/gists{/gist_id}","starred_url":"https://api.github.com/users/JinShil/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JinShil/subscriptions","organizations_url":"https://api.github.com/users/JinShil/orgs","repos_url":"https://api.github.com/users/JinShil/repos","events_url":"https://api.github.com/users/JinShil/events{/privacy}","received_events_url":"https://api.github.com/users/JinShil/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2017-03-23T01:28:15Z","updated_at":"2017-03-25T23:41:33Z","closed_at":null,"body":"If using a RPi3B with an HDMI display and the `vc4-kms-v3d` overlay, we can read the EDID of our display with either `xrand --props` or `xxd /sys/devices/platform/soc/soc:gpu/drm/card0/card0-HDMI-A-1/edid` as illustrated below:\r\n\r\n```\r\npi@raspberrypi:~ $ xrandr --props\r\nScreen 0: minimum 320 x 200, current 800 x 480, maximum 2048 x 2048\r\nHDMI-0 connected 800x480+0+0 (normal left inverted right x axis y axis) 108mm x 68mm\r\n        EDID:\r\n                00ffffffffffff000481040001000000\r\n                01110103800f0a000a00000000000000\r\n                00000000000001010101010101010101\r\n                010101010101800c208030e02d102830\r\n                d3006c44000000180000001000000000\r\n                00000000000000000000000000100000\r\n                00000000000000000000000000000010\r\n                00000000000000000000000000000017\r\n   800x480       65.68*+\r\n```\r\n\r\n```\r\npi@raspberrypi:~ $ xxd /sys/devices/platform/soc/soc:gpu/drm/card0/card0-HDMI-A-1/edid\r\n0000000: 00ff ffff ffff ff00 0481 0400 0100 0000  ................\r\n0000010: 0111 0103 800f 0a00 0a00 0000 0000 0000  ................\r\n0000020: 0000 0000 0000 0101 0101 0101 0101 0101  ................\r\n0000030: 0101 0101 0101 800c 2080 30e0 2d10 2830  ........ .0.-.(0\r\n0000040: d300 6c44 0000 0018 0000 0010 0000 0000  ..lD............\r\n0000050: 0000 0000 0000 0000 0000 0000 0010 0000  ................\r\n0000060: 0000 0000 0000 0000 0000 0000 0000 0010  ................\r\n0000070: 0000 0000 0000 0000 0000 0000 0000 0017  ................\r\n```\r\n\r\nHowever, if we use the same LCD and configuration (`vc4-kms-v3d` overlay)  with the CM3L+CMIO, the EDID cannot be read (e.g. `/sys/devices/platform/soc/soc:gpu/drm/card0/card0-HDMI-A-1/edid` exists, but returns nothing), and our LCD will not show anything.  If we VNC to the device, we can see the desktop, but it is the wrong resolution, and the mouse and keyboard input are really slow and laggy.  I'm assuming this is because the CM3L firmware is not properly reading the EDID from the display.  \r\n\r\nWe have not made any changes to the device tree.\r\n\r\n* Is this difference between the RPi3 and CM3L by design?  \r\n* If it is by design, is there any configuration or boot parameters we can use to workaround the problem?  \r\n* If it is not by design, can we expect an upcoming fix?\r\n"},"comment":{"url":"https://api.github.com/repos/raspberrypi/firmware/issues/comments/289247353","html_url":"https://github.com/raspberrypi/firmware/issues/776#issuecomment-289247353","issue_url":"https://api.github.com/repos/raspberrypi/firmware/issues/776","id":289247353,"user":{"login":"Electron752","id":24380030,"avatar_url":"https://avatars3.githubusercontent.com/u/24380030?v=3","gravatar_id":"","url":"https://api.github.com/users/Electron752","html_url":"https://github.com/Electron752","followers_url":"https://api.github.com/users/Electron752/followers","following_url":"https://api.github.com/users/Electron752/following{/other_user}","gists_url":"https://api.github.com/users/Electron752/gists{/gist_id}","starred_url":"https://api.github.com/users/Electron752/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Electron752/subscriptions","organizations_url":"https://api.github.com/users/Electron752/orgs","repos_url":"https://api.github.com/users/Electron752/repos","events_url":"https://api.github.com/users/Electron752/events{/privacy}","received_events_url":"https://api.github.com/users/Electron752/received_events","type":"User","site_admin":false},"created_at":"2017-03-25T23:41:33Z","updated_at":"2017-03-25T23:41:33Z","body":"I'm using kms on my PI3 to test ARM64 and I see that hotplug still appears to be broken on my RPI 3 as well.   The VC4 driver tries to switch from simplefb and it hangs, just like what happens if hotplug is broken.\r\n\r\nI noticed some things that were a bit funky with Eric's GPIO handling code, and I sent an email but nobody paid attention.\r\n\r\nI'm building out of this tree so are the drivers should be available."}}
{"actor":{"display_login":"Electron752"}}