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:
- The X,Y in drmModeSetCrtc does in fact specify the "source" offset into
your framebuffer (not the destination on the CRTC) which is what I was
lo
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
