[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1668790824.35266.1627559144878.JavaMail.zimbra@nod.at>
Date: Thu, 29 Jul 2021 13:45:44 +0200 (CEST)
From: Richard Weinberger <richard@....at>
To: Ezequiel Garcia <ezequiel@...guardiasur.com.ar>
Cc: Pintu Agarwal <pintu.ping@...il.com>,
Kernelnewbies <kernelnewbies@...nelnewbies.org>,
Greg KH <greg@...ah.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-mtd <linux-mtd@...ts.infradead.org>,
Sean Nyekjaer <sean@...nix.com>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Phillip Lougher <phillip@...ashfs.org.uk>
Subject: Re: MTD: How to get actual image size from MTD partition
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
Powered by blists - more mailing lists