Skip to contentSkip to conversation

boot/riscv-pk: Remove obselete bootloader

PATCH Superseded Alistair Francis 4 participants 5 messages Sep 23, 2019 – Oct 8, 2019 RISC-V

v2 of 3 Superseded Latest is v3 →

lore
Share & tools
lore
#0 lore raw

PATCH v2 1/1 boot/riscv-pk: Remove obselete bootloader

The RISCV Proxy Kernel (AKA BBL) isn't being used by most distros so has very limited testing. It has been replaced by OpenSBI and been deprecated for awhile, so let's just remove it.

---
v2:
- Remove package from DEVELOPERS
- Add option to Config.in.legacy

 Config.in.legacy          |  7 +++++++
 DEVELOPERS                |  1 -
 boot/Config.in            |  1 -
 boot/riscv-pk/Config.in   | 17 -----------------
 boot/riscv-pk/riscv-pk.mk | 32 --------------------------------
 5 files changed, 7 insertions(+), 51 deletions(-)
 delete mode 100644 boot/riscv-pk/Config.in
 delete mode 100644 boot/riscv-pk/riscv-pk.mk
Config.in.legacy +7 -0
index b8b550e5ee..2bdc223ff9 100644
@@ -146,6 +146,13 @@ endif
 
 comment "Legacy options removed in 2019.11"
 
+config BR2_TARGET_RISCV_PK
+       bool "riscv-pk was removed"
+       select BR2_LEGACY
+       help
+         The RISC-V Proxy Kernel (pk) and Berkley Boot Loader (BBL) have
+         been replaced with OpenSBI.
+
 config BR2_PACKAGE_USTR
 	bool "ustr package removed"
 	select BR2_LEGACY
DEVELOPERS +0 -1
index b427fd92ae..0f19e1c2eb 100644
@@ -1469,7 +1469,6 @@ F:	arch/arch.mk.riscv
 F:	arch/Config.in.riscv
 F:	board/qemu/riscv32-virt/
 F:	board/qemu/riscv64-virt/
-F:	boot/riscv-pk/
 F:	configs/qemu_riscv32_virt_defconfig
 F:	configs/qemu_riscv64_virt_defconfig
 
boot/Config.in +0 -1
index ac1a997f00..b3adbfc8bc 100644
@@ -15,7 +15,6 @@ source "boot/mv-ddr-marvell/Config.in"
 source "boot/mxs-bootlets/Config.in"
 source "boot/optee-os/Config.in"
 source "boot/opensbi/Config.in"
-source "boot/riscv-pk/Config.in"
 source "boot/s500-bootloader/Config.in"
 source "boot/shim/Config.in"
 source "boot/syslinux/Config.in"
boot/riscv-pk/Config.in deleted +0 -17
deleted file mode 100644
index cf9c5cd8ee..0000000000
@@ -1,17 +0,0 @@
-comment "riscv-pk needs a Linux kernel to be built"
-	depends on BR2_riscv
-	depends on !BR2_LINUX_KERNEL
-
-config BR2_TARGET_RISCV_PK
-	bool "riscv-pk (deprecated)"
-	depends on BR2_riscv
-	depends on BR2_LINUX_KERNEL
-	help
-	  The RISC-V Proxy Kernel (pk) and Boot Loader (BBL) have
-	  been deprecated. Please use OpenSBI instead.
-
-	  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.
-
-	  https://github.com/riscv/riscv-pk.git
boot/riscv-pk/riscv-pk.mk deleted +0 -32
deleted file mode 100644
index 0ab5879ee4..0000000000
@@ -1,32 +0,0 @@
-################################################################################
-#
-# riscv-pk
-#
-################################################################################
-
-RISCV_PK_VERSION = 706cc77c369fd3e4734b5a6aa813d421347f1814
-RISCV_PK_SITE = git://github.com/riscv/riscv-pk.git
-RISCV_PK_LICENSE = BSD-3-Clause
-RISCV_PK_LICENSE_FILES = LICENSE
-RISCV_PK_DEPENDENCIES = linux
-RISCV_PK_SUBDIR = build
-RISCV_PK_INSTALL_IMAGES = YES
-
-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 \
-	)
-endef
-
-define RISCV_PK_BUILD_CMDS
-	$(TARGET_MAKE_ENV) $(MAKE) -C $(@D)/build bbl
-endef
-
-define RISCV_PK_INSTALL_IMAGES_CMDS
-	$(INSTALL) -D -m 0755 $(@D)/build/bbl $(BINARIES_DIR)/bbl
-endef
-
-$(eval $(generic-package))
Signature · 1 line
2.23.0
#1 lore raw

PATCH v2 1/1 boot/riscv-pk: Remove obselete bootloader

Quoted 9 lines · On Mon, 23 Sep 2019 13:02:56 -0700 Alistair Francis <[email protected]>…

The RISCV Proxy Kernel (AKA BBL) isn't being used by most distros so has very limited testing. It has been replaced by OpenSBI and been deprecated for awhile, so let's just remove it.

---
v2:
- Remove package from DEVELOPERS
- Add option to Config.in.legacy

I'd like to have a Acked-by from Mark Corbin on this patch. Mark ?

Thanks!

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
#2 lore raw

PATCH v2 1/1 boot/riscv-pk: Remove obselete bootloader

Hello
?

Quoted 7 lines · Thomas Petazzoni
Quoted 4 lines · On Mon, 23 Sep 2019 13:02:56 -0700 Alistair Francis <[email protected]>…

The RISCV Proxy Kernel (AKA BBL) isn't being used by most distros so has very limited testing. It has been replaced by OpenSBI and been deprecated for awhile, so let's just remove it.

Quoted 6 lines
Quoted 5 lines

---
v2:
- Remove package from DEVELOPERS
- Add option to Config.in.legacy

