https://bugs.freedesktop.org/show_bug.cgi?id=702

--- Comment #9 from Roland Scheidegger sroland@vmware.com 2010-11-05 21:54:43 PDT --- Created an attachment (id=40078) View: https://bugs.freedesktop.org/attachment.cgi?id=40078 Review: https://bugs.freedesktop.org/review?bug=702&attachment=40078

trivial possible fix

Here's a simple patch which would restore previous (2006...) behaviour... Though I'm thinking probably the driver should just do this on its own depending on the ctx->Point.Size. Note the problem is the hardware has two hw primitives for points: point sprite and point. Only the former can have size larger than 1. I'm not quite sure (or can't remember) why we're not always using point sprites but points when the size is 1 and it's not attenuated. Maybe it's faster.