<LeSpocky>
CONFIG_LOGLEVEL is at 4 and CONFIG_LOG is disabled … o.O
<LeSpocky>
not sure what's going on here
guest92 has joined #u-boot
<LeSpocky>
is this related to 6afdb1585112 ("dm: core: migrate debug() messages to use dm_warn") perhaps?
<LeSpocky>
so CONFIG_DM_WARN is set here … that might be the reason
<LeSpocky>
IMHO this contradicts the help text
mmu_man has joined #u-boot
<LeSpocky>
sent a mail about it
<xypron>
Tartarus: you already mentioned that some platforms are exposing the SPL banner more than once. But I think my patch is still valid to bring all EFI py tests doing a reboot into line.
Stat_headcrabbed has joined #u-boot
iprusov_ has quit [Quit: WeeChat 3.5]
iprusov has joined #u-boot
joeskb7 has joined #u-boot
Stat_headcrabbed has quit [Quit: Stat_headcrabbed]
Stat_headcrabbed has joined #u-boot
eballetbo has joined #u-boot
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
enok has joined #u-boot
warpme has joined #u-boot
enok has quit [Remote host closed the connection]
<marex>
LeSpocky: ping qschulz here too if needed
<qschulz>
marex: got Cced on the mail, not sure how to go forward with this for now (c.f. ML)
<NishanthMenon>
if someone needs one of the boards, do drop me a note.. will try and facilitate it
<qschulz>
the thing is a bit broken logic to me though (but it's a slow brain day, so maybe it's rather my brain that is broken), it changes the log level of the dm_warn calls
<qschulz>
marex: ^
<qschulz>
dm_warn should be a warn IMO, not "well, it's a debug except if you select that option"
<Tartarus>
re dm_warn stuff, I'm also re-re-checking nothing sets DM_WARN by default
<Tartarus>
And leaning towards "well, this shows the whole area needs better logging?" was was suggested within the thread, and I want to see what sjg1 says
<qschulz>
git grep DM_WARN returns literally only the Kconfig and the thing that changes the log level in dm
<qschulz>
in short, i don't mind if it's reverted, but I kinda need this commit in some form :)
<qschulz>
I don't want the assert() to be enabled just to debug DM stuff :)
<qschulz>
and since I'm the one who broke stuff, I guess it falls on my shoulders to reimplement it properly :)
<calebccff>
sjg1: Tartarus: could you take a look at lore.kernel.org/u-boot/20240831-qcom-phones-v1-0-08614edd8e35@linaro.org ?
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
mmu_man has quit [Ping timeout: 252 seconds]
warpme has joined #u-boot
warpme has quit [Client Quit]
<sjg1>
calebccff: trini: Sorry I'm a bit tied up but will try to take a look later today. I see that that series was applied
<qschulz>
marex: sjg1: Tartarus: LeSpocky: I think i'll just send a patch adding dm_debug and instead of doing debug() -> dm_warm() we go debug() -> dm_debug()
<qschulz>
(which means, it'll be a patch to go from **some** dm_warn() to dm_debug()
<qschulz>
(the ones I changed only basically)
<qschulz>
and then we can figure something better once we have time/interest :)
monstr has quit [Remote host closed the connection]
<LeSpocky>
qschulz: I have full faith you sort that out properly, I'm sorry I can not give any feedback until october 14th, I disabled DM_WARN in my builds and that's fine for me for now
<qschulz>
LeSpocky: enjoy the time off work :)
<LeSpocky>
thanks :)
sukrutb has joined #u-boot
<marex>
qschulz: if it doesn't start spewing loads of messages on any machine (why was that reported then?) then I think the current form is also OK ?
ikarso has quit [Quit: Connection closed for inactivity]