From 9d2e8d4699d475656c8ac6647979f7fdd969cba9 Mon Sep 17 00:00:00 2001 From: "Dr. Chat" Date: Sat, 23 May 2015 14:25:10 -0500 Subject: [PATCH] Shouldn't need these range asserts anymore. --- src/xenia/kernel/xboxkrnl_memory.cc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/xenia/kernel/xboxkrnl_memory.cc b/src/xenia/kernel/xboxkrnl_memory.cc index fe98c4d27..d548edf49 100644 --- a/src/xenia/kernel/xboxkrnl_memory.cc +++ b/src/xenia/kernel/xboxkrnl_memory.cc @@ -306,8 +306,8 @@ SHIM_CALL MmAllocatePhysicalMemoryEx_shim(PPCContext* ppc_state, // and the memory must be allocated there. I haven't seen a game do this, // and instead they all do min=0 / max=-1 to indicate the system should pick. // If we have to suport arbitrary placement things will get nasty. - assert_true(min_addr_range == 0); - assert_true(max_addr_range == 0xFFFFFFFF); + //assert_true(min_addr_range == 0); + //assert_true(max_addr_range == 0xFFFFFFFF); uint32_t allocation_type = kMemoryAllocationReserve | kMemoryAllocationCommit; uint32_t protect = FromXdkProtectFlags(protect_bits);