[Bug 94197] New: SAD counting bug inintel/linux-4.0.4/drivers/gpu/drm/drm_edid.c
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Feb 17 16:31:23 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=94197
Bug ID: 94197
Summary: SAD counting bug
inintel/linux-4.0.4/drivers/gpu/drm/drm_edid.c
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: artur999555 at gmail.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 121817
--> https://bugs.freedesktop.org/attachment.cgi?id=121817&action=edit
EDID captured from Krell using OpenELEC/Kodi instructions
I have a Krell Foundation non-4K which has a strange EDID. It does not have
one audio block with multiple SAD within it as do Marantz receivers but rather
it has several audio blocks, one after another.
When I connect the Foundation to an Asrock Beebox running OpenELEC the ELD data
structure ends up with only one element.
I think that is because of these lines of code starting at line 3157 in
intel/linux-4.0.4/drivers/gpu/drm/drm_edid.c
case AUDIO_BLOCK:
/* Audio Data Block, contains SADs */
sad_count = dbl / 3;
if (dbl >= 1)
memcpy(eld + 20 + mnl, &db[1], dbl);
break;
For the Krell, the sad_count would need to be incremented instead of just set
to the value from the EDID. I do not know how this code would keep all the
audio blocks in such a fashion.
Now, if you tell me that the Foundation is doing this incorrectly I am more
than willing to report that to Krell. ;-)
Krill Foundation manual:
http://krellonline.com/downloads/FoundationProcessorOwnersReference_web.pdf
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160217/106575df/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list