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 8F58AC4338F for ; Thu, 29 Jul 2021 12:03:40 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6F4BE60E94 for ; Thu, 29 Jul 2021 12:03:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234790AbhG2MDm (ORCPT ); Thu, 29 Jul 2021 08:03:42 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53960 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234176AbhG2MDm (ORCPT ); Thu, 29 Jul 2021 08:03:42 -0400 Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D1940C0613C1 for ; Thu, 29 Jul 2021 05:03:38 -0700 (PDT) Received: by mail-ed1-x533.google.com with SMTP id x90so7833706ede.8 for ; Thu, 29 Jul 2021 05:03:38 -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=5PqNao+LvVur5nM0wboYYWnzsoVPqlHC4aLEUSYkRe8=; b=02vV/yQEakIkTyXZD9abAeEHvCDnuoT3A1ic1/OunC54FJGKkJBv1H4fRFMBQfMVAu XOWD5tkW64NqSq7N3sE4eO/bLCm6C1zfEEU41QavjbGTWmXdRXmw2jJlTTDgYoIx6gRC Ox3IUbvriQygZZGNbsph59saddP5WR38z1DwF2MspP5WeDgoT/etD7cnTvKA/lbGcM9U g5wMzPlxtgqYoJPoteQwQOlqHmvFgkFRqWNPWc538vHyeSpwxuCIKPCX4/A6P00o7q4D UEazoOYyFYjOuOcR2DG+i7Q5enWsikDluSgPSe728mrbExGIZYzw9XZMwSwh5V/qL8Iw xNcg== 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=5PqNao+LvVur5nM0wboYYWnzsoVPqlHC4aLEUSYkRe8=; b=ZI2iv/ZN7khx4jvDg/slsHm5KZI3RGAhpOdmzVoIHKh8182LhcfCB8i7Jo7LWvslIS rhkGrSj1diMfONfngfK+p781QE7JLm7lqdAzimb9EvxTwPQ4g+yKJZBi+odI8c5M44gS B3gy5qUN08hA98UpzWudfVDeRsuS1g8l36AeLQq5jAejU+mJegzGEaWVXEBGCKdgPrgw BhI13E8Zt8oZCPbX++NQfuIJqZ5i1QjuMaC7YKEpUPxv4jH8Gw8DxcSh1+9/wRUAW8Dl E79AmlnSB0EqkxxFgPUNlQNmWUCYFy9C0Rg6AE5W/Ii1r0JWOolN6ASHE9KH4+tkIr23 q2kg== X-Gm-Message-State: AOAM533BJUWn/2CyrNzkp9e7FHLRWDk5QyY6X8TBNdSi0MhsgkJoUDFl ncTcFiWhgGpD78BDJ39FHi8oJQ5ZfRf2Y/alEP0JkQ== X-Google-Smtp-Source: ABdhPJymcivsFGziq0SihV2i9nQXby5NtNXxaA1zhexuwQiwuYRDZBTYJQxO3n4NHJjRLJ2SOyCIu3Zhu+e9V+8nE7I= X-Received: by 2002:a05:6402:4c5:: with SMTP id n5mr5580197edw.322.1627560217516; Thu, 29 Jul 2021 05:03:37 -0700 (PDT) MIME-Version: 1.0 References: <1556211076.48404.1626763215205.JavaMail.zimbra@nod.at> <2132615832.4458.1626900868118.JavaMail.zimbra@nod.at> <1668790824.35266.1627559144878.JavaMail.zimbra@nod.at> In-Reply-To: <1668790824.35266.1627559144878.JavaMail.zimbra@nod.at> From: Ezequiel Garcia Date: Thu, 29 Jul 2021 09:03:26 -0300 Message-ID: Subject: Re: MTD: How to get actual image size from MTD partition To: Richard Weinberger Cc: Pintu Agarwal , 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 On Thu, 29 Jul 2021 at 08:45, Richard Weinberger wrote: > > Ezequiel, > > ----- Urspr=C3=BCngliche 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 m= tdblock 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 re= member > > 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. > OK, let me try to cook a patch for you. Eze