mips: Move MIPS boards into their own files #14472
Merged
Conversation
This file contains hidden or 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
Since the I2000 (Rx2030) and R3030 (Rx3230) boards are so different, they really belong in their own files. I've kept the original mips.cpp file for common functions. There doesn't seem to be enough commonality at this time to make a common base class worthwhile, perhaps as more boards are implemented some will be found.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Since the I2000 (Rx2030) and R3030 (Rx3230) boards are so different, they really belong in their own files. I've kept the original mips.cpp file for common functions.
There doesn't seem to be enough commonality at this time to make a common base class worthwhile, perhaps as more boards are implemented some will be found.