[PULL to discuss] Remove kdrive, Xnest, and Xvfb

Chase Douglas chase.douglas at canonical.com
Mon Mar 26 18:16:20 PDT 2012

On 03/26/2012 05:50 PM, Jamey Sharp wrote:
> On Mon, Mar 26, 2012 at 5:09 PM, Chase Douglas
> <chase.douglas at canonical.com> wrote:
>> On 03/26/2012 04:55 PM, Jamey Sharp wrote:
>>> xf86-video-dummy doesn't have an equivalent to -fbdir, but it looks
>>> like you aren't actually making use of the mmap'd framebuffer in
>>> /var/tmp/. So this case should work just fine with xf86-video-dummy
>>> today as well.
>> I haven't looked into screen scraping much, but I thought it wasn't
>> supported by the dummy video driver. I'm glad to see it is.
>> What does it take to get a screen capture out of the dummy driver? Is it
>> something you would recommend we encapsulate inside of xorg-gtest?
> Sure, GetImage on the root window works just like it does on any other
> video driver. Jeremy, Josh, and I sponsored a recently-completed
> capstone project where the students produced quite a bit of code
> relying on that:
> http://cgit.freedesktop.org/xorg/lib/libxcwm/

Thanks for the tip, we'll look into it.

> I haven't paid too much attention to xorg-gtest; I assume it's a
> framework for building X server test suites? I'd certainly recommend
> using xf86-video-dummy if you're kicking off an X server during any
> automated test procedure. Sometimes people might appreciate a
> configuration option to use xf86-video-nested instead, so they can see
> the test output. I'm not sure there's anything else you'd need to
> encapsulate in xorg-gtest that's specific to the dummy driver though.

Yeah, it kicks off a background X server using the dummy video driver by
default. You can use the --no-dummy-server option when running tests to
run them on the current $DISPLAY server, and you can specify your own
xorg.conf with nested if needed.

If it's really as simple as using XGetImage, then we probably don't need
to abstract it any inside xorg-gtest.

-- Chase

More information about the xorg-devel mailing list