Hi Stephane!
Great news! 5.4 has lots of nice features besides virtio drivers. I will be much
easier to downstream virtio drivers if needed.
BR,
Mikhail.
On 9/3/20 12:57 AM, Stephane Desneux wrote:
CAUTION: This email originated from outside of the organization.
Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hi,
Things will become even simpler in the near future because we are working on the
bump of Renesas BSP on AGL: this will bring the newest BSP with kernel 5.4,
targeting KK.
At the end, it should be easier to support the same config across all ref boards
as kernel version will be very close. For other community boards, it could be
either conditional (=unsupported) or supported through specific community efforts.
HTH
---
Stephane Desneux - CTO - IoT.bzh
stephane.desneux@xxxxxxx - www.iot.bzh
On 02/09/2020 11:49, Jan-Simon Möller wrote:
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
--
Mikhail Golubev
Senior Software Engineer
OpenSynergy GmbH
Rotherstr. 20, 10245 Berlin
Telefon: +49 (30) 60 98 54 0 - 903
EMail: mikhail.golubev@xxxxxxxxxxxxxxx
www.opensynergy.com
Handelsregister/Commercial Registry: Amtsgericht Charlottenburg, HRB 108616B
Geschäftsführer/Managing Director: Regis Adjamah
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8635): https://lists.automotivelinux.org/g/agl-dev-community/message/8635
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]
-=-=-=-=-=-=-=-=-=-=-=-