From 6613fdd32ce85be1e2ff1e8307fa4699096a103b Mon Sep 17 00:00:00 2001 From: belliash Date: Thu, 26 Jan 2023 16:55:34 +0100 Subject: [PATCH] Correct markdown --- IDEAS.md | 10 +++++----- KNOWN_ISSUES.md | 9 +++++---- 2 files changed, 10 insertions(+), 9 deletions(-) diff --git a/IDEAS.md b/IDEAS.md index 167a310..b8b4710 100644 --- a/IDEAS.md +++ b/IDEAS.md @@ -1,8 +1,8 @@ # ExectOS Ideas This is a list of ideas that migh but not must be realized. -[ ] Move processor context initialization (GDT, IDT, LDT, PCR, TSS) from XTLDR to XTOSKRNL to simplify the XTOS boot - protocol. -[ ] Rewrite memory mapping and paging support in bootloader to make it more flexible and architecture independent. - This should support paging levels, thus allowing to make a use of PML5 on modern AMD64 processors and increasing - the addressable virtual memory from 256TB to 128PB. + - [ ] Move processor context initialization (GDT, IDT, LDT, PCR, TSS) from XTLDR to XTOSKRNL to simplify the XTOS boot + protocol. + - [ ] Rewrite memory mapping and paging support in bootloader to make it more flexible and architecture independent. + This should support paging levels, thus allowing to make a use of PML5 on modern AMD64 processors and increasing + the addressable virtual memory from 256TB to 128PB. diff --git a/KNOWN_ISSUES.md b/KNOWN_ISSUES.md index 28b9c93..7b49897 100644 --- a/KNOWN_ISSUES.md +++ b/KNOWN_ISSUES.md @@ -2,7 +2,8 @@ This is a list of well known bugs that exists in all master branch builds. ## XTLDR -[ ] In some specific scenarios (most probably EFI by Insyde) XTLDR cannot load modules. Calling BootServices->LoadImage() - fails with STATUS_EFI_NOT_FOUND status code. Possibly this is a bug in BlFindVolumeDevicePath() routine. -[ ] EFI Runtime Services are not mapped properly into higher half. They are mapped itself, but all pointers inside that - structure point to some physical address that is unavailable after paging is enabled. + - [ ] In some specific scenarios (most probably EFI by Insyde) XTLDR cannot load modules. Calling the EFI's + BootServices->LoadImage() fails with STATUS_EFI_NOT_FOUND (0x800000000000000E) status code. Possibly this is + a bug in BlFindVolumeDevicePath() routine. + - [ ] EFI Runtime Services are not mapped properly into higher half. They are mapped itself, but all pointers inside + that structure point to some physical address that is unavailable after paging is enabled.