https://bugs.freedesktop.org/show_bug.cgi?id=96711
Kevin Brace <kevinbr...@gmx.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kevinbr...@gmx.com
--- Comment #1 from Kevin Brace <kevinbr...@gmx.com> ---
Hi Roc,
Sorry about the trouble the new code has caused.
In general, no part of the rendering engine control code has been touched,
however, it is quite possible that turning on certain registers that sound like
"enable prefetch mode" might have caused the problem.
At this point, since I do not have the exact hardware you have, you may have to
try to bisect the code to see which version still works and which one doesn't.
I had someone who was able to do this, and I plan to get a patch for him to try
in the next few hours.
He told me that Version 0.4.151 worked but 0.4.152 didn't. (Bug 96352)
I will delay release of the new official release version until this
particular bug is resolved.
Regarding the viafb related bug you have reported, my view is that more and
more registers have to be initialized correctly by OpenChrome itself, and I
have been doing this, but due to lack of official programming documents for all
but last 4 devices (i.e., CX700, VX800, VX855, and VX900) makes it difficult to
properly develop OpenChrome.
I hope the future releases will gradually solve this problem, and you will no
longer have to have viafb.
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Openchrome-devel mailing list
Openchrome-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/openchrome-devel
