From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 183A9C4338F for ; Thu, 29 Jul 2021 11:18:10 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id EDF9A60F0F for ; Thu, 29 Jul 2021 11:18:09 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236642AbhG2LSL (ORCPT ); Thu, 29 Jul 2021 07:18:11 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42856 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236312AbhG2LSL (ORCPT ); Thu, 29 Jul 2021 07:18:11 -0400 Received: from mail-ej1-x629.google.com (mail-ej1-x629.google.com [IPv6:2a00:1450:4864:20::629]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 22722C061765 for ; Thu, 29 Jul 2021 04:18:07 -0700 (PDT) Received: by mail-ej1-x629.google.com with SMTP id go31so10049746ejc.6 for ; Thu, 29 Jul 2021 04:18:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vanguardiasur-com-ar.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=65ZwwJqLgs4c9HtCALozYsS5NsihCPZf/ynWKHwUyR8=; b=KzMZFRO6hmvgYKId5o3d7SOQb8EMTg17Lt7c87ajkq3mxdsrAnZuzjd78zV0hB5Ak3 RuFRi/DPGHSeLWQzsrOq8Zd1HeQ2O8CeHk0XTbJtxEGCyWC7asw5mHDbHXgFdTiXRE8N XGJ29IMNwRmw0twXFXZkQcrCvoXJLz/XngDGdADdW7jHpe+J/6pruVphVa6LRvJHmewK /hLCmSB0eIdXXBmW5mIucvOw2q31pAjUa8YFBq2I3h02fldHSdy2aqyUcFe2mihrB1eG TDt65ZvGSiD1eIJ7QY4RhbmAuF26F2phzx/LqqecLEDMpBbsu5/2f6HBamAYpIiIctO0 VfGg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=65ZwwJqLgs4c9HtCALozYsS5NsihCPZf/ynWKHwUyR8=; b=rpXLjT/QFhOcBAKGYSdI9zexUSJhBX0CgyhqcsqIz7Va9gOShFixt/HAG/U+pVRp11 DRAR+Qqp9mLwi9tZFX2gYpeonznwKJUEDnoBAQMj7f3aa09IfMfJwgdeMKucowv848aD hrJ6ht03xG3Pu5jXMu3V7MZ2EJJvkO11/WlON/UfGYzrGPopS6nX8Y9R8eDcwtUkemN+ 4inRppJCijeZoaWNJxvv5gv7W2xH9iA0KGFEUNn8Bnqa+tqqGgDmnf+ufkWgmzmCXc1H xDLd5Q9qQQZqt3JZS+eecmppXLF7cqvsemkHFmM6lbwCJo7ZbSlO+UAsEPagJN8qmbQX cfSQ== X-Gm-Message-State: AOAM530prsa5SvIQXaXHAPpUZCHO0/FfZO94d/GqCIH+jy1zdU4noR8P viZWpofU4J0pou7mNbbgdkefgevYlknXXTc7h3FY9Q== X-Google-Smtp-Source: ABdhPJySfQ1NPMpN+/lsPjW164mn0r8d3REf4kf9pWPQ8yyRotEZCYiRLEJVSRNfO8LG3+VSGEByagnqdZ8GMYanqTw= X-Received: by 2002:a17:906:4fd6:: with SMTP id i22mr4214483ejw.92.1627557485657; Thu, 29 Jul 2021 04:18:05 -0700 (PDT) MIME-Version: 1.0 References: <568938486.33366.1626452816917.JavaMail.zimbra@nod.at> <1458549943.44607.1626686894648.JavaMail.zimbra@nod.at> <1556211076.48404.1626763215205.JavaMail.zimbra@nod.at> <2132615832.4458.1626900868118.JavaMail.zimbra@nod.at> In-Reply-To: From: Ezequiel Garcia Date: Thu, 29 Jul 2021 08:17:53 -0300 Message-ID: Subject: Re: MTD: How to get actual image size from MTD partition To: Richard Weinberger Cc: Pintu Agarwal , Richard Weinberger , Kernelnewbies , Greg KH , linux-kernel , linux-mtd , Sean Nyekjaer , linux-fsdevel , Phillip Lougher Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org Hi Richard, On Tue, 27 Jul 2021 at 18:16, Richard Weinberger wrote: > > On Thu, Jul 22, 2021 at 1:11 PM Pintu Agarwal wrot= e: > > > > On Thu, 22 Jul 2021 at 02:24, Richard Weinberger wrote= : > > > > > > ----- Urspr=C3=BCngliche Mail ----- > > > >> But let me advertise ubiblock a second time. > > > > Sorry, I could not understand about the ubiblock request. Is it > > > > possible to elaborate little more ? > > > > We are already using squashfs on top of our UBI volumes (including > > > > rootfs mounting). > > > > This is the kernel command line we pass: > > > > rootfstype=3Dsquashfs root=3D/dev/mtdblock44 ubi.mtd=3D40,0,30 > > > > And CONFIG_MTD_UBI_BLOCK=3Dy is already enabled in our kernel. > > > > Do we need to do something different for ubiblock ? > > > > > > From that command line I understand that you are *not* using squashfs= on top of UBI. > > > You use mtdblock. ubiblock is a mechanism to turn an UBI volume into = a read-only > > > block device. > > > See: http://www.linux-mtd.infradead.org/doc/ubi.html#L_ubiblock > > > [snip] Ouch, so surprised that after all these years someone is doing squashfs/mtd= block instead of using ubiblock :-) Can we patch either Kconfig or add some warn_once on mtdblock usage, suggesting to use ubiblock instead? I remember there was still some use case(s) for mtdblock but I can't rememb= er now what was it, perhaps we should document the expectations? (Is that for JFFS2 to mount?) Thanks, Ezequiel