Hi Jan-Simon!
Thanks for the answers. My answers inline.
On 9/1/20 6:33 PM, Jan Simon Moeller 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 Mikhail!
Can you give me a few more details on what needs changes ?
Then I can give some better advice where we plug it in.
So I gather we need kernel options turned on:
For that we have include files in
meta-agl-bsp/recipes-kernel/linux/*
(if it is valid for all boards)
That is our case. Board-independent kernel.
and
meta-agl-bsp/<board specific>/recipes-kernel/linux/
(if it is board specific)
meta-agl-devel would be the place to start.
You'd create a subfolder 'meta-agl-SOMETHING' and a template
in templates/feature/agl-SOMENAME .
Great, will do.
The move to meta-agl once matured goes through the SAT.
Understood.
Wrt kernel. I'd propose to stay with the linux-yocto kernel as it is iirc 5.4
already.
Right, Yocto 3.1 has 5.4 kernel. In the future it wold be nice to jump to the
next lts.
So we only have to flip the config options and done.
Yes, for Kooki Koi, considering timeline, this will be relatively
straightforward. That was the point from the start.
Best regards,
Jan-Simon
------
Jan-Simon Möller
AGL Release Manager
The Linux Foundation
Visit us at:
www.automotivegradelinux.org <http://www.automotivegradelinux.org>
lists.automotivelinux.org <http://lists.automotivelinux.org>
www.linuxfoundation.org <http://www.linuxfoundation.org>
On Tue, Sep 1, 2020 at 5:06 PM <mgo@xxxxxxxxxxxxxxx
<mailto:mgo@xxxxxxxxxxxxxxx>> wrote:
Hi all!
I would like to ask for your advice how to proceed with virito integration
in AGL. As I was proposing on the previous EG VIRT session, we would like to
make a new <codename> (any suggestions on codename strategy?) Yocto
qemuarm64-like machine that will have a vanilla lts Linux kernel (e.g. 5.4)
with a virtio-enabled minimalistic defconfig and minimalistic rcarh3 dt.
I would like to ask where should we start development: in meta-agl directly
or in meta-agl-devel layer? It is not clear what will be the way out of the
'devel' layer if we'll start there. Any suggestions?
BR,
Mikhail.
--
Mikhail Golubev
Senior Software Engineer
OpenSynergy GmbH
Rotherstr. 20, 10245 Berlin
Telefon: +49 (30) 60 98 54 0 - 903
EMail: mikhail.golubev@xxxxxxxxxxxxxxx <mailto:mikhail.golubev@xxxxxxxxxxxxxxx>
www.opensynergy.com <http://www.opensynergy.com>
Handelsregister/Commercial Registry: Amtsgericht Charlottenburg, HRB 108616B
Geschäftsführer/Managing Director: Regis Adjamah
BR,
Mikhail.
--
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 (#8624): https://lists.automotivelinux.org/g/agl-dev-community/message/8624
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]
-=-=-=-=-=-=-=-=-=-=-=-
