From a0c8e762026acf2300951ac8a6b6bc293de4a4b1 Mon Sep 17 00:00:00 2001 From: Kenneth Graunke Date: Wed, 10 Jul 2013 13:16:13 -0700 Subject: i965: Cite the Ivybridge PRM for why the fake MRF range is what it is. The exact text is in the public docs, so we should cite those. Signed-off-by: Kenneth Graunke --- src/mesa/drivers/dri/i965/brw_eu_emit.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/mesa/drivers') diff --git a/src/mesa/drivers/dri/i965/brw_eu_emit.c b/src/mesa/drivers/dri/i965/brw_eu_emit.c index cecabc05134..204cea2437e 100644 --- a/src/mesa/drivers/dri/i965/brw_eu_emit.c +++ b/src/mesa/drivers/dri/i965/brw_eu_emit.c @@ -84,7 +84,7 @@ gen6_resolve_implied_move(struct brw_compile *p, static void gen7_convert_mrf_to_grf(struct brw_compile *p, struct brw_reg *reg) { - /* From the BSpec / ISA Reference / send - [DevIVB+]: + /* From the Ivybridge PRM, Volume 4 Part 3, page 218 ("send"): * "The send with EOT should use register space R112-R127 for . This is * to enable loading of a new thread into the same slot while the message * with EOT for current thread is pending dispatch." -- cgit v1.2.3