On Thu, 29 Sep 2011 16:26:32 +0100 Dave Airlie <airlied@xxxxxxxxx> wrote: > From: Dave Airlie <airlied@xxxxxxxxxx> > > For the simple KMS driver case we need some more info about argb cursor > limits and a preferred depth and if shadowed framebuffer access is preferred. > > I've only added this for intel/radeon which support the dumb ioctls so far. > > I really don't want to expose a truck load of info, just enough for X to > start without configuration with a hw cursor. Actually there is probably one other thing to report - which is whether the buffers are cached. That general piece of info "front/back buffer cached/uncached" allows you to both make intelligent decisions about using back buffers and also about which copy algorithms to use. I guess X could work it out by timing algorithms at start up. Also you call this max cursor width - in some devices isn't it actually a fixed cursor width ? _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
