Tartarus changed the topic of #u-boot to: SOURCE MOVED TO https://source.denx.de/u-boot/u-boot.git / U-Boot v2024.01 is OUT / Merge Window is OPEN, next branch is CLOSED / Release v2024.04 is scheduled for 02 April 2024 / Channel archives at https://libera.irclog.whitequark.org/u-boot
ikarso has quit [Quit: Connection closed for inactivity]
l0rd_hex has joined #u-boot
<l0rd_hex> Hello everyone, this is a bit of a strange question but can I start another instance of u-boot from u-boot? like tftp a copy and them loadm/go?
KREYREN has quit [Remote host closed the connection]
KREYREN has joined #u-boot
KREYREN has quit [Remote host closed the connection]
KREYREN has joined #u-boot
persmule has quit [Ping timeout: 240 seconds]
persmule has joined #u-boot
matthias_bgg has quit [Ping timeout: 260 seconds]
matthias_bgg has joined #u-boot
joeskb7 has quit [Quit: leaving]
mmu_man has quit [Ping timeout: 264 seconds]
qqq has quit [Remote host closed the connection]
<Forty-Bot> l0rd_hex: yes; in fact that's exactly what SPL does
jclsn has quit [Ping timeout: 255 seconds]
jclsn has joined #u-boot
Peng_Fan has joined #u-boot
persmule has quit [Ping timeout: 240 seconds]
persmule has joined #u-boot
pbsds has quit [Quit: The Lounge - https://thelounge.chat]
persmule has quit [Remote host closed the connection]
pbsds has joined #u-boot
persmule has joined #u-boot
persmule has quit [Remote host closed the connection]
Stat_headcrabed has joined #u-boot
Clamor has joined #u-boot
Stat_headcrabed has quit [Quit: Stat_headcrabed]
gsz has joined #u-boot
jybz has quit [Excess Flood]
jybz has joined #u-boot
IoT-Maker has joined #u-boot
<IoT-Maker> how can i use bubt or membubt properly? If i load a u-boot binary to memory (doesn't matter if i set the cpu in arm or thumb mode) the device failed to start.
<IoT-Maker> If i read out the cmos flash ic after using membubt, the data is different to the data i loaded into memory to burn it on the cmos flash.
camus has joined #u-boot
goliath has quit [Quit: SIGSEGV]
mmu_man has joined #u-boot
dsimic has quit [Ping timeout: 260 seconds]
dsimic has joined #u-boot
goliath has joined #u-boot
ladis has joined #u-boot
IoT-Maker has quit [Quit: Leaving]
ladis has quit [Quit: Leaving]
slobodan_ has joined #u-boot
stefanro has joined #u-boot
persmule has joined #u-boot
persmule has quit [Remote host closed the connection]
persmule has joined #u-boot
persmule has quit [Remote host closed the connection]
persmule has joined #u-boot
Clamor has quit [Ping timeout: 252 seconds]
Clamor has joined #u-boot
Leopold has quit [Ping timeout: 268 seconds]
Leopold has joined #u-boot
gsz has quit [Ping timeout: 256 seconds]
ladis has joined #u-boot
mmu_man has quit [Ping timeout: 256 seconds]
mmu_man has joined #u-boot
Clamor has quit [Ping timeout: 260 seconds]
Clamor has joined #u-boot
Clamor has quit [Read error: Connection reset by peer]
Clamor has joined #u-boot
jkm has joined #u-boot
<jkm> Hello everyone, what is the status of U-Boot ARM64 (aarch64) on EFI? Is there a specific config for that? How can I help testing?
<Tartarus> as an efi payload, or executing efi payloads?
<jkm> The first one.
<jkm> Generic BOOTAA64.EFI for ARM64
<jkm> Something similar that grub-efi provides.
<jkm> I have a few ARM64 UEFI devices and could help testing if there is progress in this area.
<marex> xypron: ^
qqq has joined #u-boot
<Tartarus> Yeah, I think the answer is that efi-x86* _should_ be directly rebuildable to aarch64, but has not been done
<Tartarus> There shouldn't be anything inherently x86-centric about them
<jkm> I wouldn't assume that it will be as simple as that...
<jkm> But anyway, I'll try.
Clamor has quit [Read error: Connection reset by peer]
Clamor has joined #u-boot
<jkm> I guess that CONFIG_SYS_CPU="armv8" somewhat implies CONFIG_SYS_SOC...
jan_V2 has quit [Quit: Ping timeout (120 seconds)]
jan_V2 has joined #u-boot
<Tartarus> Taking a look at the qemu boards might be helpful too, to make up an efi-arm64_app_defconfig or so, and whatever Kconfig entries are needed too
mmu_man has quit [Ping timeout: 268 seconds]
goliath has quit [Quit: SIGSEGV]
mmu_man has joined #u-boot
jan_V2 has quit [Quit: Ping timeout (120 seconds)]
jan_V2 has joined #u-boot
<jkm> Unfortunately I couldn't make it :(
<jkm> If someone makes it happen, I will be more than happy to test it.
persmule has quit [Remote host closed the connection]
persmule has joined #u-boot
persmule has quit [Remote host closed the connection]
persmule has joined #u-boot
persmule has quit [Remote host closed the connection]
persmule has joined #u-boot
KREYREN has quit [Remote host closed the connection]
KREYREN has joined #u-boot
KREYREN has quit [Remote host closed the connection]
KREYREN has joined #u-boot
KREYREN has quit [Remote host closed the connection]
KREYREN has joined #u-boot
ladis has quit [Quit: Leaving]
KREYREN has quit [Remote host closed the connection]
Clamor has quit [Ping timeout: 256 seconds]
Clamor has joined #u-boot
jkm has quit [Quit: Ping timeout (120 seconds)]
jkm has joined #u-boot
KREYREN has joined #u-boot
Clamor has quit [Read error: Connection reset by peer]
KREYREN has quit [Remote host closed the connection]
KREYREN has joined #u-boot
jkm has quit [Quit: Client closed]
KREYREN_ has joined #u-boot
KREYREN has quit [Remote host closed the connection]
KREYREN_ has quit [Remote host closed the connection]
KREYREN_ has joined #u-boot
KREYREN_ has quit [Remote host closed the connection]
KREYREN_ has joined #u-boot
gsz has joined #u-boot
KREYREN__ has joined #u-boot
KREYREN__ has quit [Remote host closed the connection]
KREYREN__ has joined #u-boot
KREYREN_ has quit [Ping timeout: 240 seconds]
KREYREN__ has quit [Remote host closed the connection]
KREYREN__ has joined #u-boot
KREYREN__ has quit [Remote host closed the connection]
persmule has quit [Ping timeout: 240 seconds]
gsz has quit [Ping timeout: 256 seconds]
persmule has joined #u-boot
KREYREN has joined #u-boot
matthias_bgg has quit [Ping timeout: 256 seconds]
matthias_bgg has joined #u-boot