Tartarus changed the topic of #u-boot to: SOURCE MOVED TO https://source.denx.de/u-boot/u-boot.git / U-Boot v2023.07.02, v2023.10-rc2 are OUT / Merge Window is CLOSED, next branch is OPEN / Release v2023.10 is scheduled for 02 October 2023 / Channel archives at https://libera.irclog.whitequark.org/u-boot
<sjg1> Tartarus: I am having trouble building with docker:
<marex> sjg1: so if I run ./test/py/test.py -B sandbox64 --build-dir /tmp/b/sandbox -k ut_bootstd_bootflow_cmd_menu
<marex> sjg1: I get INTERNALERROR> Traceback (most recent call last):
<marex> INTERNALERROR> Exception: include/autoconf.mk does not exist; try passing --build option?
<marex> I was under the impression it was supposed to do the build ?
<sjg1> marex: Yes, but add the --build flag to do that
<marex> sjg1: if I try to get help, I get another traceback
<marex> i.e. test.py --help
<marex> Exception: .config does not exist; try passing --build option?
<marex> sjg1: from a clean worktree I guess ?
<marex> (else I get traceback too)
<marex> mmc2: 2 (SD)Can't map file 'mmc1.img': Invalid argument
<sjg1> marex: Yes you must use 'make mrproper' if you have done an in-tree build, since the symlinks get created, etc.
<marex> hum ... I thought this thing was supposed to prepare that mmc1.img file
<marex> $ ./test/py/test.py -B sandbox --build-dir /tmp/b/sandbox -k ut_bootstd_bootflow_cmd_menu --build
<marex> even this fails, hum
<marex> and the mmc1.img is 0 bytes long
qschulz has quit [Remote host closed the connection]
qschulz has joined #u-boot
<sjg1> marex: You are running a test...you need to run the setup first. Or just leave off the -k and run everything.
<sjg1> marex: Re the invalid argument, I wonder if somehow your losetup has left an open file?
<sjg1> marex: Anyway I suggest you start with a full run. Once everything is working (and the files are present) you can cut it back to what you need
<marex> sjg1: what kind of losetup ?
<marex> sjg1: the user shouldn't even have permissions to run losetup in the first place
mmu_man has quit [Ping timeout: 244 seconds]
mckoan_ has joined #u-boot
mckoan|away has quit [Ping timeout: 246 seconds]
<sjg1> marex: There are sudos in the tests!
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
<marex> sjg1: so yeah, those are not happening
<marex> oh well
vagrantc has quit [Quit: leaving]
hanetzer has joined #u-boot
prabhakarlad has quit [Quit: Client closed]
hanetzer has quit [Ping timeout: 260 seconds]
hanetzer has joined #u-boot
persmule has quit [Remote host closed the connection]
goliath has quit [Quit: SIGSEGV]
mwalle has quit [Quit: WeeChat 3.0]
camus has joined #u-boot
<marex> NishanthMenon: hey, is Faiz Abbas still with TI ? Or who is now responsible for the TI UFS stuff ?
Wouter0100670440 has quit [Quit: The Lounge - https://thelounge.chat]
Wouter0100670440 has joined #u-boot
mmu_man has joined #u-boot
sakman has quit [Remote host closed the connection]
sakman has joined #u-boot
<vigneshr> marex: Faiz is no longer at TI. If there is something to be looked at, do send me and NishanthMenon a note and we will fwd internally to get help.
redbrain has quit [Read error: Connection reset by peer]
redbrain has joined #u-boot
<marex> vigneshr: $ grep -A 3 UFS MAINTAINERS
<marex> vigneshr: Faiz is the only maintainer of drivers/ufs/ , so, who is taking over then ?
<vigneshr> marex: Sorry, didn't release that. Let me check internally on who is looking at UFS and ask maintainers list to be updated
<marex> thanks
rockosov has quit [Ping timeout: 246 seconds]
rockosov has joined #u-boot
sng has joined #u-boot
gsz has joined #u-boot
sng has quit [Ping timeout: 256 seconds]
sng_ has joined #u-boot
pivi has quit [Quit: BRB]
pivi has joined #u-boot
sng_ has quit [Remote host closed the connection]
teejay has joined #u-boot
teejay_ has quit [Ping timeout: 260 seconds]
sng has joined #u-boot
sng has quit [Remote host closed the connection]
sng has joined #u-boot
Wouter0100670440 has quit [Quit: The Lounge - https://thelounge.chat]
Wouter0100670440 has joined #u-boot
gsz has quit [Ping timeout: 256 seconds]
camus1 has joined #u-boot
camus has quit [Ping timeout: 256 seconds]
camus1 is now known as camus
goliath has joined #u-boot
sng has quit [Remote host closed the connection]
sng has joined #u-boot
stefanro has joined #u-boot
sng has quit [Ping timeout: 250 seconds]
Wouter0100670440 has quit [Quit: The Lounge - https://thelounge.chat]
Wouter0100670440 has joined #u-boot
sng has joined #u-boot
persmule has joined #u-boot
sng_ has joined #u-boot
sng has quit [Read error: Connection reset by peer]
sng_ has quit [Remote host closed the connection]
___nick___ has joined #u-boot
stefanro has quit [Quit: Leaving.]
<sjg1> marex: OK great, thanks!
___nick___ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
___nick___ has joined #u-boot
___nick___ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
___nick___ has joined #u-boot
sng has joined #u-boot
sng has quit [Read error: Connection reset by peer]
sng has joined #u-boot
<sjg1> Tartarus: I don't seem to get warnings about uninited vars in sandbox anymore. Have you noticed that?
sng has quit [Remote host closed the connection]
sng has joined #u-boot
<Tartarus> I haven't intentionally checked in a while, but I have other tests such that I'd see if anything got in to master itself
<sjg1> Tartarus: I have some pretty clear cases of uninited vars that gcc does not find
<sjg1> Tartarus: Also the 'KBUILD_CFLAGS += $(warning)' is weird (in Makefile.extrawarn) since $(warning xxx) is a Makefile command
<Tartarus> oh, non-default stuff?
sng has quit [Ping timeout: 246 seconds]
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #u-boot
sng has joined #u-boot
stefanro has joined #u-boot
stefanro has quit [Client Quit]
camus has quit [Quit: camus]
gsz has joined #u-boot
gsz has quit [Ping timeout: 245 seconds]
prabhakarlad has joined #u-boot
sng has quit [Read error: Connection reset by peer]
Clamor has joined #u-boot
<Clamor> Why can I get a driver probe 2 times in the same stage? (The first probe did not fail)
<sjg1> Tartarus: Yes that is non-default, but still, it seems strange to use $(warning) to mean two things
<Tartarus> I do lament that getting further kbuild re-syncs is so difficult
Clamor has quit [Ping timeout: 256 seconds]
Clamor has joined #u-boot
sng has joined #u-boot
sng has quit [Remote host closed the connection]
sng has joined #u-boot
sng has quit [Remote host closed the connection]
sng has joined #u-boot
<marex> Clamor: maybe two instances of the driver ?
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
Clamor has quit [Ping timeout: 256 seconds]
Clamor has joined #u-boot
Clamor has quit [Read error: Connection reset by peer]
___nick___ has quit [Ping timeout: 246 seconds]
Wouter0100670440 has quit [Quit: The Lounge - https://thelounge.chat]
Wouter0100670440 has joined #u-boot
<marex> sjg1: can we make readq() available on sandbox32 ?
<sjg1> Clamor: That sounds like a bug, or something is horribly wrong
<sjg1> Tartarus: Are you trying a sync?
<sjg1> marex: I don't see why not
<sjg1> marex: (yet)
<marex> I think it isnt necessary, hold on
<Tartarus> I've failed to sync to v5.0 twice now
<sjg1> Tartarus: You mean you synced but it doesn't work?
<Tartarus> Yes, I've failed to get it to work a few times
<Tartarus> I think I was closer the second time, and just didn't update some of our rules right, or something
<sjg1> Tartarus: I had a fiddle with it at one point and gave up
<sjg1> Tartarus: I wonder if applying the patches one-by-one would be too onerous? i.e. get closer, but not all the way?
<Tartarus> That was my first pass, and failed much worse
<sjg1> Tartarus: Well if it is close, perhaps send the patches and others can help? It is better than what we have
<Tartarus> Well frankly, if someone is feeling comfortable with make stuff, it'd be better probably to just port 6.5's logic over instead
<Tartarus> moving to "just" 4 years out of date doesn't seem super helpful, it's just how it had been being updated
<marex> sjg1: yeah, I can avoid the readq for now
___nick___ has joined #u-boot
<marex> 217 ut_asserteq_str((i++, "mmc2.blk"), dev->name);
<marex> what is this horribleness
<marex> 226 blk_foreach_probe(BLKF_BOTH, dev)
<marex> 227 ut_asserteq_str((++i == 1 ? "mmc2.blk" : i == 2 ?
<marex> 228 "mmc1.blk" : "mmc0.blk"), dev->name);
<marex> urgh
<sjg1> Tartarus: Likely you've done the bulk of the work...it's just finding the needle in the haystack that is left
<sjg1> marex: Trying to avoid writing a separate function, with attendant state. The ++ is safe with ut_assert
sng has quit [Read error: Connection reset by peer]
<marex> sjg1: it's still ew
<marex> sjg1: do you recall off the top of your head what's the right formatting string for phys_addr_t ?
<marex> seems %pa is not it
<sjg1> marex: I vaguely recall it coming up recently, but it seems there isn't one
<marex> doc/develop/printf.rst:phys_addr_t %pa, see pointers
<sjg1> You can add something to the various types.h I suppose
<marex> except it does not work
<sjg1> They are addresses, not pointers
<sjg1> EFI people get horribly confused by this
<marex> so docs are also wrong now ?
<marex> xypron: ^
<sjg1> for phys_addr_t I suggest copying something from inttypes.h
<sjg1> For other attempts: git grep "\"ll"
<marex> I guess I can also do just
<marex> - log_debug("[%s]: XIP device base addr: 0x%llx , lba_shift: %d , lbas: %lu\n",
<marex> - dev->name, plat->phys_base, plat->lba_shift, plat->lba);
<marex> + log_debug("[%s]: XIP device base addr: 0x%lx , lba_shift: %d , lbas: %lu\n",
<marex> + dev->name, (uintptr_t)plat->phys_base, plat->lba_shift, plat->lba);
<marex> this
<marex> it is ew, but oh well
<marex> sigh, that nvmxip stuff enabled only for sandbox64 eluded tests and it is utter crap
<marex> it just falls apart all over the place, grumb
goliath has quit [Quit: SIGSEGV]