<sjg1>
marex: We are not ready yet for easy xPL builds. I think this is the order:
<sjg1>
1. Troy's patches merged
<sjg1>
2. I respin spld and it gets merged
<sjg1>
3. We decide to go ahead with split config (splg) and that gets merged
<sjg1>
4. We agree on a Kconfig schema change for this (not essential but very helpful)
<marex>
ha
<marex>
I wonder if I should partialy mis-use TPL for an idea from fosdem
<marex>
basically, since MX8M now has the PSCI provider ability in U-Boot, that PSCI provider code is part of U-Boot, which means if there is a bug , U-Boot update is necessary
<marex>
but
<marex>
U-Boot now runs in EL3, it is the PSCI provider, and ... it doesn't call into any PSCI implementation
<marex>
so
<marex>
why not create self-contained PSCI implementation (xPL) which would be loaded and started just before the kernel (like optee for example) from the same kernel fitImage
<marex>
then if there is a bug in the PSCI implementation, one just updates the fitImage, as if they were updating a kernel image
<marex>
sjg1: is there some way to get the command output from 'ut' ?
<marex>
sjg1: like, during test development, I would like to be able to see what the commands printed before their failed , or just run a command to verify whatever
matthias_bgg has quit [Quit: Leaving]
lucascastro has joined #u-boot
lucascastro has quit [Ping timeout: 246 seconds]
mmu_man has quit [Ping timeout: 246 seconds]
<sjg1>
marex: With sandbox you can use the -v flag
<marex>
sjg1: thanks ... I ran into another problem in the meantime
<marex>
if a command prints \t , it is considered a line in the output
<marex>
I am looking into membuff_readline now
<sjg1>
marex: Oh that is a bug. If you change the space to a '\0' in console_record_readline() it should work
<marex>
sjg1: yeah, it does ... dang
<marex>
sjg1: can you send a patch ?
<sjg1>
OK
<marex>
sjg1: you can add my RB/TB marek.vasut+renesas@mailbox.org
mmu_man has joined #u-boot
<marex>
and I can go back to fdt print test
<marex>
which btw has a bug too
<marex>
fdt print on property clock-frequency = <0x00fde800>; ... prints it as string
<marex>
its already fixed in dtc, but broken in uboot
<marex>
sjg1: that u-boot -v ... fantastic, thanks
<sjg1>
OK good!
<marex>
sjg1: the -v doesn't print the executed commands though, does it ?