Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yu-Chien Peter Lin <peterlin@andestech.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: tim609@andestech.com, ycliang@andestech.com, dylan@andestech.com,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] andes_ae350_45_defconfig: bump opensbi, u-boot and linux
Date: Sun, 6 Nov 2022 12:07:13 +0000	[thread overview]
Message-ID: <Y2ejY8/mrFd/AVi+@APC323> (raw)
In-Reply-To: <20221105220835.1e1fa5f0@windsurf>

Hi Thomas,

On Sat, Nov 05, 2022 at 10:08:35PM +0100, Thomas Petazzoni wrote:
> On Fri, 4 Nov 2022 16:04:07 +0800
> Yu Chien Peter Lin <peterlin@andestech.com> wrote:
> 
> > This patch bumps following packages to the newer version:
> > - OpenSBI v1.1
> > - U-boot v2022.10
> > - Linux 6.0
> > 
> > Linux kernel is hosted on AndesTech Github which includes ethernet,
> > SD card, DMAC, RTC, WDT drivers support. OpenSBI is based on v1.1
> > with andes platfrom fdt driver, hence adding patches for U-boot to
> > update the plmt and plicsw compatible strings and modify the IPI scheme.
> > 
> > Signed-off-by: Yu Chien Peter Lin <peterlin@andestech.com>
> > ---
> >  board/andes/ae350/ae350.dts                   | 274 ------------------
> >  board/andes/ae350/genimage_sdcard.cfg         |   2 +-
> >  ...isable-PIC-explicitly-for-assembling.patch |  29 --
> >  ...2-Enable-cache-for-opensbi-jump-mode.patch |  25 --
> >  ...001-Fix-mmc-no-partition-table-error.patch |  27 --
> >  ...-Support-DTS-of-ftsdc010-driver-for-.patch |  35 +++
> >  ...2-Prevent-fw_dynamic-from-relocation.patch |  27 --
> >  ...-tree-blob-address-at-8-byte-boundar.patch |  37 +++
> >  ...0003-Fix-u-boot-proper-booting-issue.patch |  26 --
> >  ...andes_plic.c-use-modified-IPI-scheme.patch |  43 +++
> >  ...04-Enable-printing-OpenSBI-boot-logo.patch |  25 --
> >  ...04-riscv-Rename-Andes-PLIC-to-PLICSW.patch | 263 +++++++++++++++++
> >  board/andes/ae350/post-build.sh               |   2 +-
> >  board/andes/ae350/readme.txt                  |   4 +-
> >  .../boot/extlinux/extlinux.conf               |   2 +-
> >  board/andes/ae350/uboot.config.fragment       |   6 +-
> >  configs/andes_ae350_45_defconfig              |  16 +-
> >  17 files changed, 394 insertions(+), 449 deletions(-)
> >  delete mode 100755 board/andes/ae350/ae350.dts
> >  delete mode 100644 board/andes/ae350/patches/opensbi/0001-Disable-PIC-explicitly-for-assembling.patch
> >  delete mode 100644 board/andes/ae350/patches/opensbi/0002-Enable-cache-for-opensbi-jump-mode.patch
> >  delete mode 100644 board/andes/ae350/patches/uboot/0001-Fix-mmc-no-partition-table-error.patch
> >  create mode 100644 board/andes/ae350/patches/uboot/0001-mmc-ftsdc010_mci-Support-DTS-of-ftsdc010-driver-for-.patch
> >  delete mode 100644 board/andes/ae350/patches/uboot/0002-Prevent-fw_dynamic-from-relocation.patch
> >  create mode 100644 board/andes/ae350/patches/uboot/0002-spl-Align-device-tree-blob-address-at-8-byte-boundar.patch
> >  delete mode 100644 board/andes/ae350/patches/uboot/0003-Fix-u-boot-proper-booting-issue.patch
> >  create mode 100644 board/andes/ae350/patches/uboot/0003-riscv-andes_plic.c-use-modified-IPI-scheme.patch
> >  delete mode 100644 board/andes/ae350/patches/uboot/0004-Enable-printing-OpenSBI-boot-logo.patch
> >  create mode 100644 board/andes/ae350/patches/uboot/0004-riscv-Rename-Andes-PLIC-to-PLICSW.patch
> 
> It looks mostly good. Could you however:
> 
>  (1) Add your Signed-off-by inside each of the U-Boot patches you are
>  introducing, as well as provide a link to where the patches were
>  downloaded from?

Will do, but the first patch:
0001-mmc-ftsdc010_mci-Support-DTS-of-ftsdc010-driver-for-.patch
is used in our production code only, and might not be upstreamed,
We will drop it once we updated the mmc driver in kernel.

>  (2) Remove the numbering in the U-Boot patch titles. I.e instead of
>  [PATCH 1/2], we want to see [PATCH]. Use "git format-patch -N" to not
>  have this numbering.

OK.

>  (3) Keep the correct BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_xxyz=y
>  option in the defconfig?

OK.

> With these changes, your patch will be ready to be applied.
> 
> Also, are those U-Boot changes going to be accepted in upstream U-Boot?

For 0002, here is the thread [1], it seems to be no common solution for
ARM and RISC-V based system, not sure what's the status right now.
The 0003 & 0004 have been merged recently, I'll remove them and bump
U-boot to newer revision.

[1] https://patchwork.ozlabs.org/project/uboot/patch/20210712035231.26475-1-bmeng.cn@gmail.com/

> Thanks!
> 
> Thomas
> -- 
> Thomas Petazzoni, CTO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com

Thanks for your review!

Best regards,
Peter Lin
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-11-06  4:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04  8:04 [Buildroot] [PATCH 1/1] andes_ae350_45_defconfig: bump opensbi, u-boot and linux Yu Chien Peter Lin
2022-11-05 21:08 ` Thomas Petazzoni via buildroot
2022-11-06 12:07   ` Yu-Chien Peter Lin [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=Y2ejY8/mrFd/AVi+@APC323 \
    --to=peterlin@andestech.com \
    --cc=buildroot@buildroot.org \
    --cc=dylan@andestech.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=tim609@andestech.com \
    --cc=ycliang@andestech.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