Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Damien Le Moal <damien.lemoal@wdc.com>,
	Alistair Francis <alistair@alistair23.me>,
	Mark Corbin <mark@dibsco.co.uk>,
	buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v2 4/9] board: Add Sipeed MAIX-bit support
Date: Sat, 24 Jul 2021 00:35:14 +0200	[thread overview]
Message-ID: <20210724003514.4da0f292@windsurf> (raw)
In-Reply-To: <6a1b7aba-9fe8-d0ab-ffda-b24167b0cfce@mind.be>

Hello,

On Sat, 24 Jul 2021 00:25:27 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:

> > +++ b/board/canaan/k210-common/busybox-tiny-initramfs.config  
> 
>  Wouldn't it be better to start from busybox-minimal.config and just add a
> fragment that removes the unnecessary options?

Also, we already have a package/busybox/busybox-minimal.config. I'm not
sure we want to add zillions of "minimal" Busybox configurations.

> > +++ b/configs/sipeed_maix_bit_defconfig
> > @@ -0,0 +1,23 @@
> > +BR2_riscv=y
> > +# BR2_COMPILER_PARANOID_UNSAFE_PATH is not set

This should remain the default.

> > +BR2_KERNEL_HEADERS_5_13=y
> > +# BR2_UCLIBC_INSTALL_UTILS is not set

This should remain the default as well.

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

  reply	other threads:[~2021-07-23 22:35 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-15  0:48 [Buildroot] [PATCH v2 0/9] Add RISC-V NOMMU and Canaan K210 SoC support Damien Le Moal
2021-07-15  0:48 ` [Buildroot] [PATCH v2 1/9] arch/config: Make RISC-V MMU optional Damien Le Moal
2021-07-17 15:46   ` Yann E. MORIN
2021-07-15  0:48 ` [Buildroot] [PATCH v2 2/9] package/elf2flt: add RISC-V support Damien Le Moal
2021-07-17 15:54   ` Yann E. MORIN
2021-07-15  0:48 ` [Buildroot] [PATCH v2 3/9] package make: build RISC-V nommu builds as linux Damien Le Moal
2021-07-15  4:45   ` Alistair Francis
2021-07-15  0:48 ` [Buildroot] [PATCH v2 4/9] board: Add Sipeed MAIX-bit support Damien Le Moal
2021-07-23 22:25   ` Arnout Vandecappelle
2021-07-23 22:35     ` Thomas Petazzoni [this message]
2021-07-23 22:43       ` Damien Le Moal
2021-07-24 14:56         ` Arnout Vandecappelle
2021-07-23 22:40     ` Damien Le Moal
2021-07-24 14:53       ` Arnout Vandecappelle
2021-07-15  0:48 ` [Buildroot] [PATCH v2 5/9] board: Add Sipeed MAIX-Go support Damien Le Moal
2021-07-15  0:48 ` [Buildroot] [PATCH v2 6/9] board: Add Sipeed MAIXDUINO support Damien Le Moal
2021-07-15  0:48 ` [Buildroot] [PATCH v2 7/9] board: Add Sipeed MAIX-Dock support Damien Le Moal
2021-07-15  0:48 ` [Buildroot] [PATCH v2 8/9] board: Add Canaan KD233 support Damien Le Moal
2021-07-15  0:48 ` [Buildroot] [PATCH v2 9/9] board: Document Canaan K210 based boards support Damien Le Moal
2021-07-23 22:25 ` [Buildroot] [PATCH v2 0/9] Add RISC-V NOMMU and Canaan K210 SoC support Arnout Vandecappelle
2021-07-23 22:40   ` Damien Le Moal
2021-08-28 13:48     ` Thomas Petazzoni
2021-08-29 22:44       ` Damien Le Moal

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=20210724003514.4da0f292@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=alistair@alistair23.me \
    --cc=arnout@mind.be \
    --cc=buildroot@buildroot.org \
    --cc=damien.lemoal@wdc.com \
    --cc=mark@dibsco.co.uk \
    /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