efi/arm64: Don't bail out when mapping TTBR1 in map_range

mingw EDK2 gives us a memory map containing a one-page-long
entry that happens to be TTBR1. Because we were bailing out
in map_range, we couldn't update that page after entering
the kernel

Change-Id: Ie38fc593da268ab2a1f3ca98f3bffce36a6a6964
Reviewed-on: https://review.haiku-os.org/c/haiku/+/10658
Reviewed-by: waddlesplash <[email protected]>
Haiku-Format: Haiku-format Bot <[email protected]>
This commit is contained in:
Sam Roberts
2026-04-04 20:26:46 +00:00
committed by waddlesplash
parent 777cfcfb8b
commit 00b9933841
@@ -216,12 +216,6 @@ map_range(addr_t virt_addr, phys_addr_t phys_addr, size_t size, uint64_t flags)
return;
}
// TODO: Review this case
if (phys_addr == READ_SPECIALREG(TTBR1_EL1)) {
TRACE("Trying to map the TTBR itself?!\n");
return;
}
if (arch_mmu_read_access(virt_addr) && arch_mmu_read_access(virt_addr + size)) {
TRACE("Range already covered in current MMU\n");
return;