sdfgsdfgDropBear has quit [Quit: sdfgsdfgDropBear]
zibolo has quit [Ping timeout: 252 seconds]
zibolo has joined #u-boot
sdfgsdfgDropBear has joined #u-boot
sakman has joined #u-boot
vagrantc has quit [Ping timeout: 252 seconds]
sdfgsdfgDropBear has quit [Quit: sdfgsdfgDropBear]
jwillikers has quit [Remote host closed the connection]
sdfgsdfgDropBear has joined #u-boot
vagrantc has joined #u-boot
Rusty_Almighty has quit [Ping timeout: 245 seconds]
Rusty_Almighty has joined #u-boot
mmu_man has quit [Ping timeout: 250 seconds]
sdfgsdfgDropBear has quit [Quit: sdfgsdfgDropBear]
cambrian_invader has quit [Ping timeout: 246 seconds]
sdfgsdfgDropBear has joined #u-boot
sdfgsdfgDropBear has quit [Quit: sdfgsdfgDropBear]
cambrian_invader has joined #u-boot
sdfgsdfgDropBear has joined #u-boot
sdfgsdfgDropBear has quit [Client Quit]
fdanis_away is now known as fdanis
guillaume_g has joined #u-boot
frieder has joined #u-boot
sszy has joined #u-boot
vagrantc has quit [Quit: leaving]
mckoan|away is now known as mckoan
agust has joined #u-boot
<mwalle>
sjg1: mh, but that has the same problem, i need to access the hardware to decide which one should be bound, which isn't allowed in the bind methods, right?
sdfgsdfgDropBear has joined #u-boot
gsz has joined #u-boot
matthias_bgg has joined #u-boot
sdfgsdfgDropBear has quit [Quit: sdfgsdfgDropBear]
sakman_ has joined #u-boot
sakman has quit [Remote host closed the connection]
milkylainen has quit [Quit: Ping timeout (120 seconds)]
milkylainen_ has quit [Quit: Ping timeout (120 seconds)]
milkylainen has joined #u-boot
<milkylainen>
sjg1: Sorry about lack of feedback on U-boot and UEFI services. I think I got a window to test your work now.
<marex>
mrnuke: what ?
<marex>
=> mtd help
<marex>
data abort
<marex>
pc : [<3ff73a9a>] lr : [<3ff685d1>]
<marex>
damn
swiftgeek has quit [Ping timeout: 252 seconds]
milkylainen has quit [Quit: Ping timeout (120 seconds)]
milkylainen has joined #u-boot
wooosaii has quit [*.net *.split]
tlwoerner has quit [*.net *.split]
joaoSchim__ has quit [*.net *.split]
biot has quit [*.net *.split]
mkstr has quit [*.net *.split]
mthall has quit [*.net *.split]
<milkylainen>
whatsup with the liberia net nowdays. About as stable as a house of cards.
wooosaii has joined #u-boot
joaoSchim__ has joined #u-boot
mkstr has joined #u-boot
biot has joined #u-boot
tlwoerner has joined #u-boot
mthall has joined #u-boot
mthall has quit [Max SendQ exceeded]
mthall has joined #u-boot
swiftgeek has joined #u-boot
<marex>
milkylainen: facebook is down aftermath ?
HubiVanKanubi has joined #u-boot
gsz has quit [Quit: leaving]
sdfgsdfgDropBear has joined #u-boot
<marex>
OK, the U-Boot CI test.py failure output is just useless garbage
<marex>
lukma: test/py/tests/test_efi_capsule/test_capsule_firmware.py: 'env set dfu_alt_info "sf 0:0=u-boot-bin raw 0x100000 0x50000;u-boot-env raw 0x150000 0x200000"',
<marex>
this looks nonsensical to me, the dfu_alt_info value
swiftgeek has quit [Ping timeout: 246 seconds]
swiftgeek has joined #u-boot
sdfgsdfgDropBear has quit [Quit: sdfgsdfgDropBear]
sdfgsdfgDropBear has joined #u-boot
<marex>
OK, after wasting hours trying to reproduce the failure locally (because hey, there is no documentation), I learn that the test.py emits the exact same useless log spam
<marex>
there is literally zero useful information in the output like
<marex>
"this is how the problem was triggered"
<marex>
I really utterly hate this test.py stuff, it really is just frustrating cryptic and totally demotivating
<marex>
if this is what should motivate people to write tests, well ... it is total failure
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #u-boot
mmu_man has joined #u-boot
mckoan is now known as mckoan|away
jwillikers has joined #u-boot
sdfgsdfgDropBear has quit [Quit: sdfgsdfgDropBear]
<__ad>
can i select a fdt@x of a fitimage to be used without creating additional configuration ?
<marex>
addr:<subimg_uname> - direct component image specification
<__ad>
marex, thanks ... mmm i am always getting "Could not find subimage node type 'kernel'"
<__ad>
is it bootm ${loadaddr}:fdt@2 ?
clarity_ is now known as clarity
torez has joined #u-boot
<mrnuke>
marex: I learn about new chips by reading patches. nice
<marex>
__ad: fdt@2 no longer works, you must use fdt-2 and you must also fix all your build systems and everything
<__ad>
marex, only syntax that works on this 2020.04 is bootm ${loadaddr}:kernel@1 ${loadaddr}:ramdisk@1 ${loadaddr}:fdt@2
<marex>
__ad: is that what NXP distributes now ?
jwillikers has quit [Ping timeout: 252 seconds]
smartin has joined #u-boot
<__ad>
marex, it's a variscite u-boot
swiftgeek has quit [Ping timeout: 268 seconds]
<sjg1>
mwalle: It is hard for me to comment without seeing some code reference or patches. You could try returning -ENODEV in the probe() method instead
<sjg1>
marex: It seems to do that when U-Boot crashes, although it would be much better if it actually said so. Also, spitting out all the code around it doesn't seem useful to me