From 482f2e24b59086bcc1515663167744c707d1c82c Mon Sep 17 00:00:00 2001 From: Eric Anholt Date: Thu, 12 Apr 2018 15:19:42 -0700 Subject: [PATCH] broadcom/vc5: Don't allocate simulator BOs at offset 0. The kernel won't return us BOs at offset 0 (because things like OQs wouldn't work there), so we shouldn't in the simulator either. --- src/gallium/drivers/vc5/vc5_simulator.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/src/gallium/drivers/vc5/vc5_simulator.c b/src/gallium/drivers/vc5/vc5_simulator.c index ee4ffb28c04..5fbcad346ad 100644 --- a/src/gallium/drivers/vc5/vc5_simulator.c +++ b/src/gallium/drivers/vc5/vc5_simulator.c @@ -594,7 +594,11 @@ vc5_simulator_init_global(const struct v3d_device_info *devinfo) v3d_hw_get_mem(sim_state.v3d, &sim_state.mem_size, &sim_state.mem); - sim_state.heap = u_mmInit(0, sim_state.mem_size); + /* Allocate from anywhere from 4096 up. We don't allocate at 0, + * because for OQs and some other addresses in the HW, 0 means + * disabled. + */ + sim_state.heap = u_mmInit(4096, sim_state.mem_size - 4096); /* Make a block of 0xd0 at address 0 to make sure we don't screw up * and land there. -- 2.30.2