rburkholder has quit [Remote host closed the connection]
jclsn0 has quit [Ping timeout: 276 seconds]
rburkholder has joined #u-boot
mmu_man has quit [Ping timeout: 248 seconds]
jclsn0 has joined #u-boot
jclsn0 has quit [Ping timeout: 240 seconds]
jclsn0 has joined #u-boot
jclsn0 has quit [Ping timeout: 240 seconds]
littlebobeep has quit [Ping timeout: 240 seconds]
jclsn0 has joined #u-boot
jclsn0 has quit [Ping timeout: 248 seconds]
jclsn0 has joined #u-boot
jclsn0 has quit [Ping timeout: 240 seconds]
jclsn0 has joined #u-boot
jclsn0 has quit [Ping timeout: 240 seconds]
littlebobeep has joined #u-boot
jclsn0 has joined #u-boot
jclsn0 has quit [Ping timeout: 256 seconds]
jclsn0 has joined #u-boot
jclsn0 has quit [Ping timeout: 252 seconds]
jclsn0 has joined #u-boot
jclsn0 has quit [Ping timeout: 252 seconds]
thopiekar has quit [Ping timeout: 276 seconds]
thopiekar has joined #u-boot
jclsn0 has joined #u-boot
littlebobeep has quit [Ping timeout: 240 seconds]
littlebobeep has joined #u-boot
jclsn0 has quit [Ping timeout: 256 seconds]
littlebo1eep has joined #u-boot
littlebobeep has quit [Ping timeout: 240 seconds]
jclsn0 has joined #u-boot
jclsn0 has quit [Ping timeout: 256 seconds]
jclsn0 has joined #u-boot
jclsn0 has quit [Ping timeout: 256 seconds]
jclsn0 has joined #u-boot
jclsn0 has quit [Ping timeout: 240 seconds]
jclsn0 has joined #u-boot
jclsn0 has quit [Ping timeout: 240 seconds]
jclsn0 has joined #u-boot
littlebo1eep has quit [Ping timeout: 240 seconds]
littlebobeep has joined #u-boot
littlebobeep has quit [Ping timeout: 240 seconds]
littlebo1eep has joined #u-boot
littlebo1eep has quit [Ping timeout: 240 seconds]
littlebobeep has joined #u-boot
littlebobeep has quit [Ping timeout: 240 seconds]
littlebobeep has joined #u-boot
littlebo1eep has joined #u-boot
littlebobeep has quit [Ping timeout: 240 seconds]
littlebobeep has joined #u-boot
littlebo1eep has quit [Ping timeout: 240 seconds]
littlebobeep has quit [Ping timeout: 240 seconds]
littlebobeep has joined #u-boot
littlebobeep has quit [Ping timeout: 240 seconds]
cambrian_invader has quit [Ping timeout: 260 seconds]
littlebobeep has joined #u-boot
vagrantc has quit [Quit: leaving]
cambrian_invader has joined #u-boot
apritzel has joined #u-boot
guillaume_g has joined #u-boot
apritzel has quit [Ping timeout: 276 seconds]
swiftgeek has quit [Read error: Connection reset by peer]
frieder has joined #u-boot
littlebobeep has quit [Ping timeout: 240 seconds]
littlebobeep has joined #u-boot
sszy has joined #u-boot
littlebobeep has quit [Ping timeout: 240 seconds]
swiftgeek has joined #u-boot
littlebobeep has joined #u-boot
littlebobeep has quit [Ping timeout: 240 seconds]
littlebobeep has joined #u-boot
littlebo1eep has joined #u-boot
littlebobeep has quit [Ping timeout: 240 seconds]
littlebobeep has joined #u-boot
littlebo1eep has quit [Ping timeout: 240 seconds]
littlebobeep has quit [Ping timeout: 240 seconds]
littlebo1eep has joined #u-boot
monstr has joined #u-boot
tnovotny has joined #u-boot
jelle has joined #u-boot
sstiller has joined #u-boot
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #u-boot
ldevulder has quit [Quit: Leaving]
<jelle>
does anyone know how to develop on fedora's u-boot on the rpi? I've build uboot-images-armv8 but replacing the rpi3-u-boot.bin with /usr/share/uboot/rpi_3/u-boot.bin did not lead to a succesful boot so I'm wondering if I'm missing something
<jelle>
I also rather build from u-boot.git
<fALSO>
dont know how the boot sequence works on the rpi, but normally (at least on the boards i have, the u-boot resulting file needs to be flashed to a specific place on the card)
<fALSO>
dont know if the in rpi you just put it somewhere ;-P
<jelle>
that's not the case on the RPI
<fALSO>
ahhh OK
<fALSO>
=)
<jelle>
allwinner is easier in that regard yes :)
<fALSO>
i've just played with orange pi's and rockpr64
<jelle>
as far as I understand the broadcom bootloader loads u-boot which sets up an EFI env
<jelle>
well hmm it did start, just did not boot, should figure out the error message. I'm now wondering it trusted firmware
<jelle>
fALSO: mps ok this is fun, my own cross compiled u-boot seems to work \o/
zibolo has joined #u-boot
ldevulder has joined #u-boot
gsz has joined #u-boot
sstiller has quit [Quit: Leaving]
mmu_man has joined #u-boot
<hanetzer>
so, under most normal circumstances, every patch/commit should at least be compilable individually, but what about during soc bringup?
<fALSO>
jelle, =)))))
littlebo1eep has quit [Ping timeout: 240 seconds]
littlebobeep has joined #u-boot
tnovotny has quit [Remote host closed the connection]
prabhakarlad has quit [Quit: Client closed]
<rfs613>
hanetzer: git bisect doesn't know about soc bringup, so you still want to ensure it builds with each successive commit. Your soc may not boot or function, but the rest of the code should not be affected.
<rfs613>
at least that's my $0.02... I am not a maintainer and I can't speak for them ;-)
<Tartarus>
monstr: Oh "fun". Yeah, I have no idea and I would hope / assume someone from Linaro or Arm would be posting something.
<hanetzer>
rfs613: blerg. because I can't build soc without a board file and whatnot.
<j`ey>
hanetzer: can't you introduce a board file first, that builds, but doesnt work, and then add the drivers / config etc
<hanetzer>
and that needs a dts, and those need clock bindings things, and whatnot.
<hanetzer>
because I have a whole new arch/arm/mach-hisilicion tree lmao
<monstr>
Tartarus: we got that request and I also don't want to spend any time on it because that's something what ARM should be fixing.
<monstr>
also that upstream discussion is not over. We added the flag for compilation to TF-A which was accepted by ARM but not sure if make sense to pass -mharden-sls=all compilation flag to all arm64 based platforms
<monstr>
What should be the right way to go? I mean can you bring this up with ARM/Linaro guys to get any feedback on this?
<monstr>
apalos-: Any opinion about it?
<hanetzer>
screw it.
<Tartarus>
monstr: First I'm hearing of the issue even
<Tartarus>
apritzel: ping :)
<apalos->
monstr: I just saw that, need to go and read that thread
apalos- is now known as apalos
tom42 has quit [Write error: Connection reset by peer]
ddevault has quit [Remote host closed the connection]
ddevault has joined #u-boot
tom42 has joined #u-boot
hanetzer has quit [Ping timeout: 256 seconds]
hanetzer has joined #u-boot
littlebobeep has quit [Remote host closed the connection]
littlebobeep has joined #u-boot
<rfs613>
when using DM during early boot (before reloc), how does probe ordering work? In the pre-DM method, the board.c file would make direct calls in a specific order. Trying to wrap my head around how this is supposed to work under DM.
<rfs613>
i'm specifically thinking of things like clock, pinmux, and DDR initialization
<cambrian_invader>
stuff like clk_get_by_name() will probe the clock driver if it hasn't been probed already