21:47 <HeyMeco> Hello everyone, I was wondering if it makes sense on Rockchip to keep the boot order as "mmc1 mmc0 nvme scsi usb pxe dhcp spi" instead of switching mmc0 and nvme? I would say the expected behavior for end users is to for example install a system to nvme from emmc and then being able to use it out of the box. At least on the downstream radxa vendor

21:47 <HeyMeco> u-boot they also do SD-Card (mmc1) then nvme too

22:55 <sr20det> Hi!. is there any limit too bootargs length? it looks like it is trimmed to 241 byte on arm

23:32 <marex> sr20det: it might not be bootargs length cap

23:34 <sr20det> also i did not quite understand kernel_addr_r and kernel_comp_addr_r for booti. can they be equal to avoid moving?

23:34 <marex> 55 config SYS_CBSIZE

23:34 <marex> 56 int "Console input buffer size"

23:34 <marex> see common/Kconfig

23:34 <marex> also see PBSIZE and co.

23:35 <sr20det> marex, do those configs apply on env parsing, i never set bootargs manually

23:35 <marex> 264 kernel_addr_r

23:35 <marex> 265 Address at which to load the kernel, e.g. 0x02080000

23:35 <marex> 266

23:35 <marex> 267 kernel_comp_addr_r

23:35 <marex> 268 Address to which to decompress the kernel, e.g. 0x08000000

23:35 <marex> doc/develop/bootstd/overview.rst

23:35 <marex> kcxt: ^ maybe you can chime in on this, since it seems snapdragon thing ?

23:36 <marex> sr20det: those configs are compile time configs, youd have to rebuild your u-boot to change those

23:37 <sr20det> *BSIZE looks unrelated. because env is read from mmc

23:38 <marex> env scripts are interpreted by the shell, the shell limits are configured in common/Kconfig , there is a bunch of them

23:41 <sr20det> oh. thank you

23:42 <marex> sr20det: if you look in your uboot build .config for some number around 200 , you will likely find the right knob too