andrewrk / andrewrk/HellOS

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

Open
#2 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Zig
Stars
339
Forks
40
PR merge metrics
No merged PRs in 30d

Description

From the [Multiboot Specification](https://www.gnu.org/software/grub/manual/multiboot/multiboot.html#OS-image-format):

```

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?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.