honister and 1.52 Bitbake branch were recently released, so let's build those too. Signed-off-by: Quentin Schulz <quentin.schulz@...> --- scripts/run-docs-build | 4 ++-- 1 file chang

Both releases are missing an important patch that changes the displayed version from dev to the appropriate release number. This is confusing to the user and probably breaks some assumptions in some s

Not all Rockchip boards have their console running at 1500000 baud in U-Boot and the kernel. Such is the case for puma-haikou RK3399-based SoM+Carrierboard. In order to prepare for the addition of pum

From Linux kernel v5.14 to v5.14.11 (both included), the Ethernet MAC controller found on RK3399 is not working. A fix is available in v5.14.12 and later (available also in v5.15) which is provided he

v5.14.14 is already fixed. The only release currently is 3.4 and I hit that issue, hence the patch. I assume not everybody is updating to 3.4.1 when it's out, I've seen people running behind dot relea

I could define a python function and use it like this: SRC_URI:append:rk3399 = "${@rk3399_fix_mac(d)}" Would that work better for you? Cheers, Quentin

Hi Khem, meta-rockchip does not have a honister branch for now because it is still working with master branch from OE-Core. This patch does not break this behaviour. Do I add a "known issues" to the R

Hi Michael, Richard, I think we want to make sure we have all docs up-to-date, even for the branches that aren't maintained anymore. Especially since it's not taking a lot of CPU time to build them, i

Hi Michael, Why don't we migrate this different method (find) to the one you implement in this commit too? I could see a variable storing all "force-latest" files or someting like that to make it obvi

Reviewed-by: Quentin Schulz <foss+yocto@...> Thanks, Quentin

Hi Nicolas, Indeed. But this should be fixed, because we should handle this the same way documentation/releases.html is, with a common one across all releases. With the current implementation, only ma

Agreed, I poorly reviewed it. Thanks for stoping us before the disaster :) I think all our issues always come down to this weird and inefficient organization we have for docs and common files between

Hi Trevor, Would sed -i "s/#define RK3399_BAUDRATE\s\+.*/#define RK3399_BAUDRATE plep/" ${S}/plat/rockchip/rk3399/rk3399_def.h work for you? This makes sure that only RK3399_BAUDRATE definition will b

Hi Trevor, Gentle ping :) Honister 3.4.1 being out it's less of an issue but the question remains at least for settling on a policy :) Cheers, Quentin

Not all Rockchip boards have their console running at 1500000 baud in U-Boot and the kernel. Such is the case for puma-haikou RK3399-based SoM+Carrierboard. In order to prepare for the addition of pum

Hi Trevor, Yes, sorry just sent it :) Cheers, Quentin

Hi all, No frustration on my side, just a debate/discussion on what we should do. No, the problem is the same because it is broken only in Honister 3.4. So if we take this patch in, we basically have

Not all Rockchip boards have their console running at 1500000 baud in U-Boot and the kernel. Such is the case for puma-haikou RK3399-based SoM+Carrierboard. In order to prepare for the addition of pum

Sorry, this was meant for meta-rockchip, sending a new mail with the proper topic. Cheers, Quentin

Hi Michael, https://autobuilder.yoctoproject.org/typhoon/#/builders/114 seems to be a good place to start with? Cheers, Quentin