[driver] Optionally place direct floppy driver in far text segment #1727
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
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.
When the kernel is compiled with the BIOS, DF, SSD and RD block drivers, networking and all trace and system checks included, the near text segment checks in at 64336 bytes, too close to the 65535 byte max.
This PR moves the DF driver (and DMA code) into the far text segment when CONFIG_FARTEXT_KERNEL is set, which opens up about 3k bytes in the near text segment. Calling code between segments isn't free though, and the net total increase in kernel RAM size is plus ~400 bytes.
Considering doing the same for the SSD and RD drivers, and possibly BIOS.