rust-osdev / rust-osdev/bootloader
BIOS booting: Consider framebuffer config of kernel ELF
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.7k
- Forks
- 240
- PR merge metrics
- No merged PRs in 30d
Description
Right now the BIOS implementation does not consider the framebuffer configuration of the kernel. Instead, it just defaults to a hardcoded resolution.
To fix this, we would need to parse the kernel ELF file already in the real mode stages, which could be challenging because of the memory limits in real mode. Alternatively, we could copy the framebuffer settings to a small text file and place this file alongside the kernel executable on the FAT partition.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the BIOS implementation and its real mode stages, focusing on how the kernel ELF is loaded and how the hardcoded framebuffer resolution is selected. Compare parsing the ELF in real mode with copying framebuffer settings to a text file on the FAT partition; done means the BIOS boot path uses the kernel's framebuffer configuration instead of a hardcoded resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100