[Bug 102931] Radeon : EDID Reading Incorrectly

2015-08-17 Thread bugzilla-dae...@bugzilla.kernel.org
https://bugzilla.kernel.org/show_bug.cgi?id=102931

Maxqia  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |INVALID

-- 
You are receiving this mail because:
You are watching the assignee of the bug.


[Bug 102931] Radeon : EDID Reading Incorrectly

2015-08-17 Thread bugzilla-dae...@bugzilla.kernel.org
https://bugzilla.kernel.org/show_bug.cgi?id=102931

Christian König  changed:

   What|Removed |Added

 CC||deathsimple at vodafone.de

--- Comment #4 from Christian König  ---
get-edid calls into the BIOS directly to access the I2C bus and doesn't uses
the driver. With a kernel driver this is pretty much deprecated and shouldn't
be used any more.

Use the one provided in sysfs instead, try: find /sys -name "edid"

-- 
You are receiving this mail because:
You are watching the assignee of the bug.


[Bug 102931] Radeon : EDID Reading Incorrectly

2015-08-17 Thread bugzilla-dae...@bugzilla.kernel.org
https://bugzilla.kernel.org/show_bug.cgi?id=102931

--- Comment #3 from Maxqia  ---
Created attachment 185121
  --> https://bugzilla.kernel.org/attachment.cgi?id=185121=edit
get-edid | parse-edid output

According to the read-edid website and the program output, get-edid uses the
i2c bus.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.


[Bug 102931] Radeon : EDID Reading Incorrectly

2015-08-17 Thread bugzilla-dae...@bugzilla.kernel.org
https://bugzilla.kernel.org/show_bug.cgi?id=102931

--- Comment #2 from Alex Deucher  ---
This is not a driver bug.  It's a limitation of get-edid.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.


[Bug 102931] Radeon : EDID Reading Incorrectly

2015-08-17 Thread bugzilla-dae...@bugzilla.kernel.org
https://bugzilla.kernel.org/show_bug.cgi?id=102931

Alex Deucher  changed:

   What|Removed |Added

 CC||alexdeucher at gmail.com

--- Comment #1 from Alex Deucher  ---
IIRC, get-edid doesn't actually probe any i2c buses, it uses vm86 to do vbe
calls to the vbios.  vbe will only provide the edid for whatever monitor it
happened to probe at boot and likely won't work correctly once a real driver is
loaded.  It's also not multi-head aware so if you have multiple monitors
attached or are using a different display than what was available at boot it
probably won't work.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.