| 12 Jul 2023 |
 Alex | This isn't a problem on the vendor's Debian, because the devel branch of the kernel has a different partition table. | 17:41:27 |
| Alex | Can you describe what needs to be done to boot from SD?
I might be able to make the change. | 17:41:51 |
 Pratham Patel | Just a sec | 17:42:10 |
| Pratham Patel | I use this partition layout for the first two partitions
https://github.com/thefossguy/archlinux-visionfive2/blob/master/create-image.sh#L85 | 17:42:46 |
| Pratham Patel | Then, you dd u-boot-spl.bin.normal.out to part1 and visionfive2_fw_payload.img to part2 | 17:44:13 |
| Alex | So 4 partitions:
- SPL (u-boot metadata)
- u-boot (flat binary)
- boot (FAT)
- root
Makes sense. | 17:44:29 |
| Pratham Patel | So instead of reading firmware from flash, the firmware is entirely read from the SD card ;) | 17:44:31 |
| Pratham Patel | In reply to @alex:tunstall.xyz
So 4 partitions:
- SPL (u-boot metadata)
- u-boot (flat binary)
- boot (FAT)
- root
Makes sense. Exactly! | 17:44:44 |
| Pratham Patel | But be vary of the sectors where the partions start and end | 17:44:56 |
| Pratham Patel | There's a reason why my script starts the first partition at 4096 ;) | 17:45:19 |
| Alex | Oh does the bootloader expect the partitions to be at specific offsets? | 17:45:20 |
| Pratham Patel | Yes :) | 17:45:48 |
| Pratham Patel | But that's the ZSBL so it won't ever change | 17:46:03 |
