for Debian Buster. A build for Debian Bullseye can use the webserver and createfs option as the are active in the Debian provided package on salsa. Only `nodoc` needs to applied to buster and

Quirin just told me that only nodoc is needed for all. Dropping this patch again (keeping 1/2 though). Please send a v3 which does that, ie. adds a _bullseye profile and keeps the existing buster

Thanks, applied. Jan -- Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux

From my testing only the option nodoc is necessary for bullseye. Quirin

So these things were actually broken for bullseye so far? Jan -- Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux

Stretch in now dropped. The conditional includes for buster is now not needed. Those includes are applicable to buster as well as bullseye. Signed-off-by: Vijai Kumar K

The generic profile of CIP Core started its work with buster, stretch was only experimental for this layer. Remove the support now. Signed-off-by: Vijai Kumar K

Changes since v1: - Change P1 commit message - Bring back conditional include of buster patch for swupdate This series has 2 patches P1 drops stretch support P2 cleans up overrides / conditional

The more accurate reasoning would be that the generic profile of CIP Core does started its work with buster, stretch was only experimental for this layer. Jan -- Siemens AG, T RDA IOT Corporate

Hi, The patch 0009-debian-prepare-build-for-isar-debian-buster.patch should not be applied to bullseye as it can have an impact on the functionality of SWUpdate. Quirin

Stretch in now dropped. The conditional includes for buster is now not needed. Those includes are applicable to buster as well as bullseye. Signed-off-by: Vijai Kumar K

stretch is now old enough to be dropped. Support the current stable(bullseye) and old-stable(buster). Signed-off-by: Vijai Kumar K <Vijaikumar_Kanagarajan@...> --- Kconfig

This series has 2 patches P1 drops stretch support P2 cleans up overrides / conditional includes for buster/bullseye CI Job is

From: Biju Das <biju.das.jz@...> commit fa2a30f8e0aa9304919750b116a9e9e322465299 upstream. As per RZ/G2L HW(Rev.0.50) manual, clock monitor register value 0 means clock is not supplied

From: Biju Das <biju.das.jz@...> commit 32897e6fff196a5de4981030466ae391dfe56c7b upstream. The AXI and CHI clocks use the same register bit for controlling clock output. Add a new clock

From: Biju Das <biju.das.jz@...> commit 7c5a2561737d88b55764034b27f897498e90a319 upstream. Add support to handle mux clocks in order to select a clock source from multiple