[Mesa3d-dev] [Bug 5785] larger textures sizes should be announced with DRI drivers
http://bugs.freedesktop.org/show_bug.cgi?id=5785 ajax at nwnk dot net a...@nwnk.net changed: What|Removed |Added Version|CVS |git --- Comment #8 from ajax at nwnk dot net a...@nwnk.net 2009-08-24 12:23:41 PST --- Mass version move, cvs - git -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
[Mesa3d-dev] [Bug 5785] larger textures sizes should be announced with DRI drivers
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=5785 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2006-02-04 00:30 --- commited. driconf translations except german are missing. I've added this to the intel driver too, since it already used a hack to only calculate the limits so that one texture always fits (though this driver seems to use driconf differently, it looks like it never parses the config file? YMMV), which I've left as default there. radeon/r200 still default to calculate the limits so all texture units can bind a worst-case texture. IMHO I think this default is a bit too conservative. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
[Mesa3d-dev] [Bug 5785] larger textures sizes should be announced with DRI drivers
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=5785 --- Additional Comments From [EMAIL PROTECTED] 2006-02-03 03:12 --- (In reply to comment #4) Created an attachment (id=4544) -- (https://bugs.freedesktop.org/attachment.cgi?id=4544action=view) [edit] patch for announcing larger texture sizes Does this look reasonable? It looks pretty much okay. I'm wondering about the change to get_max_size (and the associated changes to SET_MAX and SET_MAX_RECT). Removing the '+ 1' allows get_max_size to return 0 in non-error cases. I don't think that's a particularly a problem, though. ACK. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
[Mesa3d-dev] [Bug 5785] larger textures sizes should be announced with DRI drivers
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=5785 --- Additional Comments From [EMAIL PROTECTED] 2006-02-03 04:46 --- (In reply to comment #5) It looks pretty much okay. I'm wondering about the change to get_max_size (and the associated changes to SET_MAX and SET_MAX_RECT). That's just a cheap way out to not have to handle the case separately when the hw limits are used directly. You're right though it would set non-null sizes if one sort of texture isn't supported, though as far as I can tell it will never return 0 since currently it looks like the smallest number it will ever return is 2. I'll find a nicer solution. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
[Mesa3d-dev] [Bug 5785] larger textures sizes should be announced with DRI drivers
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=5785 --- Additional Comments From [EMAIL PROTECTED] 2006-02-02 04:07 --- The texture size limits advertised by all of the drivers is very conservative. This is an issue that has come up a few times before. There's a trade off. We can advertise the actual hardware limits or we can advertise the limits that we can guarantee will work. We're stuck with either having to fallback to software if an app tries to use too much texture memory at once or artificially limit the available texture sizes. This technique was introduced back in the Quake 2 days. There were some low-memory cards that could end up on a software path with Quake 2's default settings when the full texture sizes were advertised. With the new memory manager that Keith is writing, this won't be an issue. We should always be able to map any texture into the GART, so the allocations will never fail. In the mean time, it might be best to add a config option Conservative Texture Limits that defaults to on. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
