summaryrefslogtreecommitdiff
path: root/Source/Core/VideoCommon/GraphicsModSystem
diff options
context:
space:
mode:
authorJosJuice <josjuice@gmail.com>2025-12-31 19:26:54 +0100
committerJosJuice <josjuice@gmail.com>2026-02-04 21:35:22 +0100
commit94283c963993336826b141bb367ad54ff2f00507 (patch)
tree3543cc7907e5192bd3d4e0b321d77db16407a0d2 /Source/Core/VideoCommon/GraphicsModSystem
parentb0e2a28e14b28acecbc3648efcaaa0f04c974967 (diff)
Core: Don't call InitMMIO from MemoryManager::Init
In the unit test I'm adding in the next commit, I want to call MemoryManager::Init, but initializing all the hardware that MemoryManager::InitMMIO calls into would be cumbersome. Calling MemoryManager::InitMMIO from MemoryManager::Init was a bit strange anyway. Because MemoryManager::Init is called about halfway through HW::Init, some of the hardware that MemoryManager::InitMMIO calls into isn't initialized yet.
Diffstat (limited to 'Source/Core/VideoCommon/GraphicsModSystem')
0 files changed, 0 insertions, 0 deletions