To read all comments associated with this story, please click here.
one should think so as there is no longer a need for a "sync" between the kernel and X about what state the card is in.
btw, is it just me or have there yet to be a "sync" based system that works flawlessly under load, for any kind of use?
cvs/svn/git is sync for code, and we have heard horror stories about having to clean up large syncs.
calender sync is a hit or miss experience, even when both sides are from the same company.
and the list goes on...
I can assure you, with any recent Intel X-driver, it happens bl**dy constantly. I've tried every recent version but invariably end up going back to 1.7.4 so I can shut down without X falling over so badly I can't even SysReq out of it.
If this approach puts an end to this instability, I'm all for it. But I won't hold my breath...





Member since:
2005-07-06
have always been one of those weird interactions between kernel and X in unix os's.
that a user space app should take over full control of some hardware, to the degree that if said app should get into trouble, there is no way for the kernel to recover from it, was more or less insane.
but then i guess X was originally designed to run on a more bare bones kernel (if any at all) at the terminal end of things, and therefor needed the ability to handle said control.