Hi all,
We have been tasked with creating a Linux Yocto distribution for the Morello server and we were given a green light to upstream the patches. We do have the hardware that we can test it on, in fact we have already had Morello Linux running in its current state on the board with some simple user space apps in purecap mode. The scope of this work would include the toolchain, bsp, kernel and musl-libc in the user space.
I am aware that there is an existing meta-arm layer that we could use as a starting point. The question is how and should we commit our patches to the project ?
Kind regards, Pawel
On 20 Oct 2022, at 11:38, Pawel Zalewski pzalewski@thegoodpenguin.co.uk wrote:
We have been tasked with creating a Linux Yocto distribution for the Morello server and we were given a green light to upstream the patches. We do have the hardware that we can test it on, in fact we have already had Morello Linux running in its current state on the board with some simple user space apps in purecap mode. The scope of this work would include the toolchain, bsp, kernel and musl-libc in the user space.
I am aware that there is an existing meta-arm layer that we could use as a starting point. The question is how and should we commit our patches to the project ?
Speaking as a meta-arm co-maintainer (although emphasis on co-, Jon may disagree), considering Morello is experimental and may well involve some in-progress patches to start with, I think it would be best if a new layer was created (meta-morello, presumably) which could depend on meta-arm for anything it needs.
If Morello was just a new machine tune and some firmware tweaking I’d happily accept it into meta-arm, but right now we’re talking about fast-moving toolchain/libc/kernel patches.
Ross IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Many thanks, we will go ahead with a new layer.
Kind regards, Pawel
On Thu, 20 Oct 2022 at 11:59, Ross Burton Ross.Burton@arm.com wrote:
On 20 Oct 2022, at 11:38, Pawel Zalewski pzalewski@thegoodpenguin.co.uk wrote:
We have been tasked with creating a Linux Yocto distribution for the Morello server and we were given a green light to upstream the patches. We do have the hardware that we can test it on, in fact we have already had Morello Linux running in its current state on the board with some simple user space apps in purecap mode. The scope of this work would include the toolchain, bsp, kernel and musl-libc in the user space.
I am aware that there is an existing meta-arm layer that we could use as a starting point. The question is how and should we commit our patches to the project ?
Speaking as a meta-arm co-maintainer (although emphasis on co-, Jon may disagree), considering Morello is experimental and may well involve some in-progress patches to start with, I think it would be best if a new layer was created (meta-morello, presumably) which could depend on meta-arm for anything it needs.
If Morello was just a new machine tune and some firmware tweaking I’d happily accept it into meta-arm, but right now we’re talking about fast-moving toolchain/libc/kernel patches.
Ross IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
linux-morello-distros@op-lists.linaro.org
-
Pawel Zalewski -
Ross Burton