why not compile Xorg 7.2 ?
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]
What you will benefit from it ? Except eating more memory? I'd prefer compiling kdrive.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=157837\"][{POST_SNAPBACK}][/a][/div]
this my question, but not have a good anwser, but fix all, to after put new thigs is a good choice, and xorg7.2 can compiled as kdrive not ?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=157855\"][{POST_SNAPBACK}][/a][/div]
My impression as per this thread
[a href=\"https://www.oesf.org/forums/index.php?showtopic=17950&hl=transparency]https://www.oesf.org/forums/index.php?showt...hl=transparency[/url]
is that Xorg6.9 uses less memory than xfree.
I would think that since 7.2 is even more modular than 6.9, that it might take even less memory.
By the way, as to it's heaviness, xorg takes more ROM space, but less RAM space than xfree AFAIK. Sorry if this is incorrect.
I've been trying to cross-compile 6.9, from the following page:
http://www.linuxfromscratch.org/blfs/view/stable/x/xorg.htmlbut failing pretty consistently. (Don't currently have my output, but building up to attempting a native build from a 6000).
Another benefit of compiling xorg might be that fonts could be set up more like standard X fonts, since I haven't been able to get any new ".pfb" fonts working other than what comes with the xfree package.
It would probably be somewhat difficult to apply the pdaxrom patches to the 6.9 source. Then again, maybe not.
Last I heard, both Angstrom and OpenZaurus were using xorg7.1 with "--enable-kdrive" at compile time.
https://www.oesf.org/forums/index.php?showt...22487&hl=kdrivehttps://www.oesf.org/forums/index.php?showtopic=23402&hl=#9 (post #9)