From 85d2358157e0ed36a8350dd615e08f98e7b6a2e5 Mon Sep 17 00:00:00 2001 From: Vincent Pelletier Date: Wed, 28 Sep 2022 11:52:12 +0000 Subject: [PATCH] EXI_DeviceMemoryCard: Drop comment about ChipErase behaviour Tested on an official DOL-014 (251 blocks) memory card by executing the 0xf4 command on a card with content along its entire length and then dumping the whole card: it reads as 0xff all the way through. Therefor, the current implementation is already consistent with hardware. --- Source/Core/Core/HW/EXI/EXI_DeviceMemoryCard.cpp | 2 -- 1 file changed, 2 deletions(-) diff --git a/Source/Core/Core/HW/EXI/EXI_DeviceMemoryCard.cpp b/Source/Core/Core/HW/EXI/EXI_DeviceMemoryCard.cpp index 0a48ffe7b9..2aa5c1bbb5 100644 --- a/Source/Core/Core/HW/EXI/EXI_DeviceMemoryCard.cpp +++ b/Source/Core/Core/HW/EXI/EXI_DeviceMemoryCard.cpp @@ -295,8 +295,6 @@ void CEXIMemoryCard::SetCS(int cs) case Command::ChipErase: if (m_position > 2) { - // TODO: Investigate on HW, I (LPFaint99) believe that this only - // erases the system area (Blocks 0-4) m_memory_card->ClearAll(); m_status &= ~MC_STATUS_BUSY; }