Page MenuHomeFreeBSD

Fixes and updates to Zynq u-boot ports
AbandonedPublic

Authored by skibo on Oct 16 2019, 5:42 PM.
Tags
None
Referenced Files
Unknown Object (File)
Nov 30 2024, 6:33 PM
Unknown Object (File)
Nov 26 2024, 8:29 AM
Unknown Object (File)
Nov 11 2024, 9:35 AM
Unknown Object (File)
Oct 19 2024, 10:51 PM
Unknown Object (File)
Oct 8 2024, 4:37 PM
Unknown Object (File)
Oct 2 2024, 9:54 AM
Unknown Object (File)
Sep 25 2024, 2:52 AM
Unknown Object (File)
Sep 18 2024, 6:37 PM

Details

Reviewers
manu
Summary

Fix build breakage in recent u-boot releases. Update uEnv.txt files. Fix package description of u-boot-zybo.

Test Plan

Tested on Zybo.

Diff Detail

Repository
rP FreeBSD ports repository
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

manu added inline comments.
sysutils/u-boot-zedboard/files/uEnv.txt
0

I'm pretty sure that uEnv.txt isn't parsed anymore, if that is the case we should just drop it.

sysutils/u-boot-zedboard/files/uEnv.txt
0

It won't boot without this so it is parsed. Looks like this is board-specific (see include/configs/zynq-common.h).
But, I had the idea that there might be a default filename for the dtb like system.dtb and maybe I can get rid of this. I'll check into this...

sysutils/u-boot-zedboard/files/uEnv.txt
0

There is a default dtb filename. It's "zynq-zynq.dtb" in Zybo's case (weird) so I don't need uEnv.txt. Also, the script I use to make an image generates uEnv.txt anyway so it doesn't need to be here. I'll upload a diff without uEnv.txt and adjust the Makefile so it's not installed.

Also, u-boot-master/Makefile creates a boot.scr for all arm boards but the zynq boards ignore it and don't need it. Should we come up with an exception for zynq boards?

This diff is no longer valid because the Zynq u-boot ports have been removed.

This is pity that this patch get abandoned. If this patch fixes the issue, we can certainly readd these ports. @skibo and @manu , are you still interested in checking this?

This is pity that this patch get abandoned. If this patch fixes the issue, we can certainly readd these ports. @skibo and @manu , are you still interested in checking this?

I don't mind adding those ports again if they work, Milan Obuch on u-boot@ said that the zybo ports needs a patch. I want this patch submitted properly upstream before doing anything here as I don't want to maintain patch in the ports tree for u-boot (especially when I don't have the hardware).

I'll look into submitting the fix to u-boot but it won't appear until 2020.04.

I'll look into submitting the fix to u-boot but it won't appear until 2020.04.

Maybe even later, but I'm fine with local patch if they are submitted upstream, see the discussion I had with Milan about this.