From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ralph Siemsen Subject: Re: 2.6.16-rc3 + Xorg 6.9.0 - works for me... Date: Thu, 27 Apr 2006 08:23:07 -0400 Message-ID: <4450B7AB.70904@netwinder.org> References: <43F4AF97.8080909@xandros.com> <443E3A4B.8000101@netwinder.org> <443E4435.1060904@xandros.com> <443F8EB1.30803@netwinder.org> <444FBE2A.90106@xandros.com> <20060426200907.GE9738@flint.arm.linux.org.uk> <444FD4C9.1040209@xandros.com> <20060427114817.GA7196@deprecation.cyrius.com> <20060427115353.GA30095@flint.arm.linux.org.uk> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20060427115353.GA30095@flint.arm.linux.org.uk> Resent-Message-ID: <9XdtrC.A.bVD.-eLUEB@murphy> List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Russell King Cc: Martin Michlmayr , Woody Suwalski , linux-fbdev-devel@lists.sourceforge.net, debian-arm@lists.debian.org Russell King wrote: > And under 2.6, does clearing this burst bit solve your problem? Yes, I have confirmed this behaviour. Clearing the burst flag makes the 2010 work for me. I tried all other sorts of changes, like going back to the "OLD_PLL" code and similar, but none had any effect, except for the burst flag. RMK, its worth noting that "2.4" in the previous conversation was referring to 2.4.19-rmk7, so that may explain why it was working there. So is it a 2010 bug? Seems unlikely... -R PS. I am still seeing X crash after a few hours running x11perf, now with both 2.4 and 2.6 framebuffers. Its easily reproduced, but without any debugging symbols in the X binary, I'm not sure how useful a gdb backtrace would be...