rust-osdev / rust-osdev/bootloader
Make the FrameBufferWriter and logger in to a separate crate so it can be reused by a kernel for quick start?
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 bootloader-x86_64-common crate has std dependencies. and doesn't compile with no_std flag. If that can be made to work with no_std or move the framebuffer logic to a separate crate it would be usable by kernel code and helps with quick start of a kernel that can log messages.
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 inspecting the bootloader-x86_64-common crate, especially FrameBufferWriter and its logger, to identify the std dependencies preventing no_std compilation. Determine whether the crate can support no_std or whether the framebuffer logic should be extracted. Done means kernel code can reuse the logging functionality for a quick start.
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