From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: [PATCH v2 3/4] doc: Enhance list of supported cross-archs, drop QEMU reference
Date: Fri, 11 Sep 2020 14:13:08 +0200 [thread overview]
Message-ID: <845a58b35e021b6a740d876bd492cfbc1c4f4254.1599826389.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1599826389.git.jan.kiszka@siemens.com>
From: Jan Kiszka <jan.kiszka@siemens.com>
We also test mipsel in cross-builds. RISC-V 64-bit is available but
experimental.
Furthermore, remove the reference to qemu because Isar also supports
building cross for physical targets. This might be confusing.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
doc/user_manual.md | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/doc/user_manual.md b/doc/user_manual.md
index fb6574bb..9c28d165 100644
--- a/doc/user_manual.md
+++ b/doc/user_manual.md
@@ -714,10 +714,14 @@ put into Isar apt.
Debian cross-compilation works out of the box starting from Debian stretch distribution. Currently the following build configurations are supported in Isar:
- - qemuarm-stretch
- - qemuarm-buster
- - qemuarm64-stretch
- - qemuarm64-buster (for host >= buster)
+ - arm-stretch
+ - arm-buster
+ - arm64-stretch
+ - arm64-buster (for host >= buster)
+ - mipsel-stretch
+ - mipsel-buster (for host >= buster)
+
+Experimental support for riscv64 is available as well.
## Examining and debugging package generation inside their buildchroot
--
2.26.2
next prev parent reply other threads:[~2020-09-11 12:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 12:13 [PATCH v2 0/4] 32-bit compat arch support Jan Kiszka
2020-09-11 12:13 ` [PATCH v2 1/4] Add compat architecture support via multiarch Jan Kiszka
2020-09-11 12:13 ` [PATCH v2 2/4] ci: Add compat arch support Jan Kiszka
2020-09-11 12:13 ` Jan Kiszka [this message]
2020-09-11 12:13 ` [PATCH v2 4/4] doc: Describe new " Jan Kiszka
2020-09-21 9:24 ` [PATCH v2 0/4] 32-bit " Jan Kiszka
2020-09-21 9:41 ` Baurzhan Ismagulov
2020-09-21 12:06 ` Jan Kiszka
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=845a58b35e021b6a740d876bd492cfbc1c4f4254.1599826389.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.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