drmModeSetCrtc and how to use x,y (original) (raw)

Rian Quinn rianquinn at gmail.com
Thu Feb 13 06:05:23 PST 2014


In case someone else reads this, I think I sort of answered my questions. We tested on the AMD w600 with 6 monitors and were able to do the following:

I didn't try it with drmModePageFlip, but I don't think that should be an issue since you have to run drmModeSetCrtc first to set your mode anyways. If you need a good example of page flipping, David Herrmann has a good blog post on it: http://dvdhrm.wordpress.com/2012/12/21/advanced-drm-mode-setting-api/

Thanks,

On Wed, Feb 12, 2014 at 2:05 PM, Rian Quinn <rianquinn at gmail.com> wrote:

With respect to Windows XDDM, in the past I was able to map more than one display to a single framebuffer by leveraging width, height, stride, and then adding an offset to the framebuffer's char*. I can see how this would work with dumb buffers as they are basically a simple linear ARGB buffer, but how does this work with respect to GBM buffers that are tiled?

My initial thought was to use the x,y in drmModeSetCrtc. Basically, I could create a framebuffer in GBM that spanned multiple displays. From there, I could use drmModeSetCrtc to tell the CRTC where, within the framebuffer, to get it's data. Is that the proper use of x,y in drmModeSetCrtc, and if so, does it handle the titling issues behind the scenes? Also, are there any limitations with a design like that. For example, is it possible to create GBM buffers that span 6 monitors wide? Thanks, - Rian -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140213/b629d77c/attachment.html>



More information about the dri-devel mailing list