From: Wolfram Sang <wsa@kernel.org>
To: barebox@lists.infradead.org
Cc: Wolfram Sang <wsa@kernel.org>
Subject: [PATCH 1/2] ARM: at91: usb-a926x: remove nand partitions from config
Date: Thu, 27 Apr 2023 20:47:17 +0200 [thread overview]
Message-ID: <20230427184718.105393-2-wsa@kernel.org> (raw)
In-Reply-To: <20230427184718.105393-1-wsa@kernel.org>
We define partitions as well in the board file. Leading to:
New partition nand0.at91bootstrap (0x00000000-0x0001ffff) on nand0 overlaps with partition at91bootstrap_raw (0x00000000-0x0001ffff), not creating it
cannot create nand0.at91bootstrap: Invalid argument
addpart: Invalid argument
So, remove it from the config file.
Signed-off-by: Wolfram Sang <wsa@kernel.org>
---
Or shall I rather remove it from the board file?
arch/arm/boards/usb-a926x/defaultenv-usb-a926x/config | 4 ----
1 file changed, 4 deletions(-)
diff --git a/arch/arm/boards/usb-a926x/defaultenv-usb-a926x/config b/arch/arm/boards/usb-a926x/defaultenv-usb-a926x/config
index 49199ba391..f9159cb946 100644
--- a/arch/arm/boards/usb-a926x/defaultenv-usb-a926x/config
+++ b/arch/arm/boards/usb-a926x/defaultenv-usb-a926x/config
@@ -29,10 +29,6 @@ kernelimage=zImage
#kernelimage=Image
#kernelimage=Image.lzo
-nand_device=atmel_nand
-nand_parts="128k(at91bootstrap),256k(barebox)ro,128k(bareboxenv),128k(bareboxenv2),128k(oftree),4M(kernel),120M(rootfs),-(data)"
-rootfs_mtdblock_nand=6
-
autoboot_timeout=3
bootargs="console=ttyS0,115200"
--
2.35.1
next prev parent reply other threads:[~2023-04-27 18:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 18:47 [PATCH 0/2] ARM: at91: usb-a9g20: make it work out of the box again Wolfram Sang
2023-04-27 18:47 ` Wolfram Sang [this message]
2023-05-02 11:43 ` [PATCH 1/2] ARM: at91: usb-a926x: remove nand partitions from config Sascha Hauer
2023-04-27 18:47 ` [PATCH 2/2] defconfigs: usb-a9g20: update to a working version Wolfram Sang
2023-05-02 11:42 ` [PATCH 0/2] ARM: at91: usb-a9g20: make it work out of the box again Sascha Hauer
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=20230427184718.105393-2-wsa@kernel.org \
--to=wsa@kernel.org \
--cc=barebox@lists.infradead.org \
/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