general high-level discussion about spectrum
 help / color / mirror / Atom feed
From: Ville Ilvonen <ville.ilvonen@unikie.com>
To: discuss@spectrum-os.org
Cc: evgeniia.nikolaenko@unikie.com
Subject: Documentation of aarch64 port on Spectrum OS upstream
Date: Mon, 14 Nov 2022 14:02:52 +0200	[thread overview]
Message-ID: <cf8275c6-7b54-b3f0-52d2-f60b25a8ebd2@unikie.com> (raw)

Hi,

We've built the wayland demo branch on aarch64 port and added some other 
apps on it to showcase embedded virtualization with Spectrum OS.

The build configuration for the reference device is documented [1] with 
the out-of-tree build configuration as agreed in our earlier 
discussion[2]. There's also some additional accompanied documentation on 
binary cache we have used with aarch64 and could be of general use. I'd 
like to see that documentation upstreamed as much as possible.

Would it make sense to link this work from Spectrum documentation? To 
indicate work in progress aarch64 support with known issues on a ref. 
device and avoid forking this documentation?

The practical benefit is that anyone interested in building Spectrum OS 
for an aarch64 device using vendor BSP would have some reference linked 
from Spectrum OS documentation - e.g. an initial porting guide as even 
the x86_64 does not yet use the build configuration. Additionally, I 
don't want to fragment Spectrum OS ports and their documentation further 
than necessary.

Best,

-Ville

[1] https://github.com/tiiuae/spectrum-config-imx8/blob/main/README.md
[2] 
https://spectrum-os.org/lists/archives/spectrum-discuss/CAP-nJwHTmROzMbyYNtrTrOdXGV-iJvwPuJ3FSZb3gLy5R3z80Q@mail.gmail.com/ 



             reply	other threads:[~2022-11-14 12:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14 12:02 Ville Ilvonen [this message]
2022-11-23 10:57 ` Documentation of aarch64 port on Spectrum OS upstream Alyssa Ross

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cf8275c6-7b54-b3f0-52d2-f60b25a8ebd2@unikie.com \
    --to=ville.ilvonen@unikie.com \
    --cc=discuss@spectrum-os.org \
    --cc=evgeniia.nikolaenko@unikie.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).