About kdrive status
jeremyhu at apple.com
Wed May 11 23:02:16 PDT 2011
FWIW, we're still shipping Xnest, Xephyr, Xvfb, Xfake built from the server-1.6-branch because the ones built out of 1.7.x and later no longer work (I think something XKB related, but I forget exactly what) and I don't have any intention of figuring out a workaround.
I haven't actually looked into building the X.Org server / xfree86 DDX on darwin as an alternative, so I can't confirm that they don't work (just that it's never been tried by me). Jamey, do you know who told you that it doesn't work, or can you tell me specifically what doesn't work, so I can put it on my list of things todo? It would be nice to at least get that DDX buildable on OSX. Is the problem some dependency on libpciaccess, libdrm, DRI2, etc that needs to be better conditionalized?
On May 11, 2011, at 12:56 PM, Jamey Sharp wrote:
> On Wed, May 11, 2011 at 04:50:17PM +0800, Liu Peng wrote:
>> Ajax (Adam Jackson) mentioned that the drivers for kdrive were broken and in
>> every way inferior to the corresponding Xorg drivers.
>> So, what's the status of kdrive, is it obsolete?
> As I recall, there's a consensus that the Xfbdev driver in kdrive is
> completely redundant with the X.Org fbdev driver, but the situation with
> Xephyr and Xfake is less clear.
> With the recent push of the X.Org nested driver, both the Xephyr and
> Xfake kdrive servers have counterparts in X.Org drivers. However, as far
> as I can tell, Xephyr and Xfake should work on Windows and Mac, and I'm
> told that X.Org currently doesn't. Also, the nested driver is not yet as
> functional or as efficient as Xephyr.
> For those reasons, I think Xephyr and Xfake will live a little longer,
> but personally I hope their days are numbered.
> xorg-devel at lists.x.org: X.Org development
> Archives: http://lists.x.org/archives/xorg-devel
> Info: http://lists.x.org/mailman/listinfo/xorg-devel
More information about the xorg-devel