Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Damien Le Moal <damien.lemoal@wdc.com>
Cc: Alistair Francis <alistair@alistair23.me>,
	"Yann E . MORIN" <yann.morin.1998@free.fr>,
	buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v4 0/9] Add RV64 NOMMU and Canaan K210 SoC support
Date: Mon, 30 Aug 2021 23:32:04 +0200	[thread overview]
Message-ID: <20210830233204.2d8dcfad@windsurf> (raw)
In-Reply-To: <20210830044100.260173-1-damien.lemoal@wdc.com>

Hello Damien,

On Mon, 30 Aug 2021 13:40:51 +0900
Damien Le Moal <damien.lemoal@wdc.com> wrote:

> Christoph Hellwig (2):
>   package/elf2flt: add RISC-V 64-bits support
>   package/Makefile.in: Fix NOMMU RISC-V 64-bits toolchain base name
> 
> Damien Le Moal (7):
>   arch/config: Make RISC-V 64-bits MMU optional

Just tested with the first 3 patches applied the following defconfig:

BR2_riscv=y
# BR2_USE_MMU is not set

It fails to build with:

/home/thomas/buildroot/buildroot/output/host/riscv64-buildroot-linux-uclibc/bin/elf2flt: Loading to RAM ('-r' option) 
is required

This is using the default Busybox configuration, i.e
package/busybox/busybox.config. I haven't tested if other noMMU
architectures exhibit the same issue.

The package/busybox/busybox-minimal.config causes the same issue.

I'm gonna try on ARM noMMU and see.

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

  parent reply	other threads:[~2021-08-30 21:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-30  4:40 [Buildroot] [PATCH v4 0/9] Add RV64 NOMMU and Canaan K210 SoC support Damien Le Moal
2021-08-30  4:40 ` [Buildroot] [PATCH v4 1/9] package/elf2flt: add RISC-V 64-bits support Damien Le Moal
2021-08-30  4:40 ` [Buildroot] [PATCH v4 2/9] package/Makefile.in: Fix NOMMU RISC-V 64-bits toolchain base name Damien Le Moal
2021-08-30  4:40 ` [Buildroot] [PATCH v4 3/9] arch/config: Make RISC-V 64-bits MMU optional Damien Le Moal
2021-08-30  4:40 ` [Buildroot] [PATCH v4 4/9] board: Add Sipeed MAIX-bit support Damien Le Moal
2021-08-30  4:40 ` [Buildroot] [PATCH v4 5/9] board: Add Sipeed MAIX-Go support Damien Le Moal
2021-08-30  4:40 ` [Buildroot] [PATCH v4 6/9] board: Add Sipeed MAIXDUINO support Damien Le Moal
2021-08-30  4:40 ` [Buildroot] [PATCH v4 7/9] board: Add Sipeed MAIX-Dock support Damien Le Moal
2021-08-30  4:40 ` [Buildroot] [PATCH v4 8/9] board: Add Canaan KD233 support Damien Le Moal
2021-08-30  4:41 ` [Buildroot] [PATCH v4 9/9] board: Document Canaan K210 based boards support Damien Le Moal
2021-08-30 21:32 ` Thomas Petazzoni [this message]
2021-08-30 21:42   ` [Buildroot] [PATCH v4 0/9] Add RV64 NOMMU and Canaan K210 SoC support Damien Le Moal
2021-08-30 21:55     ` Thomas Petazzoni
2021-08-30 21:59       ` Damien Le Moal
2021-08-30 21:52   ` Thomas Petazzoni

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=20210830233204.2d8dcfad@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=alistair@alistair23.me \
    --cc=buildroot@buildroot.org \
    --cc=damien.lemoal@wdc.com \
    --cc=yann.morin.1998@free.fr \
    /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