On Mon, 2003-07-14 at 02:59, Alex Deucher wrote: > --- Michel Dnzer <[EMAIL PROTECTED]> wrote: > > On Mon, 2003-07-14 at 00:34, Alex Deucher wrote: > > > > > however, the framebuffer on crtc1 is still shifted a few pixels to > > > the left when you run an opengl app in clone mode. side by side > > > modes work fine. everything works fine with pageflipping disabled. > > > > Hmm, for a second I thought I had botched the RADEON_CRTC_OFFSET > > calculation in the DRM as well, but it looks to me like it should be > > identical to that in RADEONDoAdjustFrame(). Agreed? > > I would think so. Should the patch [...]
I forgot to unattach the patch, it's clearly wrong (if it was correct, the error would have been significant and on the y axis). Do you agree that in RADEONDoAdjustFrame() and radeon_cp_dispatch_flip() the same value gets written to RADEON_CRTC_OFFSET for the same frame position? (Note that pitch = displayWidth * <bytes per pixel>) > > > > > I'm trying to understand how this would work. with the driver > > as it > > > > is > > > > > now, if you create a single 3D window greater than 2048 in > > either > > > > > dimension, it will only display up to 2048. now, again with > > the > > > > driver > > > > > as it is now, if you displayed two 3D windows with a total size > > of > > > > > greater then 2048 in one dimension would/should it work? > > > > > > > > That's what someone needs to find out. :) If that works, then the > > > > cliprect split trick should work as well. > > > > > > Alas, it doesn't work. If run two apps side by side both display > > fine > > > up to 2048. if you cross the 2048 boundry, the 3D window that > > crosses > > > it goes blank. :( looks like we may not be able to go above 2048 > > for > > > 3D. > > > > It's not clear to me what exactly you have tried, please describe in > > more detail. > > I created a virtual framebuffer of size 2080x480. I then started an > instance of glxgears and resized the window to about 3/4 of the size of > the frambuffer. I then started a second instance of glxgears and > placed it next to the first instance, then resized it. it resized fine > until I hit the 2048 boundry, then the window (the one I was resizing), > went black; the first window was still showed gears. resizing smaller, > the gears came back when I crossed the 2048 boundry again. Weird, I don't understand what would cause the window to go blank. What happens when you enlarge a single window beyond 2048, does it go blank as well, or is the rendering cropped to 2048? In the latter case I suspect this is a different problem. -- Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer ------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
