From: Sam Edwards <cfsworks@gmail.com>
To: hs@denx.de, Simon Glass <sjg@chromium.org>
Cc: u-boot@lists.denx.de, Kyungmin Park <kmpark@infradead.org>
Subject: Re: [RFC PATCH 0/4] mtd: ubi: Enable accessing RO filesystems in UBI vols
Date: Thu, 7 Sep 2023 15:46:09 -0600 [thread overview]
Message-ID: <1e85f9ce-f3df-fb56-9855-59fb7cb70a67@gmail.com> (raw)
In-Reply-To: <5e986e31-388b-3e48-2a48-04bbd61651f0@denx.de>
Hi Heiko and Simon,
Thought I'd follow-up to keep this discussion going. The main thing I
would like to decide first (as it lets me start relying on it in boot
scripts) would be the UBI access syntax:
=> ls ubi 0:rootfs /boot
=> ls ubi 0:2 /boot
Do those look good? Should I be trying to mimic the accepted syntax of
fs/ubifs/super.c:open_ubi()? Perhaps "ubi 0!rootfs" and/or "ubi 0_2"?
Not using ':' leaves open the possibility for logical volumes (LVM2/UBI)
to contain partitions - not that I expect anyone will want that. :)
Cheers,
Sam
next prev parent reply other threads:[~2023-09-07 21:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 0:06 [RFC PATCH 0/4] mtd: ubi: Enable accessing RO filesystems in UBI vols Sam Edwards
2023-08-12 0:06 ` [RFC PATCH 1/4] mtd: ubi: register UBI attachments as DM devices Sam Edwards
2023-08-12 0:06 ` [RFC PATCH 2/4] mtd: ubi: bind block device driver for static volumes Sam Edwards
2023-08-12 0:06 ` [RFC PATCH 3/4] disk: part: fall-through if "ubi" requested but ubifs not mounted Sam Edwards
2023-08-12 0:06 ` [RFC PATCH 4/4] HACK: enable access to `ubi 0:volname` block devices Sam Edwards
2023-08-14 6:45 ` [RFC PATCH 0/4] mtd: ubi: Enable accessing RO filesystems in UBI vols Heiko Schocher
2023-09-07 21:46 ` Sam Edwards [this message]
2023-09-21 6:44 ` Heiko Schocher
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=1e85f9ce-f3df-fb56-9855-59fb7cb70a67@gmail.com \
--to=cfsworks@gmail.com \
--cc=hs@denx.de \
--cc=kmpark@infradead.org \
--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