Unless you know of an API that exposes different numbers of CB's per stage, I don't think there's any reason not to just make the query return the minimum number supported across all stages. IE. if we can't tell the app about it, do we need to get that information from the driver?
Keith ________________________________________ From: Brian Paul [bri...@vmware.com] Sent: Thursday, January 21, 2010 12:57 PM To: Michal Krol Cc: mesa3d-dev; Keith Whitwell Subject: Re: [Mesa3d-dev] [RFC] gallium-multiple-constant-buffers merge Don't we need a new PIPE_CAP_MAX_CONSTANT_BUFFERS query? Maybe even a query per shader stage? -Brian ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
