Chase Douglas wrote: > Jerome Glisse wrote: >> Theory is mostly good however i see a couple of issues. First the >> big one is that you put to much things in the driver, in fact this >> limitation would be better worked out in core mesa without >> having to touch the driver. Mainly because every driver otherwise >> will have to duplicate the code and i believe this somethings that >> should be avoided. Moreover i think it will be easier and cleaner >> to hack this into mesa because mesa have a better view of what >> is going on, i will balance this a bit as there is still need for some >> card information more below. >> > > I understand why it would be nice to have this as a core mesa piece, but > does this situation, where 3D rendering is smaller than many dual > monitor setups but 2D rendering is not, come up frequently? > > Thanks
I would say all radeon up to r400, savage, volari and likely a lot of older nvidia card have this limitation and this are for the card currently supported by an open source driver. So it's basically all cards we support. Btw as their are many massive change going on in graphics driver area (new mesa driver interface: softpipe, proper memory manager, modesetting, ...) i think you better go on with your current hack and a more general solution might be worked out once all this big changes have settle a bit. Cheers, Jerome Glisse ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Mesa3d-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
