Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Future: Be more flexible with MMC SPL code on future devices. #55

Open
kallisti5 opened this issue Dec 5, 2023 · 0 comments
Open

Future: Be more flexible with MMC SPL code on future devices. #55

kallisti5 opened this issue Dec 5, 2023 · 0 comments

Comments

@kallisti5
Copy link

kallisti5 commented Dec 5, 2023

I'm writing this as an OS developer who wants to see riscv64 succeed.
Please, please be consistent with early startup processes.

Here i'm comparing the SiFive Unmatched's MMC format to the MMC of the StarFive Vision2:

u-boot

The VisionFive 2 is on the left, the Unmatched is on the right. The boards are very similar, minus a few differences:

  • The SiFive Unmatched has a dedicated GPT partition UUID for the SPL + u-boot
  • The VisionFive has an "FFFF" GPT partition UUID for the SPL + u-boot.

Looking at the JH7110 developer guide, the SPL partition offset is assumed at a fixed offset of 4096 which clashes with the Unmatched.

In future revisions of the BootROM, please allow the dynamic discovery of the MMC SPL by examining the partition table and looking for the offset of a dedicated GPT UUID. (maybe fallback to a fixed address if a valid GPT partition isn't found)

bootrom

@kallisti5 kallisti5 changed the title Be consistant with u-boot loaders on mmc devices Future: Be more flexible with MMC SPL code on future devices. Dec 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant