Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why request meminfo and align in multiboot header if neither are used? #2

Open
pixelherodev opened this issue Oct 13, 2019 · 1 comment

Comments

@pixelherodev
Copy link

From the Multiboot Specification:



If bit 0 in the ‘flags’ word is set, then all boot modules loaded along with the operating system must be aligned on page (4KB) boundaries. Some operating systems expect to be able to map the pages containing boot modules directly into a paged address space during startup, and thus need the boot modules to be page-aligned.

If bit 1 in the ‘flags’ word is set, then information on available memory via at least the ‘mem_*’ fields of the Multiboot information structure (see Boot information format) must be included. If the boot loader is capable of passing a memory map (the ‘mmap_*’ fields) and one exists, then it may be included as well. 

However, this OS does not at any point use the multiboot info structure, ever! Is this because it's meant to be used in the future?

@sagehane
Copy link

sagehane commented May 4, 2021

Likely because it's simply copied verbatim from the Bare Bones tutorial. No idea why they chose to set those flags.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants