feat: implement framebuffer driver, get rid of VGA text mode #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…if possible Closes #3
marekvospel
force-pushed
the
framebuffer
branch
from
e83e3df
to
115746a
Compare
|
Instead of refactoring, I'll close this and rewrite it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This merge request takes a step towards UEFI compatibility, by not using the legacy VGA text mode. Monocraft is used, as it was simple to implement by rendering each pixel separately. In the future we definitely don't want to do it this way, we should optimally read the font file and render it based on that, but before that, I'd like to have a filesystem driver, and load some sort of init binary (and setup a scheduler)
TODO