From: Richard Weinberger <richard@nod.at>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Cc: Pintu Agarwal <pintu.ping@gmail.com>,
Kernelnewbies <kernelnewbies@kernelnewbies.org>,
Greg KH <greg@kroah.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mtd <linux-mtd@lists.infradead.org>,
Sean Nyekjaer <sean@geanix.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Phillip Lougher <phillip@squashfs.org.uk>
Subject: Re: MTD: How to get actual image size from MTD partition
Date: Thu, 29 Jul 2021 13:45:44 +0200 (CEST) [thread overview]
Message-ID: <1668790824.35266.1627559144878.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <CAAEAJfCY+X-G=7Oe9NqrJ4yQZ29DBA78jOFAX44GD0g6=s7qhg@mail.gmail.com>
Ezequiel,
----- Ursprüngliche Mail -----
> [snip]
>
> Ouch, so surprised that after all these years someone is doing squashfs/mtdblock
> instead of using ubiblock :-)
>
> Can we patch either Kconfig or add some warn_once on mtdblock
> usage, suggesting to use ubiblock instead?
a hint in Kconfig makes IMHO sense. Do you want to send a patch?
A warning is too much since on some tiny embedded system with NOR flash mtdblock is still
a good choice.
ubiblock is mostly useful for NAND flash.
> I remember there was still some use case(s) for mtdblock but I can't remember
> now what was it, perhaps we should document the expectations?
> (Is that for JFFS2 to mount?)
a long time ago mount didn't accept character devices, so you had to pass mtdblockX to mount
JFFS2.
This limitation is gone.
Thanks,
//richard
next prev parent reply other threads:[~2021-07-29 11:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 6:42 MTD: How to get actual image size from MTD partition Pintu Agarwal
2021-07-16 7:16 ` Richard Weinberger
2021-07-16 15:41 ` Greg KH
2021-07-16 16:26 ` Richard Weinberger
2021-07-19 9:09 ` Pintu Agarwal
2021-07-19 9:28 ` Richard Weinberger
2021-07-20 6:17 ` Pintu Agarwal
2021-07-20 6:40 ` Richard Weinberger
2021-07-20 8:01 ` Pintu Agarwal
2021-07-21 20:54 ` Richard Weinberger
2021-07-22 11:10 ` Pintu Agarwal
2021-07-27 21:16 ` Richard Weinberger
2021-07-29 11:17 ` Ezequiel Garcia
2021-07-29 11:45 ` Richard Weinberger [this message]
2021-07-29 12:03 ` Ezequiel Garcia
2021-07-29 17:11 ` Pintu Agarwal
2021-08-20 18:24 ` Pintu Agarwal
2021-08-22 14:21 ` Ezequiel Garcia
2021-08-30 15:58 ` Pintu Agarwal
2021-10-29 16:12 ` Pintu Agarwal
2021-10-29 16:48 ` Ezequiel Garcia
2021-11-08 13:51 ` Pintu Agarwal
2021-11-12 13:58 ` Ezequiel Garcia
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=1668790824.35266.1627559144878.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=phillip@squashfs.org.uk \
--cc=pintu.ping@gmail.com \
--cc=sean@geanix.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 NNTP newsgroup(s).