summaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorCorbin Simpson <MostAwesomeDude@gmail.com>2009-01-20 15:38:43 -0800
committerCorbin Simpson <MostAwesomeDude@gmail.com>2009-02-01 23:30:24 -0800
commit8d1f386dcbdabaa4edf0301267f881e3831ad18a (patch)
treea66d220623f63071e6dfe4d3e497087fea36f4a7 /src
parent54d137e079b9420e8aca55f37307ece45e9b71d8 (diff)
r300: Set floating-point params.
Note: I took those numbers from classic Mesa. I know that points are routinely used to clear buffers, but line width is probably wrong.
Diffstat (limited to 'src')
-rw-r--r--src/gallium/drivers/r300/r300_screen.c17
1 files changed, 10 insertions, 7 deletions
diff --git a/src/gallium/drivers/r300/r300_screen.c b/src/gallium/drivers/r300/r300_screen.c
index 3cb61b4c4e..a241d606c0 100644
--- a/src/gallium/drivers/r300/r300_screen.c
+++ b/src/gallium/drivers/r300/r300_screen.c
@@ -95,18 +95,21 @@ static float r300_get_paramf(struct pipe_screen* pscreen, int param)
switch (param) {
case PIPE_CAP_MAX_LINE_WIDTH:
case PIPE_CAP_MAX_LINE_WIDTH_AA:
- /* XXX look this up, lazy ass! */
- return 0.0;
+ /* XXX this is the biggest thing that will fit in that register.
+ * Perhaps the actual rendering limits are less? */
+ return 10922.0f;
case PIPE_CAP_MAX_POINT_WIDTH:
case PIPE_CAP_MAX_POINT_WIDTH_AA:
- /* XXX see above */
- return 255.0;
+ /* XXX this is the biggest thing that will fit in that register.
+ * Perhaps the actual rendering limits are less? */
+ return 10922.0f;
case PIPE_CAP_MAX_TEXTURE_ANISOTROPY:
- return 16.0;
+ return 16.0f;
case PIPE_CAP_MAX_TEXTURE_LOD_BIAS:
- return 16.0;
+ return 16.0f;
default:
- return 0.0;
+ /* XXX implementation error? */
+ return 0.0f;
}
}