Really nice article.

Posted Aug 30, 2005 20:09 UTC (Tue) by corbet (editor, #1) [Link]

FWIW, here is the note Jon posted when he quit working on Xgl. It seems to be a matter of not enough people working on it, and too much energy going into things like EXA, which Jon sees as a half measure serving only to delay the deployment of a real solution.

Posted Aug 31, 2005 0:14 UTC (Wed) by airlied (subscriber, #9104) [Link]

Xegl hasn't stopped, I've done some recent work on it, and I'm waiting on the Xgl author to make some changes he has in the pipeline,

but Xegl isn't the beginning and end there is a lot of work to be done that is infrastructure work, he claims fbdev can be used for a lot more than it can, and at KS we decided a userspace solution may be necessary in a lot of cases. Video Memory management is a big area that Xegl needs to get working futher, work in this is area seems to be taking off again and once X.org modular is finished it will probably see more developers.

And the current DRI drivers are completely useful outside of X, I use them in products with Mesa-solo, and Xegl is built on the current radeon DRI driver. The big areas missing are mode setting and memory management.

As for the proprietary ones you'd have to ask NVIDIA/ATI.

Posted Aug 31, 2005 9:25 UTC (Wed) by joib (guest, #8541) [Link]

Yes, I agree the article was really good.

To my uninformed eyes it seems that Xegl represents a very strong and long term vision of how X and Linux graphics should evolve. IMHO it would be a pity to see the project waste away.

I hope that once the dust settles around the X modularization project X.org will think hard about the long term plans and dedicate sufficient resources to Xegl (or something similar).

Posted Aug 31, 2005 14:36 UTC (Wed) by g.da.luz (guest, #32192) [Link]

IMHO, X developers should put some effort to make approaching contributing to the project easier for new developers. When I checked last time, the sticker "in order to accept your contribution, you'll have to show us that you know how to find your own way trough the code" was still there for junior developers. This is of course fine statement in itself, that could be applied equally well to any open source project, but we are talking about 16M lines of code here... As for myself, with almost 10 years of experience in OpenGL application programming, some kernel stuff reading and some spare time and will to spend it on X development, I tried on several occasions to approach DRI and related code, but to no avail - I was more or less able to understand what happens locally in code that I was reading, but I wasn't able to get a slightest clue about big picture. Jon's article helped me too a bit in that regard and maybe current efforts on code modularization will make these things easier to approach too, but I would be still very interested to hear is it possible to split the work in tasks of size that guys of background alike to mine (not X or kernel gurus by any means, but still I guess knowledgeable about graphics to some extent) would be able to help with.

Posted Aug 31, 2005 19:30 UTC (Wed) by josh (subscriber, #17465) [Link]

XCB is under active development at the moment. One reason you might not notice this on the mailing list is that a number of the primary developers all live in the same area, and often communicate and collaborate offline. Another reason is that many of the developers are also students, and are frequently busy with classes. :) Please don't let that discourage you from participating; just because there isn't a ton of traffic on the mailing list at the moment doesn't mean you won't get any discussion if you post there.

The primary focus at the moment is ensuring that Xlib/XCB passes the X Test Suite, at least to the same extent that plain Xlib does. Once that happens, we plan to make Xlib/XCB the default Xlib.