On 25.05.22 19:34, Hannah Kiekens wrote:

On Wed, May 25, 2022 at 1:41 PM Jan Kiszka <jan.kiszka@...
<mailto:jan.kiszka@...>> wrote:

Hehe, someone actually read AND tried the manual :). Thanks for caring!

Would be good to list some reasoning for switching to bullseye here.
Buster should still work, "just" not with 4.19 anymore.

In fact, we should think about making bullseye default in kas-cip.yml.


There is no real reason why I am switching to bullseye.
This combination worked great, what it was before did not

Right, and that is likely only because the current combination chooses
kernel 4.19 which is no longer working since 05dd963a.

This patch is currently doing the rounds at our site for evaluating/demo
isar-cip-core, I needed a working, easy to follow guide for regular
techies.  I am not sure if the technical details matter in this case
 

For that particular purpose, it does not. However, we should try to
structure the document in a way that it can be easier maintained or is
less likely to out-date where possible.

5.10 becomes default when selecting bullseye, so you could drop that
option.

It's probably also worth noting that some of the build configuration
issues are "resolved" now via "kas-container menu" and its dependency
encoding. But it is still clearer to describe the actual configuration
the way it's done here.


Sorry, it's not entirely clear if you want me to modify this patch or not.

Was kind of thinking out loudly. Let's make it more concert now:

- describe the requirements, here kernel >= 5.10
- suggest to use "kas-container menu", besides providing a concrete
call of "kas-container build ..."

Meanwhile, I've created a patch to switch defaults to bullseye [1].

Thanks,
Jan

[1]
https://lore.kernel.org/cip-dev/9c68811b-c8df-6f80-d314-b379b131ab8c@siemens.com/T/#u

--
Siemens AG, Technology
Competence Center Embedded Linux