Tartarus changed the topic of #u-boot to: SOURCE MOVED TO https://source.denx.de/u-boot/u-boot.git / U-Boot v2021.10 is OUT / Merge Window is OPEN until 25 October 2021 / Release v2022.01 is scheduled for 10 January 2022 / http://www.denx.de/wiki/U-Boot / Channel archives at https://libera.irclog.whitequark.org/u-boot
<qsx> samueldr: https://bpa.st/RPRA
<samueldr> thanks [qsx](https://matrix.to/#/@qsx:libera.chat), matches *exactly* with my observations on other boards
<qsx> (i think the MMC2 SPL wants to boot from at first is the wifi sdio, lol)
<samueldr> nah, naming is weird, and differs at that stage
<qsx> btw, the inno-usb2 issue does not appear when i boot linux using EFI
<samueldr> if you have a more specific use case, e.g. using USB Mass Storage with RK3399, removing the op here will help:
<samueldr> that's because the UMS bits in U-Boot will exercise that function which otherwise doesn't
<samueldr> I suspect it's possible you need to provide a "good enough" dtb for Linux that U-Boot can load
<qsx> well the dtb uboot uses is the one from linux, plus uboot additions linux doesn’t care about
<samueldr> with EFI boot, U-Boot will look, at the root of the ESP, in those folders for the dtb to load:
<samueldr> it's possible it's not been synced for a while [unfounded guess]
<qsx> if there is none, uboot will provide the one it used itself, which works fine
<samueldr> I know that usually you'd want to use the exact dtb file built with the kernel you intend to boot on ARM, because of... reasons...
<qsx> in fact i examined rk3399.dtsi, rk3399-opp.dtsi, and rk3399-rockpro64* this afternoon, and the updates that have not propagated so far are irrelevant for me (some cosmetic naming, some hardware i don’t use)
<samueldr> (I won't go into details here as it's not the right venue, but while it's stated it should work, too often things are "fixed" in the device tree, which means an older device tree won't correctly work)
<qsx> yes i had that kind of fun with the vendor linux 4.4 vs. mainline linux 5.10
<samueldr> right, I was thinking solely about mainline :)
* qsx misses the old days where OpenFirmware on a sun or a powermac just provided _the_ device tree
<samueldr> anyway, I can't exactly help, so I won't try much more to guess
<qsx> yeah backporting that fix already did it -- <qsx> nevermind, the solution is already there: https://lore.kernel.org/u-boot/20211101044347.17822-1-yifeng.zhao@rock-chips.com/
<samueldr> yeah, that I agree with: if the kernel is to decide what is the "correct" overview of the hardware, it should somehow handle loading the "correct" dtb file itself *grumbles and groans*
jwillikers has quit [Read error: Connection reset by peer]
jwillikers has joined #u-boot
camus has quit [Remote host closed the connection]
camus has joined #u-boot
jwillikers has quit [Read error: Connection reset by peer]
jwillikers has joined #u-boot
jwillikers has quit [Remote host closed the connection]
sdfgsdfg has quit [Quit: ZzzZ]
vagrantc has quit [Quit: leaving]
samekh has joined #u-boot
samekh_ has quit [Ping timeout: 256 seconds]
thopiekar has quit [Ping timeout: 240 seconds]
thopiekar has joined #u-boot
alchemist_ has joined #u-boot
mmu_man has quit [Ping timeout: 245 seconds]
alchemist has quit [Ping timeout: 240 seconds]
thopiekar has quit [Ping timeout: 260 seconds]
thopiekar has joined #u-boot
sdfgsdfg has joined #u-boot
camus has quit [Ping timeout: 268 seconds]
camus has joined #u-boot
sdfgsdfg has quit [Quit: ZzzZ]
sdfgsdfg has joined #u-boot
michalkotyla_ has quit [Ping timeout: 240 seconds]
rfs613 has quit [Ping timeout: 240 seconds]
rfs613 has joined #u-boot
sdfgsdfg has quit [Quit: ZzzZ]
camus has quit [Ping timeout: 240 seconds]
camus has joined #u-boot
sdfgsdfg has joined #u-boot
sdfgsdfg has quit [Quit: ZzzZ]
SallyAhaj has joined #u-boot
camus1 has joined #u-boot
camus has quit [Ping timeout: 268 seconds]
camus1 is now known as camus
agust has joined #u-boot
redbrain has joined #u-boot
camus has quit [Ping timeout: 268 seconds]
camus has joined #u-boot
mmu_man has joined #u-boot
redbrain has quit [Ping timeout: 240 seconds]
thopiekar has quit [Ping timeout: 240 seconds]
thopiekar has joined #u-boot
sdfgsdfg has joined #u-boot
alchemist_ has quit [Read error: Connection reset by peer]
redbrain has joined #u-boot
jwillikers has joined #u-boot
alchemist has joined #u-boot
sdfgsdfg has quit [Quit: ZzzZ]
alchemist has quit [Remote host closed the connection]
alchemist has joined #u-boot
alchemist has quit [Ping timeout: 240 seconds]
alchemist has joined #u-boot
jwillikers has quit [Remote host closed the connection]
redbrain has quit [Ping timeout: 240 seconds]
thopiekar has quit [Ping timeout: 260 seconds]
thopiekar has joined #u-boot
stefanro has quit [Ping timeout: 240 seconds]
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #u-boot
stefanro has joined #u-boot
redbrain has joined #u-boot
mmu_man has quit [Ping timeout: 268 seconds]
<rfried> Tartarus, sjg1: We're not going to support non DM drivers any longer right, so there's no reason to accept #ifndef DM_ETH statement. am I right ?
redbrain has quit [Ping timeout: 250 seconds]
<Tartarus> rfried: SPL/TPL aren't in that category, and SPL+networking is a valid combination
mmu_man has joined #u-boot
taliho has quit [Read error: Connection reset by peer]
taliho has joined #u-boot
mmu_man has quit [Ping timeout: 250 seconds]
redbrain has joined #u-boot
Gravis has quit [Ping timeout: 256 seconds]
sdfgsdfg has joined #u-boot
Gravis has joined #u-boot
mmu_man has joined #u-boot
redbrain has quit [Ping timeout: 256 seconds]
mmu_man has quit [Ping timeout: 245 seconds]
mmu_man has joined #u-boot
vagrantc has joined #u-boot
sdfgsdfg has quit [Quit: ZzzZ]