GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #u-boot
frieder has joined #u-boot
<hthiery>
marex: I figured out one problem. In the pitx-imx8m case there is a function (board_phys_sdram_size) in the board specific code that tries to get the board variant. This function uses gpios. U-Boot has DM_GPIO enabled and tries to setup the GPIOS in dm-pre-reloc path.
<hthiery>
marex: but this is not the main problem with the clk-imx8mq thing. I still have to remove all the unused clocks to get the board started.
prabhakarlad has quit [Quit: Client closed]
frieder has quit [Remote host closed the connection]
<marex>
hthiery: probably too small MALLOC_F then, eventually you get ENOMEM somewhere in the clock driver
<hthiery>
marex: i am still struggling with why this is happening on my board and not the others
<Tartarus>
xypron: So for moving CI to ubuntu 22.04, the Dockerfile part was easy but given the CI errors it feels like the new host image is leading us to trip up on some new security features or something? I don't know, but it's not looking like a trivial update so I'll poke it again later this week maybe
<marex>
hthiery: different clock needed in SPL , or no DM in SPL on other boards ?
<hthiery>
marex: maybe I do not understand this full
<hthiery>
marex: the issue is in U-boot .. not in spl
<hthiery>
marex: there is no SPL_CLK_IMX8MQ set in my config
<marex>
hthiery: err, in U-Boot itself ?
<marex>
I always thought this was all SPL
<hthiery>
marex: no it is just in U-boot .. on SPL issue
guillaume_g has quit [Quit: Konversation terminated!]
<marex>
errrr
guillaume_g has joined #u-boot
<marex>
hthiery: so lemme understand this again , with these two patches in place , u-boot now hangs for you ?
<marex>
11c8ab01f3e ("clk: imx8mq: Add a clock driver for the imx8mq")
<marex>
and if you revert them, all good ?
<hthiery>
marex: I'm not able to remove the patches
<marex>
hthiery: git revert ?
<hthiery>
marex: other issues appear if doing that
<marex>
what issues ?
<hthiery>
marex: I tried to revert but now "Failed to find clock node. Check device tree"
<hthiery>
"Failed to find clock node. Check device tree"
<marex>
hthiery: git grep for that string, see where it comes from
<hthiery>
"initcall sequence 0000000040278918 failed at call 000000004021fe40 (err=-19)"
<marex>
oh yes ... 0x40278918 ... of course
<marex>
that one
<marex>
hthiery: now aarch64...objdump -lSD u-boot | less and search for ^ that address , to figure out which initcall that is
<hthiery>
marex: ret = dm_init_and_scan(true);
<hthiery>
in initf_dm()
<marex>
so, some driver fails to bind/probe ...
<marex>
continue
<marex>
there is going to be some loop which iterates over DT nodes and gets you a struct udevice * each time
<hthiery>
what about the power domain
<marex>
add printf (... dev->name) to identify the name
<marex>
power domains are optional for U-Boot, they're only used for USB
<marex>
one step at a time
<hthiery>
I will do as you suggested .. but unfortunalty I have to leave now
<hthiery>
i want to go to the swimming pool with my son
<hthiery>
;-)
<marex>
have fun
<hthiery>
thanks and thanks for your help
hanetzer has quit [Ping timeout: 264 seconds]
<xypron>
Tartarus: I expected that gcc throwing a bunch of new warnings. It will be a bunch of work to work through those. But it is a work that needs to be done.
<xypron>
Do you have link to the CI runs?
<Tartarus>
xypron: We don't change GCC, and it's failing much earlier than that. I thought you were following along from your other comments :)
<Tartarus>
But it feels like with the new container, and I gather backend stuff going "Oh, newer container runtime features are available" we're tripping some security check, just like how you need newer docker itself to even make a container with ubuntu 22.04 as the runtime as otherwise it can't read /etc/apt/* stuff and so on
<xypron>
Tartarus: Does root do the clone?
<Tartarus>
Don't think so
<Tartarus>
All this runs how it normally runs
<xypron>
Tartarus: Di you try: git config --global --add safe.directory /builds/u-boot/u-boot
<Tartarus>
xypron: No, I just moved on to other problems.
<xypron>
Git 2.35.2 has some "improved" security.
<Tartarus>
I'm not sure and will have to poke at what env variables provide that path for both systems
davlefou has quit [Ping timeout: 260 seconds]
davlefou_ has quit [Ping timeout: 260 seconds]
<Tartarus>
"/builds" isn't set by Dockerfile nor .gitlab-ci.yml, so we can't just hard-code that part, need to see what's passing it. Or hope we can hard-code that for gitlab and /u/u-boot or whatever the azure error is