From: vijai kumar <vijaikumar.kanagarajan@gmail.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v2 00/13] RISC-V support
Date: Tue, 28 Jan 2020 07:51:19 -0800 (PST) [thread overview]
Message-ID: <72ebdb74-f3ea-472d-937b-aeb7ace84aa5@googlegroups.com> (raw)
In-Reply-To: <aa7bfd92-5ec4-18f5-698e-6628c84038a1@siemens.com>
[-- Attachment #1.1: Type: text/plain, Size: 6077 bytes --]
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.
Thanks,
Vijai Kumar K
On Tuesday, January 28, 2020 at 5:01:38 PM UTC+5:30, Jan Kiszka wrote:
>
> On 13.01.20 09:28, [ext] Jan Kiszka wrote:
> > Changes since v1:
> > - added HiFive Unleashed board
> > - enabled custom kernel builds for riscv64
> > - enabled custom module cross-build for riscv64
> > - updated mainline kernel to 5.4.10 (needed for HiFive)
> > - added some missing riscv64-specific vars to bitbake.conf
> > - enabled u-boot-script for riscv64, and likely also mipsel
> > - cleaned up qemu multiconfigs
> >
> > Jan
> >
> > Jan Kiszka (13):
> > meta: Add debian-sid-ports distro config
> > meta: Add RISC-V architecture
> > meta: Allow cross-compilation for RISC-V
> > start_vm: Add RISC-V 64-bit support
> > meta-isar: Add qemuriscv64 virtual target
> > meta-isar: Clean up qemu multiconfigs
> > u-boot-script: Account for variations of kernel files and boot
> > commands
> > linux-custom: Tune strip rule to cover vmlinux images as well
> > linux-custom: Add support for RISC-V
> > linux-modules: Add support for RISC-V
> > linux-mainline: Avoid failing UBIFS test when defconfig does not
> > support it
> > linux-mainline: Update to 5.4.10
> > meta-isar: Add HiFive Unleashed board as physical RISC-V target
> >
> > meta-isar/conf/machine/qemuamd64.conf | 17 +++++++--
> > meta-isar/conf/machine/qemuarm.conf | 16 +++++++--
> > meta-isar/conf/machine/qemuarm64.conf | 16 +++++++--
> > meta-isar/conf/machine/qemui386.conf | 14 ++++++--
> > meta-isar/conf/machine/qemumipsel.conf | 16 +++++++--
> > meta-isar/conf/machine/qemuriscv64.conf | 24 +++++++++++++
> > meta-isar/conf/machine/sifive-fu540.conf | 15 ++++++++
> > meta-isar/conf/multiconfig/qemuamd64-bullseye.conf | 16 ---------
> > .../conf/multiconfig/qemuamd64-buster-tgz.conf | 6 ----
> > meta-isar/conf/multiconfig/qemuamd64-buster.conf | 16 ---------
> > meta-isar/conf/multiconfig/qemuamd64-stretch.conf | 13 -------
> > meta-isar/conf/multiconfig/qemuarm-bullseye.conf | 12 -------
> > meta-isar/conf/multiconfig/qemuarm-buster.conf | 12 -------
> > meta-isar/conf/multiconfig/qemuarm-stretch.conf | 12 -------
> > meta-isar/conf/multiconfig/qemuarm64-bullseye.conf | 12 -------
> > meta-isar/conf/multiconfig/qemuarm64-buster.conf | 12 -------
> > meta-isar/conf/multiconfig/qemuarm64-stretch.conf | 12 -------
> > meta-isar/conf/multiconfig/qemui386-bullseye.conf | 13 -------
> > meta-isar/conf/multiconfig/qemui386-buster.conf | 13 -------
> > meta-isar/conf/multiconfig/qemui386-stretch.conf | 13 -------
> > .../conf/multiconfig/qemumipsel-bullseye.conf | 12 -------
> > meta-isar/conf/multiconfig/qemumipsel-buster.conf | 12 -------
> > meta-isar/conf/multiconfig/qemumipsel-stretch.conf | 12 -------
> > .../conf/multiconfig/qemuriscv64-sid-ports.conf | 8 +++++
> > .../conf/multiconfig/sifive-fu540-sid-ports.conf | 7 ++++
> > .../recipes-bsp/opensbi/files/sifive-fu540-rules | 13 +++++++
> > .../opensbi/opensbi-sifive-fu540_0.5.bb | 23 ++++++++++++
> > .../example-module/example-module.bb | 1 +
> > ...fpga-Rename-socfpga_cyclone5_de0_-sockit-.patch | 41
> ----------------------
> > ...ainline_4.19.88.bb => linux-mainline_5.4.10.bb} | 13 ++++---
> > .../scripts/lib/wic/canned-wks/sifive-fu540.wks | 10 ++++++
> > meta/classes/dpkg-base.bbclass | 2 ++
> > meta/conf/bitbake.conf | 2 ++
> > meta/conf/distro/debian-sid-ports.conf | 25 +++++++++++++
> > meta/conf/distro/debian-sid-ports.list | 2 ++
> > meta/conf/distro/debian-sid.list | 2 ++
> > .../u-boot-script/files/update-u-boot-script | 22 ++++++++----
> > .../base-apt/files/distributions.in | 2 +-
> > .../buildchroot/buildchroot-host.bb | 7 ++++
> > .../crossbuild-essential-riscv64_0.1-isar.bb | 11 ++++++
> > .../isar-apt/files/distributions.in | 2 +-
> > .../recipes-kernel/linux-module/files/debian/rules | 3 ++
> > .../linux/files/debian/isar/install.tmpl | 10 +++---
> > meta/recipes-kernel/linux/files/debian/rules.tmpl | 2 +-
> > meta/recipes-kernel/linux/linux-custom.inc | 2 ++
> > scripts/start_vm | 4 +++
> > 46 files changed, 260 insertions(+), 270 deletions(-)
> > create mode 100644 meta-isar/conf/machine/qemuriscv64.conf
> > create mode 100644 meta-isar/conf/machine/sifive-fu540.conf
> > create mode 100644
> meta-isar/conf/multiconfig/qemuriscv64-sid-ports.conf
> > create mode 100644
> meta-isar/conf/multiconfig/sifive-fu540-sid-ports.conf
> > create mode 100644
> meta-isar/recipes-bsp/opensbi/files/sifive-fu540-rules
> > create mode 100644 meta-isar/recipes-bsp/opensbi/
> opensbi-sifive-fu540_0.5.bb
> > delete mode 100644
> meta-isar/recipes-kernel/linux/files/0001-ARM-dts-socfpga-Rename-socfpga_cyclone5_de0_-sockit-.patch
>
> > rename meta-isar/recipes-kernel/linux/{linux-mainline_4.19.88.bb =>
> linux-mainline_5.4.10.bb} (64%)
> > create mode 100644
> meta-isar/scripts/lib/wic/canned-wks/sifive-fu540.wks
> > create mode 100644 meta/conf/distro/debian-sid-ports.conf
> > create mode 100644 meta/conf/distro/debian-sid-ports.list
> > create mode 100644 meta/conf/distro/debian-sid.list
> > create mode 100644 meta/recipes-devtools/crossbuild-essential-riscv64/
> crossbuild-essential-riscv64_0.1-isar.bb
> >
>
> Any feedback from anyone on this?
>
> Jan
>
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux
>
[-- Attachment #1.2: Type: text/html, Size: 12698 bytes --]
next prev parent reply other threads:[~2020-01-28 15:51 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 [this message]
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
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=72ebdb74-f3ea-472d-937b-aeb7ace84aa5@googlegroups.com \
--to=vijaikumar.kanagarajan@gmail.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