13:13 <Raito_Bezarius> My bootloader CLI has a `help` which returns a subset of actually available commands, is there a secret way / known way to obtain a better list of commands? I can try to pull the binary and RE but I'm not sure if the command table is something that does exist in U-Boot and can be statically discovered from the binary

13:16 <Raito_Bezarius> but the `help xyz` works on it

13:16 <f_> Raito_Bezarius: if it's not in `help`, then it's not in your build.

13:19 <Raito_Bezarius> f_: right, so the only trivial way is to perform ∀ command, `help command` and see if it returns

13:19 <Raito_Bezarius> is there a nice way to compile all possible commands inside of u-boot src code?

13:29 <marex> probably , enable all CONFIG_CMD in Kconfig , but I doubt you can really get them all into single build, some might be specific to conflicting configs

13:29 <marex> why ?

13:29 <marex> Raito_Bezarius: note that U-Boot is GPLv2 , just look at the source code, no need to RE anything

13:31 <Raito_Bezarius> marex: yeah I'd need to ask the vendor for the source code

13:32 <f_> Raito_Bezarius: oh is it downstream?

13:32 <Raito_Bezarius> yep…

13:32 <Raito_Bezarius> it's the U-Boot of the Zyxel NWA50AX AP to be precise

13:32 <marex> and the vendor sucks so badly they dont outright distribute their changes ?

13:32 <f_> oh then it's more like YMMV than anything else..

13:32 <f_> marex: too much vendors just suck because of that :P

13:33 <Raito_Bezarius> I'm trying to look and I don't think they published right away their source code

13:33 <marex> you have every right to the source code if you do have a matching binary build

13:33 <Raito_Bezarius> https://www.zyxel.com/global/en/form/gpl-oss-software-notice

13:34 <Raito_Bezarius> they have this

13:34 <Raito_Bezarius> I find it beautiful they ask my location

13:36 <Raito_Bezarius> I sent a request, will publish the source code when I receive it

15:22 <Clamor> Is there a CONFIG_ version of CFG_PRAM?

18:05 <marex> Clamor: CFG is old preprocessor config, CONFIG is Kconfig

18:05 <marex> Clamor: feel free to introduce one and send a patch

18:05 <Clamor> Ugh

18:13 <marex> I think there was even a script to do the conversion of Kconfig symbols

18:19 <milkylainen> I think you can tell Kconfig what the prefix should be.

18:28 <Clamor> That would be nice

18:30 <Clamor> marex: maybe you remember where to get one

18:31 <marex> Clamor: git log configs or check scripts/

18:31 <Clamor> Thanks

18:32 <marex> ./tools/moveconfig.py

18:34 <milkylainen> lkc.h:return getenv( "CONFIG_" ) ?: CONFIG_;

18:34 <milkylainen> And my favourite, only took Linux 15 years to reinstate it after they broke the original functionality:

18:35 <milkylainen> confdata.c:warn_unknown = getenv("KCONFIG_WARN_UNKNOWN_SYMBOLS");

18:35 <milkylainen> :)

18:39 <Clamor> qconfig now

18:41 <milkylainen> ? I don't think the frontend should matter.

18:42 <milkylainen> Atleast not for the option I listed.

18:43 <marex> milkylainen: better discuss this with Kconfig maintainer

18:47 <milkylainen> marex: Kconfig never cared about other projects that much. Only kernel needs. I've tried. I even told them that the entire kernel had 1k+ undefined sybols and not warning developers like they used to do is a stupid idea.

18:47 <milkylainen> But yeah. OT.

18:49 <f_> OT == off-topic?

18:50 <marex> milkylainen: I'm sure that went down well

18:56 <milkylainen> marex :)

18:56 <milkylainen> Anyway. It's reinstated. And all downstreams are probably going to pick it up sooner or later.

18:58 <milkylainen> f_: yes.

19:14 <Clamor> marex: ok, converted.

19:22 <Clamor> Oh, it seems that I know why this migration was not performed

19:24 <Clamor> Km and omap5

19:41 <marex> NishanthMenon: ^

20:34 <marex> NishanthMenon: is the VPU in AM68x supported upstream ? (it seems git grep fails me today)