On Thu, 9 Jul 2009 11:37:30 -0400
Alex Deucher <alexdeucher@...> wrote:
> On Thu, Jul 9, 2009 at 11:15 AM, Keith Packard<keithp@...>
> > On Wed, 2009-07-08 at 20:28 +0100, Julien Cristau wrote:
> >> DRI2 init can fail for various reasons, and it's easier to test if
> >> you don't have to hack the driver. No particular opinion on kms
> >> without uxa, though.
> > Right, which is why I also fixed the DRI option parsing in the KMS
> > case (which was broken before).
> > Any thoughts on whether NoAccel remains useful though?
> Might be useful to bring up a shadowfb or noaccel X if the user is
> having accel problems, just to have a desktop.
Yeah, getting *something* displayed when things break is important.
But at least in our case, keeping NoAccel code working turns out to be
hard, since it violates most of the assumptions in the rest of the
driver code. And if it's usually broken it won't be much use to
people... I wonder if fbdev could fill the "get something on the
screen when the driver is busted" hole. Is it good enough to rely on