introduce support for the SolidRun clearfog #250
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
Artox
force-pushed
the
pr-clearfog
branch
3 times, most recently
from
076f16c to
4d2d216
Compare
Signed-off-by: Josua Mayer <[email protected]>
Initial support for the SolidRun Clearfog laned in FreeBSD with r319914. The board has acceptable support in mainline U-Boot, as well as a vendor fork based on 2018.01. For now an MBR partition table is used, with a fat partition to load DTB and ubldr from, reserved space covering the first 1M of the disk to make sure installing u-boot later doesn't destroy the boot partition. Signed-off-by: Josua Mayer <[email protected]>
The Helios-4 uses the same SoM as the Clearfog and can share all of the clearfog specific configuration. The DTB has been copied from the Helios-4 linux fork on github.com: https://github.com/helios-4/linux-marvell/blob/linux-marvell-4.4/arch/arm/boot/dts/armada-388-helios4.dts Signed-off-by: Josua Mayer <[email protected]>
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.
Initial support for the SolidRun Clearfog laned in FreeBSD with r319914.
The board has acceptable support in mainline U-Boot, as well as a
vendor fork based on 2018.01.
For now an MBR partition table is used, with a fat partition to load
DTB and ubldr from, reserved space covering the first 1M of the disk
to make sure installing u-boot later doesn't destroy the boot partition.
Note: this currently depends on issue #249
This is a first draft, let me know what you think, and if some things can be done differently.
Especially the reserved partition looks very hacky. My point was to reserve exactly the space that U-Boot may use. The vendor u-boot is configured to store the environment right before 1M into the block device that it is running from. So I made a partition that starts as early as possible, and spans up to sector 2047.
Maybe there could be a helper function for such task? Or, considering that nobody uses the disk_reserved_create function, maybe it could made to not align?