Received: by 2002:a05:6a10:c7c6:0:0:0:0 with SMTP id h6csp1206732pxy; Sun, 1 Aug 2021 16:47:07 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz6K/xtogDATNmWwtSqXyQCmwX+BqLGE1vwMo5JJpk8uVz60mQefvrSv8U4gV+QAlzrqeaL X-Received: by 2002:a05:6402:3507:: with SMTP id b7mr16490108edd.293.1627861627651; Sun, 01 Aug 2021 16:47:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1627861627; cv=none; d=google.com; s=arc-20160816; b=NaaOuPErERqkTJfIRXghW1wf7VMjC2L0fL86mzI0K0knNKXhd/UppXByK7zJIYw1Sj ogiGksTS7ZjYYPNHaKK3bxc2PucS5fmnq3uqK+iEx42S0WU/CgwJHfbjKLvQXJbpixf/ bLJ5tuziOJTwj9khOzA9xvUiZalHAXLX42GdfbDyUMGVS0lkNZUllhmlAhNkzjbfUs5r 4O64M25dh3JpQTmYoasYbcx1JsEHf9r/ZEKnZwWCVgO0bI4FRGAx218+Kava1O4EdmCw 5vQCX6iRkbf9JEO2/2O1t+qUmDklN3e7K0qhDf09JzVVCn2i/+wBerFdLdlIC/PBpYek PRwA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=bwmc4oqgAHRIngbiu9rMxdNLPkuWN2CVMPxvjY30UjM=; b=zgnt+L3Eqd8ZcQ+p/VC1u1YxkZlsyYKIjgaXTu4ss9UlVBypG0yaO85xiPF1UDi1dQ XGixetGsXj9odtsYSdoQRTTMoBir2pZmirjL1IcDwB4YMzJUwEFmWWQZYaP4gJPPYwQR K/g8bBLIecG85UgUyLBn8JVelqYwu8mDb3CYbP9HcsEP04p2jAYo4edtgog5C6cEkIYY jQWJAhKYB9ZYTja5oDcWG/rgYUYbYEu8QvlD9wWGSVGO+a6D1ikpiIOr2knOvjcgeeaz bGQ4rt8mlpi6bkUAT3JojNUlyZZXbK9j3TlxNFof/m1HzILjFggEUqxH9l4JvEb+95ax Hikg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id u26si8223192ejr.374.2021.08.01.16.46.45; Sun, 01 Aug 2021 16:47:07 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231639AbhHAXpc (ORCPT + 99 others); Sun, 1 Aug 2021 19:45:32 -0400 Received: from bhuna.collabora.co.uk ([46.235.227.227]:50928 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231615AbhHAXpc (ORCPT ); Sun, 1 Aug 2021 19:45:32 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: ezequiel) with ESMTPSA id A23A21F424C8 From: Ezequiel Garcia To: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org, Richard Weinberger Cc: Miquel Raynal , Vignesh Raghavendra , Ezequiel Garcia Subject: [PATCH 1/3] mtdblock: Update old JFFS2 mention in Kconfig Date: Sun, 1 Aug 2021 20:45:03 -0300 Message-Id: <20210801234509.18774-2-ezequiel@collabora.com> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20210801234509.18774-1-ezequiel@collabora.com> References: <20210801234509.18774-1-ezequiel@collabora.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org JFFS2 can be mounted without 'mtdblock' since a really, really long time. Some git-log archaeology shows that in 2006 it was possible to use 'root=' to mount a JFFS2 rootfs: commit e9482b4374e2596e6f3f1ab30c4ea469f4ac6311 Author: Joern Engel Date: Tue May 30 14:25:46 2006 +0200 [MTD] Allow alternate JFFS2 mount variant for root filesystem. With this patch, "root=mtd3" and "root=mtd:foo" work for a JFFS2 rootfs. However, there are still plenty of tutorials that mention mtdblock, so users are still taking this route. Update the Kconfig to reflect this is no longer needed. Signed-off-by: Ezequiel Garcia --- drivers/mtd/Kconfig | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/drivers/mtd/Kconfig b/drivers/mtd/Kconfig index 79a8ff542883..32bed6c63863 100644 --- a/drivers/mtd/Kconfig +++ b/drivers/mtd/Kconfig @@ -127,10 +127,9 @@ config MTD_BLOCK on RAM chips in this manner. This block device is a user of MTD devices performing that function. - At the moment, it is also required for the Journalling Flash File - System(s) to obtain a handle on the MTD device when it's mounted - (although JFFS and JFFS2 don't actually use any of the functionality - of the mtdblock device). + Note that mounting a JFFS2 filesystem doesn't require using mtdblock. + It's possible to mount a rootfs using the MTD device on the "root=" + bootargs as "root=mtd2" or "root=mtd:name_of_device". Later, it may be extended to perform read/erase/modify/write cycles on flash chips to emulate a smaller block size. Needless to say, -- 2.32.0