From: Tom Rini <trini@konsulko.com>
To: Francesco Dolcini <francesco@dolcini.it>,
Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Simon Glass <sjg@chromium.org>,
u-boot@lists.denx.de,
Marcel Ziswiler <marcel.ziswiler@toradex.com>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
Marek Vasut <marex@denx.de>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH v1 0/3] fdt: Fix mtparts fixup
Date: Fri, 13 Jan 2023 14:34:11 -0500 [thread overview]
Message-ID: <20230113193411.GW3787616@bill-the-cat> (raw)
In-Reply-To: <20230113184547.487322-1-francesco@dolcini.it>
[-- Attachment #1.1: Type: text/plain, Size: 1609 bytes --]
On Fri, Jan 13, 2023 at 07:45:44PM +0100, Francesco Dolcini wrote:
> From: Francesco Dolcini <francesco.dolcini@toradex.com>
>
> Recently we had a boot regression on colibri-imx7 because of a cleanup change
> on Linux imx7.dtsi setting nand controller node #size-cells from 1 to 0.
>
> Because of that Linux partition parser was no longer able to properly
> parse the OF partitions leading to a boot failure, the above change was
> reverted in the meantime as an immediate workaround, but some improvement
> is required on both Linux and U-Boot.
>
> This change improve the U-Boot part of it, #size-cell is set to 1 when
> it has an invalid value. This has the limitation to work only with devices
> smaller than 4GiB. In general the suggestion from the Linux MTD maintainer would
> be to just deprecate using this U-Boot function and pass the MTD partitions
> from the command line, unless they are statically defined in the DTS file
> in the first place.
>
> This series therefore convert colibri-imx6ull and colibri-imx7 to pass the
> partition list from the command line instead of fixing up the DT.
>
> Link: https://lore.kernel.org/all/20221202071900.1143950-1-francesco@dolcini.it/
> Link: https://lore.kernel.org/all/Y4dgBTGNWpM6SQXI@francesco-nb.int.toradex.com/
My higher level question / concern here is, is using one of the dts
partition schemes still valid / preferred, or should everyone now have
reverted to passing via the kernel command line? If device tree still,
is mtd/partitions/fixed-partitions.yaml the one to follow or something
else?
--
Tom
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
[-- Attachment #2: Type: text/plain, Size: 144 bytes --]
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2023-01-13 19:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 18:45 [PATCH v1 0/3] fdt: Fix mtparts fixup Francesco Dolcini
2023-01-13 18:45 ` [PATCH v1 1/3] fdt: validate/fix cells count on mtdpart fixup Francesco Dolcini
2023-01-15 14:35 ` Marek Vasut
2023-01-16 14:20 ` Francesco Dolcini
2023-01-16 17:54 ` Marek Vasut
2023-01-16 18:00 ` Francesco Dolcini
2023-01-17 0:59 ` Marek Vasut
2023-01-23 9:56 ` Miquel Raynal
2023-01-24 8:41 ` Francesco Dolcini
2023-01-24 8:58 ` Miquel Raynal
2023-01-24 10:24 ` Francesco Dolcini
2023-01-13 19:34 ` Tom Rini [this message]
2023-01-23 10:06 ` [PATCH v1 0/3] fdt: Fix mtparts fixup Miquel Raynal
2023-01-23 20:01 ` Tom Rini
2023-02-23 10:23 ` Patrick DELAUNAY
2023-02-23 22:35 ` Tom Rini
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=20230113193411.GW3787616@bill-the-cat \
--to=trini@konsulko.com \
--cc=francesco.dolcini@toradex.com \
--cc=francesco@dolcini.it \
--cc=linux-mtd@lists.infradead.org \
--cc=marcel.ziswiler@toradex.com \
--cc=marex@denx.de \
--cc=miquel.raynal@bootlin.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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