On Dec 3, 2007, at 5:28 PM, Jeremy Huddleston wrote:
On Dec 3, 2007, at 16:13, Ben Byer wrote:
A couple of things: 1) I know I've been silent on the Xquartz Trac bugs -- I intend to make a pass through later today 2) Ken Thomases (of CodeWeavers / Crossover fame -- go buy their product) and I have been going back and forth for quite some time talking about the rootless bugs / architecture issues; He's had some good suggestions for tracking down the bugs that I haven't had time to implement, so I'm going to try to distill some info from that and send it out in a email -- again, later today. Hopefully they'll inspire one of you.
Do they involve gutting rootless and using kdrive perchance? I'm only half joking...
No, but I *swore* I mentioned the analogous 100% serious suggestion from the X.org folks that we gut rootless and use xcomposite. (I don't know that kdrive solves the problem that we're trying to solve here.) While talking this stuff over with Kevin and Jordan last night, the question arose of "why are we even using fb code at all, when we have all of these shiny libXplugin functions to move bits around?" It turns out there's a threshold, above which it uses the "accelerated" calls, and below which it uses the fb/ code. So, I put a hack in that disables the fb code if you create a file called "/tmp/ disable_fb.txt": http://gitweb.freedesktop.org/?p=xorg/xserver.git;a=commit;h=4dcd9106a89ceb6... If you're experiencing crashes in the fb/rootless code, I'd like to hear if enabling that fixes them. I'd also like to hear if it impacts performance. -- Ben Byer CoreOS / BSD Technology Group, XDarwin maintainer