On Wed, 2003-07-09 at 16:03, Alex Deucher wrote:
> --- Richard F Weber <[EMAIL PROTECTED]> wrote:
> > >
> > >> So I guess my next questions are: 1) is the 2048x2048 a HW 
> > >> limitation, or a SW/implementation limitation
> > >
> > > AFAIK the maximum size of the GL context is a hardware issue.
> > However,
> > > it shouldn't matter where it is displayed, that is it should work
> > on the
> > > second head as well (hardware-wise), as long as the height or width
> > of
> > > the GL window doesn't exceed 2048. If it doesn't work in that
> > manner, 
> > > that's probably because how the driver handles the GL contexts. 
> > 
> > I think I mentioned it below, but I found some docs indicating that
> > the 
> > 2048x2048 is a limitation on the viewport to the framebuffer.  But if
> > 
> > that's the case, then I'd expect the mergedfb stuff to have a
> > problem.
> 
> I haven't been able to test mergedfb with a 3D context of 2048x2048 or
> larger since my m6 only has 8 mb of ram.

You could try with just the horizontal or vertical virtual resolution
larger than 2048?


> According to Michel Danzer, you may be able to support up to 4096x4096
> using two cliprects, [...]

Well, actually four cliprects in the worst case. :)


-- 
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/bulletproofapps
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to