ShuriZma
/
xenia-canary
mirror of https://github.com/xenia-canary/xenia-canary.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Shouldn't need these range asserts anymore.

This commit is contained in:
Dr. Chat 2015-05-23 14:25:10 -05:00
parent d71ad2d5a3
commit 9d2e8d4699
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/xenia/kernel/xboxkrnl_memory.cc
View File

@ -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);