-
Notifications
You must be signed in to change notification settings - Fork 35
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
fix the EFI path #3
Comments
See the UEFI 2.9 specification 3.5.1.1:
The fedora patches should be dropped. For example fe93fbc 8a6805d and others which are for different architectures/socs entirely. A binary image with these reverted along with instructions would be helpful. It also isn't clear which repository should be used. Which combination of repositories and branches were used to build the image that shipped in the spi flash of the beta boards? There is only one repository for the earlier stages |
https://wiki.seeedstudio.com/BeagleV-Make-File-System-Compile-uboot-Kernal/ uses the Fedora branches of https://github.com/starfive-tech/beagle_opensbi and https://github.com/starfive-tech/beagle_uboot-opensbi with manual offset changes and the result is run through https://github.com/starfive-tech/freelight-u-sdk/blob/starfive/fsz.sh |
@jonathangray sorry for the confusion about the repositories. Wei Fu (@tekkamanninja) is actively cleaning this up so that there will be just a single repo each for opensbi, uboot and Linux. I will make it widely known once @tekkamanninja has finished that cleanup. For the BeagleV beta developers, I have apost about this in the beaglev-beta forum: For BeagleV beta developers that can not access that URL please email me: drew@beagleboard.org |
@tekkamanninja tells me that this will be resolved once we get u-boot executing grub which is the eventual solution needed for Fedora. We also plan in the future to try EDK2 UEFI as well. |
Since today , we have got u-boot executing grub to boot Fedora, so let me try to explain this : for scan_dev_for_efi, we do not use this for efi file. for other distro image , we can also execute efi/boot/bootriscv64.efi by modify uEnv.txt for their own Image |
Reviving this thread since we're now adding support for the VisionFive board to OpenBSD. Customizing images using uEnv.txt doesn't make any sense; the whole point of UEFI is that it allows to boot generic OS images. As a project we simply can't provide separate customized images for each and every board that hits the market. So we only provide a single generic OS image. And I suspect some of the Linux distributions are in the same boat. While I do think that there should be no need for uEnv.txt, it should be possible to retain this feature, but simply fall back on the default distroboot boot command if no uEnv.txt file is found. I can probably help with the necessary changes in u-boot. |
The same for Haiku. |
I would like to see this glitch fixed, too. Thanks. |
Theo de Raadt from OpenBSD contacted me:
The text was updated successfully, but these errors were encountered: