From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 5/6] boot/riscv-pk: add bootloader for RISC-V architecture
Date: Tue, 25 Sep 2018 22:08:40 +0200 [thread overview]
Message-ID: <20180925220840.562695d8@windsurf> (raw)
In-Reply-To: <20180912102256.3164-6-mark.corbin@embecosm.com>
Hello,
On Wed, 12 Sep 2018 11:22:55 +0100, Mark Corbin wrote:
> Add the RISC-V Proxy Kernel (pk) package which provides the Berkeley
> Boot Loader for booting RISC-V kernel images.
>
> Signed-off-by: Mark Corbin <mark.corbin@embecosm.com>
I have applied, after doing some minor changes, see below.
> diff --git a/boot/riscv-pk/Config.in b/boot/riscv-pk/Config.in
> new file mode 100644
> index 0000000000..ec49f6aa6d
> --- /dev/null
> +++ b/boot/riscv-pk/Config.in
> @@ -0,0 +1,13 @@
> +comment "riscv-pk (BBL) needs a Linux kernel to be built"
Changed to just "riscv-pk needs ..."
> + depends on BR2_riscv
> + depends on !BR2_LINUX_KERNEL
> +
> +config BR2_TARGET_RISCV_PK
> + bool "riscv-pk (BBL)"
Changed to just "riscv-pk"
For both changes: our policy is to try to stick to the upstream package
name in the Config.in prompt and comments.
> + depends on BR2_riscv
> + depends on BR2_LINUX_KERNEL
> + help
> + The RISC-V Proxy Kernel (pk) package contains the Berkeley
> + Boot Loader (BBL) which has been designed to boot a Linux
> + kernel on a RISC-V processor.
I've added a missing blank line here.
> + https://github.com/riscv/riscv-pk.git
> +define RISCV_PK_CONFIGURE_CMDS
> + mkdir -p $(@D)/build
> + (cd $(@D)/build; \
> + $(TARGET_CONFIGURE_OPTS) ../configure \
> + --host=$(GNU_TARGET_NAME) \
> + --with-payload=$(BINARIES_DIR)/vmlinux \
I fixed a bit the indentation here.
> + )
> +endef
> +
> +define RISCV_PK_BUILD_CMDS
> + $(TARGET_MAKE_ENV) $(MAKE) \
> + -C $(@D)/build bbl
Changed this to be on one single line.
> +endef
> +
> +define RISCV_PK_INSTALL_IMAGES_CMDS
> + cp $(@D)/build/bbl $(BINARIES_DIR)
And changed to:
$(INSTALL) -D -m 0755 $(@D)/build/bbl $(BINARIES_DIR)/bbl
Thanks again for this contribution!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-09-25 20:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 10:22 [Buildroot] [PATCH v2 0/6] Add RISC-V 64-bit architecture support Mark Corbin
2018-09-12 10:22 ` [Buildroot] [PATCH v2 1/6] linux: add hash file Mark Corbin
2018-09-23 19:21 ` Thomas Petazzoni
2018-09-23 19:39 ` Fabio Estevam
2018-09-12 10:22 ` [Buildroot] [PATCH v2 2/6] package/linux-headers: add support for custom headers Mark Corbin
2018-09-12 15:23 ` Thomas Petazzoni
2018-09-23 20:12 ` Thomas Petazzoni
2018-09-12 10:22 ` [Buildroot] [PATCH v2 3/6] arch: allow GCC target options to be optionally overwritten Mark Corbin
2018-09-23 20:33 ` Thomas Petazzoni
2018-09-12 10:22 ` [Buildroot] [PATCH v2 4/6] arch: add support for RISC-V 64-bit (riscv64) architecture Mark Corbin
2018-09-12 15:21 ` Thomas Petazzoni
2018-09-25 20:06 ` Thomas Petazzoni
2018-09-12 10:22 ` [Buildroot] [PATCH v2 5/6] boot/riscv-pk: add bootloader for RISC-V architecture Mark Corbin
2018-09-25 20:08 ` Thomas Petazzoni [this message]
2018-09-12 10:22 ` [Buildroot] [PATCH v2 6/6] configs/qemu: add qemu_riscv64_virt_defconfig Mark Corbin
2018-09-25 20:10 ` Thomas Petazzoni
2018-09-12 15:18 ` [Buildroot] [PATCH v2 0/6] Add RISC-V 64-bit architecture support Thomas Petazzoni
2018-09-12 16:14 ` Mark Corbin
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=20180925220840.562695d8@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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