From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Damien Le Moal <Damien.LeMoal@wdc.com>
Cc: "alistair@alistair23.me" <alistair@alistair23.me>,
"yann.morin.1998@free.fr" <yann.morin.1998@free.fr>,
"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v5 05/10] board: Add Sipeed MAIX-bit support
Date: Mon, 3 Jan 2022 16:25:20 +0100 [thread overview]
Message-ID: <20220103162520.07b40bf0@windsurf> (raw)
In-Reply-To: <ba60fa7b8380ce6c817bb5bb2ada0283752efdfe.camel@wdc.com>
Hello Damien,
On Fri, 31 Dec 2021 00:39:14 +0000
Damien Le Moal <Damien.LeMoal@wdc.com> wrote:
> My apologies about the delay. I have been swamped with the kernel and other
> projects. I kept at this a little though, mainly trying to address the elf2flt
> issue which seems to generate unworkable binaries for Peter, while it is always
> working for me... Really no clue what is going on so I am a little stuck with
> that. I will work on updates addressing all of Peter's comments and see how
> that work.
No worries about the delay. I took advantage of the Christmas/New Year
quiet period to help catch up with our patch backlog, and stumbled
across your patch series, which is why I asked.
I also saw the on-going discussion with Peter who had issues with
non-working binaries produced by elf2flt.
> > - The readme.txt file for each defconfig should be added in the patch
> > adding the defconfig
>
> Hmm... It is the same procedure for all boards, only the defconfig name
> differs. Hence I added this README file last with all board defconfigs
> mentioned. I can add the README file with the first board and update it with
> each patch adding a board ?
Yes, that would work: add the README file with the first board, and
update it progressively for each board.
Thanks a lot!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-03 15:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 7:17 [Buildroot] [PATCH v5 00/10] Add RV64 NOMMU and Canaan K210 SoC support Damien Le Moal
2021-10-26 7:17 ` [Buildroot] [PATCH v5 01/10] package: Makefile.in: fix elf2flt invocation options Damien Le Moal
2021-10-27 13:37 ` Peter Korsgaard
2021-10-26 7:17 ` [Buildroot] [PATCH v5 02/10] package/elf2flt: add RISC-V 64-bits support Damien Le Moal
2021-10-27 13:38 ` Peter Korsgaard
2021-10-28 0:35 ` Damien Le Moal
2021-10-28 6:30 ` Peter Korsgaard
2021-10-26 7:17 ` [Buildroot] [PATCH v5 03/10] package/Makefile.in: Fix NOMMU RISC-V 64-bits toolchain base name Damien Le Moal
2021-10-27 3:26 ` Alistair Francis
2021-10-27 13:38 ` Peter Korsgaard
2021-10-26 7:17 ` [Buildroot] [PATCH v5 04/10] arch/config: Make RISC-V 64-bits MMU optional Damien Le Moal
2021-10-27 13:38 ` Peter Korsgaard
2021-10-26 7:17 ` [Buildroot] [PATCH v5 05/10] board: Add Sipeed MAIX-bit support Damien Le Moal
2021-10-27 13:51 ` Peter Korsgaard
2021-10-28 1:07 ` Damien Le Moal
[not found] ` <e6eb0eda-20db-dfd6-c3d6-47db131bc247@gmail.com>
2021-10-28 2:24 ` Damien Le Moal
2021-10-28 7:01 ` Peter Korsgaard
2021-12-30 20:27 ` Thomas Petazzoni
2021-12-30 20:29 ` Thomas Petazzoni
2021-12-31 0:39 ` Damien Le Moal
2022-01-03 15:25 ` Thomas Petazzoni [this message]
2022-02-15 23:37 ` Damien Le Moal
2022-02-16 7:54 ` Thomas Petazzoni via buildroot
2021-10-26 7:17 ` [Buildroot] [PATCH v5 06/10] board: Add Sipeed MAIX-Go support Damien Le Moal
2021-10-26 7:17 ` [Buildroot] [PATCH v5 07/10] board: Add Sipeed MAIXDUINO support Damien Le Moal
2021-10-26 7:17 ` [Buildroot] [PATCH v5 08/10] board: Add Sipeed MAIX-Dock support Damien Le Moal
2021-10-26 7:17 ` [Buildroot] [PATCH v5 09/10] board: Add Canaan KD233 support Damien Le Moal
2021-10-26 7:17 ` [Buildroot] [PATCH v5 10/10] board: Document Canaan K210 based boards support 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=20220103162520.07b40bf0@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=Damien.LeMoal@wdc.com \
--cc=alistair@alistair23.me \
--cc=buildroot@buildroot.org \
--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