This patch introduces a segfault for me due to rhdCrtc->CurrentMode being NULL. Had to work around it with the following: Using height is not a god idea, since it is the height of the
Am Dienstag, den 24.02.2009, 00:01 -0800 schrieb Yang Zhao: framebuffer, not what the crtc is actually scanning out of the framebuffer (AFAIK). Waiting for a line that's not scanned out can easyly deadlock the hardware.
Haven't had a chance to figure out why DxModeSet, which sets CurrentMode, isn't called. I know why, Active gets set when the Crtc is assigned to ANY connector, and not if the crtc is active and displaying a picture. You probably have more than one connector and the monitor isn't connected to the first one. We are hardcoded waiting on the first one atm, since i haven't had time yet to figure out on which crtc we are actually rendering.
@Alex: Could you push this bugfix (again). I promise not to write patches at three o'clock in the morning again. Bye, Christian.