From: Richard Weinberger <richard@nod.at>
To: Tomas Alvarez Vanoli <tomas.alvarez-vanoli@hitachienergy.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: specify root squashfs ubiblock by volume name
Date: Mon, 15 Apr 2024 21:06:52 +0200 (CEST) [thread overview]
Message-ID: <1423540685.195759.1713208012331.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <DB9PR06MB7849A67820F6FBA17FF20584C2092@DB9PR06MB7849.eurprd06.prod.outlook.com>
----- Ursprüngliche Mail -----
> I have an embedded system in which multiple rootfs are stored in an ubi device
> as squashfs ubi volumes.
> This is to be able to have fallback systems or to be able to store and run
> different versions of the software easily.
> Because the number and order of volumes in the ubi device can change (different
> configurations, optional log volume, etc),
> I have a small patch that allows me to specify the volume using “ubiblock:name”,
> which mirrors the already possible “ubi:name”,
> Instead of specifying the device name for the "root" boot argument.
>
> Is there already a way to do this that I may have overlooked?
Traditionally, I always suggest using a minimal initramfs as soon the rootfs setup
is non-trivial. But there are exceptions.
> If not, do you think this is a feature that would be accepted into mainline?
Depends on the changes.
In any case, please share your patch. It does not have to be perfect,
just mark it as RFC.
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2024-04-15 19:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 13:48 specify root squashfs ubiblock by volume name Tomas Alvarez Vanoli
2024-04-15 19:06 ` Richard Weinberger [this message]
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=1423540685.195759.1713208012331.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=tomas.alvarez-vanoli@hitachienergy.com \
--cc=vigneshr@ti.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).