I'd like to have a Acked-by from Mark Corbin on this patch. Mark ?

I'm in two minds about removing the BBL bootloader at the moment...

...on one hand I can see that OpenSBI should be used for all RISC-V projects going forward, but on the other hand there still seem to be a number of RISC-V projects that are using riscv-pk /BBL (and Buildroot), e.g. Ariane/OpenPiton, Shakti C-class and LowRISC (for Rocket core). Keeping BBL support within Buildroot at least gives people a smoother upgrade path, i.e. riscv-pk + Buildroot -> Buildroot (with integrated riscv-pk) -> Buildroot (with integrated OpenSBI).

I know that most 'desktop' distros are moving, or are planning to move, to OpenSBI, but I'm not so sure about the situation for people working with softcores/FPGAs or more deeply embedded systems.

Thoughts?

Mark

Signature · 3 lines
Mark Corbin
Embecosm Ltd.
https://www.embecosm.com
#3 lore raw

PATCH v2 1/1 boot/riscv-pk: Remove obselete bootloader

Quoted 16 lines · Mark Corbin

Hello

Quoted 12 lines · Thomas Petazzoni
Quoted 9 lines · On Mon, 23 Sep 2019 13:02:56 -0700 Alistair Francis <[email protected]>…

The RISCV Proxy Kernel (AKA BBL) isn't being used by most distros so has very limited testing. It has been replaced by OpenSBI and been deprecated for awhile, so let's just remove it.

---
v2:
- Remove package from DEVELOPERS
- Add option to Config.in.legacy

Quoted 8 lines
Quoted 1 line

I'd like to have a Acked-by from Mark Corbin on this patch. Mark ?

I'm in two minds about removing the BBL bootloader at the moment...

...on one hand I can see that OpenSBI should be used for all RISC-V projects going forward, but on the other hand there still seem to be a number of RISC-V projects that are using riscv-pk /BBL (and Buildroot), e.g. Ariane/OpenPiton, Shakti C-class and LowRISC (for Rocket core).

OpenSBI supports Ariane: https://github.com/riscv/opensbi/tree/master/platform

Although buildroot doesn't have configs for all of these platforms.

Quoted 3 lines

Keeping BBL support within Buildroot at least gives people a smoother upgrade path, i.e. riscv-pk + Buildroot -> Buildroot (with integrated riscv-pk) -> Buildroot (with integrated OpenSBI).

The main problem with keeping it is that it's not maintained and as other software keeps moving forward there will be compatibility issues that won't be obvious to people. For example some new kernel thing that relies on the firmware to behave in some way and BBL won't do that. As the SBI spec is updated this will also be an issue.

Quoted 4 lines

I know that most 'desktop' distros are moving, or are planning to move, to OpenSBI, but I'm not so sure about the situation for people working with softcores/FPGAs or more deeply embedded systems.

Most distros in general have moved on, not just the traditional desktop distros. SiFive have moved away from it and the last real commit to the repo was in August.

We haven't removed it from any existing buildroot releases, so anyone who has locked into a release can continue to use it. This will just stop new projects from starting with it and help convince people to swap.

Alistair

Quoted 14 lines

Thoughts?

Mark

--
Mark Corbin
Embecosm Ltd.
https://www.embecosm.com

_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

#4 lore raw

PATCH v2 1/1 boot/riscv-pk: Remove obselete bootloader

Hello Alistair

Quoted 43 lines · Alistair Francis
Quoted 15 lines · Mark Corbin

Hello

Quoted 12 lines · Thomas Petazzoni
Quoted 9 lines · On Mon, 23 Sep 2019 13:02:56 -0700 Alistair Francis <[email protected]>…

The RISCV Proxy Kernel (AKA BBL) isn't being used by most distros so has very limited testing. It has been replaced by OpenSBI and been deprecated for awhile, so let's just remove it.

---
v2:
- Remove package from DEVELOPERS
- Add option to Config.in.legacy

Quoted 7 lines
Quoted 1 line

I'd like to have a Acked-by from Mark Corbin on this patch. Mark ?

I'm in two minds about removing the BBL bootloader at the moment...

...on one hand I can see that OpenSBI should be used for all RISC-V projects going forward, but on the other hand there still seem to be a number of RISC-V projects that are using riscv-pk /BBL (and Buildroot), e.g. Ariane/OpenPiton, Shakti C-class and LowRISC (for Rocket core).

OpenSBI supports Ariane: https://github.com/riscv/opensbi/tree/master/platform

Although buildroot doesn't have configs for all of these platforms.

Quoted 3 lines

Keeping BBL support within Buildroot at least gives people a smoother upgrade path, i.e. riscv-pk + Buildroot -> Buildroot (with integrated riscv-pk) -> Buildroot (with integrated OpenSBI).

The main problem with keeping it is that it's not maintained and as other software keeps moving forward there will be compatibility issues that won't be obvious to people. For example some new kernel thing that relies on the firmware to behave in some way and BBL won't do that. As the SBI spec is updated this will also be an issue.

Quoted 3 lines

I know that most 'desktop' distros are moving, or are planning to move, to OpenSBI, but I'm not so sure about the situation for people working with softcores/FPGAs or more deeply embedded systems.

Most distros in general have moved on, not just the traditional desktop distros. SiFive have moved away from it and the last real commit to the repo was in August.

Quoted 6 lines

We haven't removed it from any existing buildroot releases, so anyone who has locked into a release can continue to use it. This will just stop new projects from starting with it and help convince people to swap.

Alistair

Thanks for the update. Makes sense to remove it.

Please could you re-send with tabs instead of spaces in Config.in.legacy.

Thanks

Mark

Signature · 3 lines
Mark Corbin
Embecosm Ltd.
https://www.embecosm.com