https://bugs.freedesktop.org/show_bug.cgi?id=63857
Xavier Bachelot <xav...@bachelot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|gan...@poczta.onet.pl |openchrome-de...@lists.free
| |desktop.org
CC| |xav...@bachelot.org
--- Comment #7 from Xavier Bachelot <xav...@bachelot.org> ---
The patches mentioned above have been pushed to master some time ago and are
part of the 0.3.2 release.
What Willem is seeing is a failure to initialize the driver because the
selected mode has been rejected by iga[12]_crtc_mode_fixup. However, the
current code is not verbose at all on the reason for the rejection. I'm
attaching a patch that doesn't fix the issue, but should provide more
information on the mode rejection.
The same mode rejection bug has been reported already and has been somewhat
worked around by changing the connected monitor and thus the used mode.
See https://bugs.freedesktop.org/show_bug.cgi?id=63194
Changing the screen won't indeed work here as the screen is a TV set, but it
might be possible to tweak HorizSync and VertRefresh in the X conf to work
around it. Anyway, this look as a regression, either in openchrome or in the X
server and would need a proper fix.
Bartosz, I've assigned the ticket back to openchrome-devel ML so the replies
are still going to the mailing list. You're still in CC: though.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Openchrome-devel mailing list
Openchrome-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/openchrome-devel
