Comment 30 for bug 337608

Revision history for this message
In , Michel Dänzer (michel-daenzer) wrote :

(In reply to comment #4)
> Here's a crazy patch to fix this bug. The real bug is in the server somewhere
> (EXA pixmap migration appears to be broken, judging by the corruption shown in
> the text case vs. UXA and EXA with this patch). But rather than deal with the
> server's EXA migration code (scary) why not just make our driver do pixmap
> management itself?

The reported crash is not likely to be directly related to EXA migration, as that doesn't have any impact on the size of memory mappings.

So while I very much like this patch (I wish this approach had been taken in the first place rather than the whole UXA silliness...), I'm afraid it can only solve the problem indirectly. (Not to mention it won't help people without a kernel memory manager)