On Tue, 11 Nov, at 09:09:18PM, Fathi Boudra wrote:
As you may know, some work is in progress to include a new qemu machine for ARMv8 architecture. It will help in getting meta-aarch64 bits merged as YOCTO will be able to test this architecture.
Ah, that's awesome news. That will certainly help me out with validating the arm64 kernel changes I take through my kernel.org EFI tree.
But to get back to the big picture, you haven't said what the 'obstacles' actually are, just some vague handwaving about missing aarch64 support in OE-core. I'm curious to know what you have actually accomplished so far and even more curious to know which concrete problems you are facing. Bundling poky instead of plain OE-core makes me strongly suspect meta-luv being broken to start with.
I think Koen's point is valid: what are the issues observed? Is meta-luv usable with meta-linaro? i.e. can we just include the layer in our daily builds and see what breaks
Sure you can, the layer itself is available here,
http://git.yoctoproject.org/cgit/cgit.cgi/meta-luv/
You'll need to set the DISTRO to "luv", but other than that I don't think there's anything else required.
The issues have mainly been around the fact that we rely upon the genericx86-64 currently and there's no armv8 equivalent, so I can't build and try things out without pulling in the meta-linaro layer.
Of course, we could integrate meta-linaro into luv-yocto umbrella repository, but that seems like the wrong approach to me. I'm sure other projects would benefit from seeing generic aarch64 support upstream.