Closed mkszuba closed 1 year ago
Unless I have missed something, declaring this at build time is the only way of having u-boot support device-tree overlays when distro boot is in use. Would be nice to have this included officially... For what it's worth, what I did on my end (i.e. with self-compiled u-boot on a BeagleV Starlight beta board) was, in include/configs/starfive-jh7100.h, bump
ramdisk_addr_r
to 0x88400000 and setfdtoverlay_addr_r
to 0x88300000 - and it seems to work fine.
Hi @mkszuba , Great thanks for your info , we have moved ramdisk_addr_r to the uEnv.txt file in /boot/ of 'boot' partition, you can find this file in our latest image, so if you need this fdtoverlay_addr_r
, we should set it up in our image but not u-boot.
We will test: ramdisk_addr_r=0x88400000 fdtoverlay_addr_r=0x88300000 if this works well, we will put it into the uEnv.txt file of our image
We will test: ramdisk_addr_r=0x88400000 fdtoverlay_addr_r=0x88300000 if this works well, we will put it into the uEnv.txt file of our image
@mkszuba I have tried it , but since we are using grub to boot linux. we don't need those variables , and also can boot Fedora. So we can add
ramdisk_addr_r=0x88400000
fdtoverlay_addr_r=0x88300000
if you really need it . and I would like to know how you use it, since I never use it before .
IMO it still makes sense to set this in the default U-Boot environment. It does not hurt even if it remains unused. It is about making this U-Boot build as compatible as possible, and for extlinux
, it is the required standard for making use of the fdtoverlays
directive.
PR up to add it for the VisionFive 2: #44
The variable is btw listed as "required" in upstream U-Boot docs, so to comply is another argument to add it: https://github.com/u-boot/u-boot/blob/master/doc/develop/distro.rst#required-environment-variables
@MichaelZhuxx thanks for the merges for VisionFive V2!
I believe this should still be re-opened as it remains an issue on the VisionFive V1 (which it was originally reported against)? #31 (and seems also #32) exists to address it afaik
Unless I have missed something, declaring this at build time is the only way of having u-boot support device-tree overlays when distro boot is in use. Would be nice to have this included officially... For what it's worth, what I did on my end (i.e. with self-compiled u-boot on a BeagleV Starlight beta board) was, in include/configs/starfive-jh7100.h, bump
ramdisk_addr_r
to 0x88400000 and setfdtoverlay_addr_r
to 0x88300000 - and it seems to work fine.