Thread (16 messages) 16 messages, 6 authors, 2005-01-24

Re: Radeon framebuffer weirdness in -mm2

From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: 2005-01-24 04:01:08
Also in: lkml

On Thu, 2005-01-20 at 22:09 -0800, Matt Mackall wrote:
It's something in this batch. Which is good, as I'd be a bit
disappointed if the "vt leakage" were somehow attributable to the fb
layer. More bisection after dinner.
Regarding the radeonfb reboot problem, can you try this patch on
top of -mm2 ?
--- linux-work.orig/drivers/video/aty/radeon_base.c	2005-01-24 12:19:09.000000000 +1100
+++ linux-work/drivers/video/aty/radeon_base.c	2005-01-24 14:59:14.000000000 +1100
@@ -2435,13 +2435,16 @@
  
 	radeonfb_pm_exit(rinfo);
 
+#if 0
 	/* restore original state
 	 * 
-	 * Doesn't quite work yet, possibly because of the PPC hacking
-	 * I do on startup, disable for now. --BenH
+	 * Doesn't quite work yet, I suspect if we come from a legacy
+	 * VGA mode (or worse, text mode), we need to do some VGA black
+	 * magic here that I know nothing about. --BenH
 	 */
         radeon_write_mode (rinfo, &rinfo->init_state, 1);
- 
+ #endif
+
 	del_timer_sync(&rinfo->lvds_timer);
 
 #ifdef CONFIG_MTRR




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help