You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 6, 2023. It is now read-only.
Currently the initial scratch space is in the UEFI FD image. I reduced the image size from 8MB to ~2.2MB and most of the second free area (green) is the scratch space.
We probably don't need to waste this space. I think this scratch space is only used in the very beginning and then we use physical RAM for the scratch space.
Since memory is trained when EDK2 starts (on all platforms so far), we probably don't to start off with scratch space in memory.
The text was updated successfully, but these errors were encountered:
JohnAZoidberg
changed the title
Investigate if initial scratch space has to in FD image
Investigate if initial scratch space has to be in FD image
May 9, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently the initial scratch space is in the UEFI FD image. I reduced the image size from 8MB to ~2.2MB and most of the second free area (green) is the scratch space.
We probably don't need to waste this space. I think this scratch space is only used in the very beginning and then we use physical RAM for the scratch space.
Since memory is trained when EDK2 starts (on all platforms so far), we probably don't to start off with scratch space in memory.
The text was updated successfully, but these errors were encountered: