From: Andy Shevchenko <andy@kernel.org>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>, Jonathan Corbet <corbet@lwn.net>,
Ulf Hansson <ulf.hansson@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Kees Cook <kees@kernel.org>,
Daniel Golle <daniel@makrotopia.org>,
INAGAKI Hiroshi <musashino.open@gmail.com>,
Christian Brauner <brauner@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Li Lingfeng <lilingfeng3@huawei.com>,
Ming Lei <ming.lei@redhat.com>,
Christian Heusel <christian@heusel.eu>,
linux-block@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
devicetree@vger.kernel.org, linux-hardening@vger.kernel.org,
Miquel Raynal <miquel.raynal@bootlin.com>,
Lorenzo Bianconi <lorenzo@kernel.org>,
upstream@airoha.com
Subject: Re: [PATCH v4 0/5] block: partition table OF support
Date: Mon, 30 Sep 2024 15:54:04 +0300 [thread overview]
Message-ID: <ZvqfbNDfI2QWZEBg@smile.fi.intel.com> (raw)
In-Reply-To: <20240930113045.28616-1-ansuelsmth@gmail.com>
On Mon, Sep 30, 2024 at 01:30:07PM +0200, Christian Marangi wrote:
> Hi,
> this is an initial proposal to complete support for manually defining
> partition table.
>
> Some background on this. Many OEM on embedded device (modem, router...)
> are starting to migrate from NOR/NAND flash to eMMC. The reason for this
> is that OEM are starting to require more and more space for the firmware
> and price difference is becoming so little that using eMMC is only benefits
> and no cons.
>
> Given these reason, OEM are also using very custom way to provide a
> partition table and doesn't relay on common method like writing a table
> on the eMMC.
>
> One way that is commonly used is to hardcode the partition table and
> pass it to the system via various way (cmdline, special glue driver,
> block2mtd...)
> This way is also used on Android where the partition table
> is passed from the bootloader via cmdline.
>
> One reason to use this method is to save space on the device and to
> permit more flexibility on partition handling.
>
> What this series does is complete support for this feature.
> It's possible to use the cmdline to define a partition table similar
> to how it's done for MTD but this is problematic for a number of device
> where tweaking the cmdline is not possible. This series adds OF support
> to make it possible to define a partition table in the Device Tree.
>
> We implement a similar schema to the MTD fixed-partition, where we define
> a "label" and a "reg" with "offset" and "size".
>
> A new block partition parser is introduced that check if the block device
> have an OF node attached and check if a fixed-partition table is defined.
>
> If a correct node is found, then partition table is filled. cmdline will
> still have priority to this new parser.
>
> Some block device also implement boot1 and boot2 additional disk. Similar
> to the cmdline parser, these disk can have OF support using the
> "partitions-boot0" and "partitions-boot1" additional node.
>
> It's also completed support for declaring partition as read-only as this
> feature was introduced but never finished in the cmdline parser.
I'm not sure I fully understood the problem you are trying to solve.
I have a device at hand that uses eMMC (and was produced almost ten years ago).
This device has a regular GPT on eMMC and no kernel needs to be patched for that.
So, why is it a problem for the mentioned OEMs to use standard GPT approach?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-09-30 12:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 11:30 [PATCH v4 0/5] block: partition table OF support Christian Marangi
2024-09-30 11:30 ` [PATCH v4 1/5] block: add support for defining read-only partitions Christian Marangi
2024-09-30 11:30 ` [PATCH v4 2/5] docs: block: Document support for read-only partition in cmdline part Christian Marangi
2024-09-30 11:30 ` [PATCH v4 3/5] string: add strends() helper to check if a string ends with a suffix Christian Marangi
2024-09-30 12:45 ` Andy Shevchenko
2024-10-01 14:33 ` kernel test robot
2024-10-01 21:47 ` kernel test robot
2024-09-30 11:30 ` [PATCH v4 4/5] block: add support for partition table defined in OF Christian Marangi
2024-09-30 12:49 ` Andy Shevchenko
2024-09-30 11:30 ` [PATCH v4 5/5] dt-bindings: mmc: Document support for partition table in mmc-card Christian Marangi
2024-09-30 12:18 ` Rasmus Villemoes
2024-09-30 12:22 ` Christian Marangi
2024-09-30 14:00 ` Rasmus Villemoes
2024-09-30 12:54 ` Andy Shevchenko [this message]
2024-10-02 9:20 ` [PATCH v4 0/5] block: partition table OF support Rasmus Villemoes
2024-10-03 9:59 ` Andy Shevchenko
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=ZvqfbNDfI2QWZEBg@smile.fi.intel.com \
--to=andy@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=christian@heusel.eu \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@makrotopia.org \
--cc=devicetree@vger.kernel.org \
--cc=kees@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lilingfeng3@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=ming.lei@redhat.com \
--cc=miquel.raynal@bootlin.com \
--cc=musashino.open@gmail.com \
--cc=robh@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=upstream@airoha.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).