Bingo, that does it exactly.
> You must not do any output during register framebuffer. If you'll output
> one line, I believe that it will still work, but if you'll do more,
> kernel output is catched in upper Tux window instead of in the bottom half
> of screen. And if you'll print really much of info during
> register_framebuffer, kernel will die...
Well, that's a good reason to get this patch into the 2.4.15-final, then.
--- radeonfb.c.orig Tue Nov 20 12:08:54 2001
+++ radeonfb.c Tue Nov 20 12:09:24 2001
@@ -2347,7 +2347,7 @@
OUTREG(CRTC_OFFSET, 0);
OUTREG(CRTC_OFFSET_CNTL, 0);
OUTREG(CRTC_PITCH, mode->crtc_pitch);
-#if 1
+#if 0
printk("CRTC_H_TOTAL_DISP = 0x%x, H_SYNC = 0x%x\n",
mode->crtc_h_total_disp, mode->crtc_h_sync_strt_wid);
printk("CRTC_V_TOTAL_DISP = 0x%x, V_SYNC = 0x%x\n",
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/