While specifying the barebox environment within the barebox dts is very
helpful for standalone barebox development it's difficult for BSPs which
use this development platform and want to use the GPT mechanism.
As a result BSPs had to manually delete the nodes via a external
provided dts, because we wanted to keep the comfort for the standalone
development flow.
Lucky commit 86531d4bf7aa ("commands: create createnv command")
introduced a convenient helper to create a barebox environemnt on
demand exactly for this purpose:
| "We want to move away from describing the barebox environment explicitly
| in the device tree and instead motivate usage of GPT partitions.."
So start with the i.MX8MP-EVK to encourage the use of GPT partitions and
to make the BSP integration for these development platforms easier.
Signed-off-by: Marco Felsch <[email protected]>
---
arch/arm/dts/imx8mp-evk.dts | 43 -------------------------------------
1 file changed, 43 deletions(-)
diff --git a/arch/arm/dts/imx8mp-evk.dts b/arch/arm/dts/imx8mp-evk.dts
index e6f8c2d1b482..37798fa99efa 100644
--- a/arch/arm/dts/imx8mp-evk.dts
+++ b/arch/arm/dts/imx8mp-evk.dts
@@ -12,19 +12,6 @@
/ {
barebox,deep-probe;
- chosen {
- environment-sd {
- compatible = "barebox,environment";
- device-path = &env_sd2;
- status = "disabled";
- };
- environment-emmc {
- compatible = "barebox,environment";
- device-path = &env_sd3;
- status = "disabled";
- };
- };
-
gpio-leds {
status {
barebox,default-trigger = "heartbeat";
@@ -78,33 +65,3 @@ &usb_dwc3_0 {
usb-role-switch;
status = "okay";
};
-
-&usdhc2 {
- #address-cells = <1>;
- #size-cells = <1>;
-
- partition@0 {
- label = "barebox";
- reg = <0x0 0xe0000>;
- };
-
- env_sd2: partition@e0000 {
- label = "barebox-environment";
- reg = <0xe0000 0x20000>;
- };
-};
-
-&usdhc3 {
- #address-cells = <1>;
- #size-cells = <1>;
-
- partition@0 {
- label = "barebox";
- reg = <0x0 0xe0000>;
- };
-
- env_sd3: partition@e0000 {
- label = "barebox-environment";
- reg = <0xe0000 0x20000>;
- };
-};
--
2.47.3
