Re: [agl-dev-community] AGL virtio integration

[Jan-Simon Möller <dl9pf@xxxxxx>]

Hi Mikhail !


> That is our case. Board-independent kernel.

This makes it simpler.

Ok here is the steps we need:

- we need the CONFIG fragment file
- we need to include it in the various kernel bbappends as the other
  .cfg frags

- note that different boards have different kernel versions. Most are 5.4,
  but e.g. m3/h3 is 4.19 . So you might have 2 versions of the cfg fragment
  in the end.

- only question is if this needs or should be conditional to a
  AGL_ENABLE_VIRTIO variable or not.
--- IOW: is it save/secure to be enabled by default even if not used or
--- do we need to turn it on for use
--- that question is for you to answer
- if conditional, we need an aglsetup template to throw the switch


simple case:
- conf fragment + require in all kernel bbappends (all meta-agl-bsp)

conditional case:
- conf fragment + _conditional_ require in all kernel bbappends (meta-agl-bsp)
- aglsetup template ...
--- now to keep it simple, I'm indeed tempted to put the template in
     meta-agl/templates
--- the workflow meta-agl-devel -> meta-agl is mainly for userspace software
     additions. for kernel config additions it is simpler to do it
     in meta-agl-bsp

So TLDR: the question to answer: are these kernel configs safe to be enabled
by default ?

If so, we can go for the simple case.


BR,
JS



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#8625): https://lists.automotivelinux.org/g/agl-dev-community/message/8625
Mute This Topic: https://lists.automotivelinux.org/mt/76558271/2167316
Group Owner: agl-dev-community+owner@xxxxxxxxxxxxxxxxxxxxxxxxx
Unsubscribe: https://lists.automotivelinux.org/g/agl-dev-community/leave/4543822/883735764/xyzzy  [list-automotive-discussions82@xxxxxxxxxxx]
-=-=-=-=-=-=-=-=-=-=-=-