<kallisti5>
that u-boot.bin is qemu-riscv64_smode_defconfig
<kallisti5>
locking up as in qemu hangs + crashes
<kallisti5>
nevermind. no u-boot.itb on the qemu-riscv64_smode_defconfig config
<kallisti5>
^ ignore. Thought I was supposed to be using u-boot.itb, but that's only for qemu-riscv64_spl_defconfig. qemu-riscv64_smode_defconfig is the only thing that even boots for me
tre has quit [Quit: Leaving]
macromorgan has joined #u-boot
Sout_ has quit [Ping timeout: 252 seconds]
Sout_ has joined #u-boot
Sout_ has joined #u-boot
Sout_ has quit [Changing host]
sszy has quit [Ping timeout: 268 seconds]
<xypron>
milkylainen: you told you wanted to load a file from a block device. This is not supported by the U-Boot with CONFIG_EFI_APP=y yet. You would have develop a block device driver consuming the EFI_BLOCK_IO_PROTOCOL.
<xypron>
milkylainen_
fdanis is now known as fdanis_away
redbrain has joined #u-boot
<milkylainen_>
xypron: I am running U-boot as an EFI_PAYLOAD. Does that mean that EFI services are disabled?
maxs has joined #u-boot
akaWolf has quit [Ping timeout: 268 seconds]
akaWolf has joined #u-boot
maxs has quit [Ping timeout: 246 seconds]
jwillikers has quit [Remote host closed the connection]
maxs has joined #u-boot
gsz has quit [Quit: leaving]
blmaier_ has quit [Quit: ZNC 1.7.5+deb4 - https://znc.in]
blmaier has joined #u-boot
maxs has quit [Ping timeout: 246 seconds]
jwillikers has joined #u-boot
redbrain has quit [Ping timeout: 268 seconds]
milkylainen_ has quit [Ping timeout: 252 seconds]
milkylainen has quit [Ping timeout: 268 seconds]
milkylainen_ has joined #u-boot
maxs has joined #u-boot
alpernebbi has quit [Quit: alpernebbi]
jwillikers has quit [Quit: jwillikers]
jwillikers has joined #u-boot
jwillikers has quit [Remote host closed the connection]
birkoff has quit [Ping timeout: 248 seconds]
<sjg1>
milkylainen_: I would say it is likely. Check CONFIG_EFI_LOADER
<sjg1>
It is a long time since I have fiddled with distroboot. Does anyone know a suitable distribution that uses it (with a U-Boot board)? Perhaps something on rpi3?
<sjg1>
Tartarus: ^
<Tartarus>
sjg1: arm32 or 64?
<Tartarus>
fedora covers both I believe, out of the box
<Tartarus>
and i think that's what I went with for arm64 as well locally
<sjg1>
Tartarus: OK ta, I was thinking arm32 rpi3 - so fedora should work with that OK?
agust has quit [Quit: Leaving.]
cottsay has quit [Quit: TTFN]
cottsay has joined #u-boot
<Tartarus>
sjg1: To be clearer, fedora will get you the EFI path of distro boot, on arm32
<Tartarus>
Debian will get you I think the boot.scr path
<Tartarus>
(I forget, and it's on my mx6cuboxi, which isn't easy to automate)
<Tartarus>
OpenEmbedded will get you the extlinux.conf path on arm32, if you enable the right flags (not everything does that out of the box)
<Tartarus>
For 64bit, OE will also with the right config, give you EFI, and fedora is EFI out of the box