From: Jan Kiszka <jan.kiszka@siemens.com>
To: vijai kumar <vijaikumar.kanagarajan@gmail.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v2 00/13] RISC-V support
Date: Tue, 28 Jan 2020 23:06:17 +0100 [thread overview]
Message-ID: <e21a7a65-8411-8218-a796-8ab0106a9093@siemens.com> (raw)
In-Reply-To: <946ae65d-ac00-4f74-870e-1be88dc2e741@googlegroups.com>
On 28.01.20 20:23, vijai kumar wrote:
> Hi Jan,
>
> A couple of observations.
>
> 1. Entry for qemuriscv64-sid-ports is missing in BBMULTICONFIG.
Good catch. I was not using this but rather a local kas file, so this
slipped through.
> 2. My distro (Xubuntu 18.04) does not seem to have the latest
> qemu-debootstrap to support riscv. It fails with unknown arch.
> I have to manually hack qemu-debootstrap to add an entry for riscv64.
>
> If you have a buster host, it should work out of the box I guess. It has
> the latest debian package.
Always use kasproject/kas-isar when not building on Debian natively. I
do the same on SUSE. There is no point in worrying about *Ubuntu for us.
Thanks for testing,
Jan
>
> Thanks,
> Vijai Kumar K
>
> On Tuesday, January 28, 2020 at 9:32:49 PM UTC+5:30, Jan Kiszka wrote:
>
> On 28.01.20 16:51, vijai kumar wrote:
> > Hi Jan,
> >
> > Actually I wanted to try this out. Do you have a tree from which
> I can
> > get this series?
> >
> > I am yet to set up my mail client to download patches. Sorry
> about that.
> >
>
> No problem. Just pushed the branch (un-rebased) to
> https://github.com/siemens/isar/commits/jan/queue
> <https://github.com/siemens/isar/commits/jan/queue>.
>
> Jan
>
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux
>
> --
> You received this message because you are subscribed to the Google
> Groups "isar-users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to isar-users+unsubscribe@googlegroups.com
> <mailto:isar-users+unsubscribe@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/isar-users/946ae65d-ac00-4f74-870e-1be88dc2e741%40googlegroups.com
> <https://groups.google.com/d/msgid/isar-users/946ae65d-ac00-4f74-870e-1be88dc2e741%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2020-01-28 22:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 8:28 Jan Kiszka
2020-01-13 8:28 ` [PATCH v2 01/13] meta: Add debian-sid-ports distro config Jan Kiszka
2020-01-13 8:28 ` [PATCH v2 02/13] meta: Add RISC-V architecture Jan Kiszka
2020-01-13 8:28 ` [PATCH v2 03/13] meta: Allow cross-compilation for RISC-V Jan Kiszka
2020-01-13 8:28 ` [PATCH v2 04/13] start_vm: Add RISC-V 64-bit support Jan Kiszka
2020-01-13 8:28 ` [PATCH v2 05/13] meta-isar: Add qemuriscv64 virtual target Jan Kiszka
2020-01-13 8:28 ` [PATCH v2 06/13] meta-isar: Clean up qemu multiconfigs Jan Kiszka
2020-01-28 21:51 ` Henning Schild
2020-01-28 22:06 ` Jan Kiszka
2020-01-13 8:28 ` [PATCH v2 07/13] u-boot-script: Account for variations of kernel files and boot commands Jan Kiszka
2020-01-13 8:28 ` [PATCH v2 08/13] linux-custom: Tune strip rule to cover vmlinux images as well Jan Kiszka
2020-01-13 8:28 ` [PATCH v2 09/13] linux-custom: Add support for RISC-V Jan Kiszka
2020-01-13 8:28 ` [PATCH v2 10/13] linux-modules: " Jan Kiszka
2020-01-13 8:28 ` [PATCH v2 11/13] linux-mainline: Avoid failing UBIFS test when defconfig does not support it Jan Kiszka
2020-01-13 8:28 ` [PATCH v2 12/13] linux-mainline: Update to 5.4.10 Jan Kiszka
2020-01-13 8:28 ` [PATCH v2 13/13] meta-isar: Add HiFive Unleashed board as physical RISC-V target Jan Kiszka
2020-01-28 11:31 ` [PATCH v2 00/13] RISC-V support Jan Kiszka
2020-01-28 15:51 ` vijai kumar
2020-01-28 16:02 ` Jan Kiszka
2020-01-28 16:09 ` vijai kumar
2020-01-28 19:23 ` vijai kumar
2020-01-28 22:06 ` Jan Kiszka [this message]
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=e21a7a65-8411-8218-a796-8ab0106a9093@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=vijaikumar.kanagarajan@gmail.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