From patchwork Thu Aug 31 03:09:32 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Nicolas Pitre X-Patchwork-Id: 111351 Delivered-To: patch@linaro.org Received: by 10.140.95.112 with SMTP id h103csp1908206qge; Wed, 30 Aug 2017 20:10:28 -0700 (PDT) X-Received: by 10.84.194.195 with SMTP id h61mr903351pld.367.1504149027901; Wed, 30 Aug 2017 20:10:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1504149027; cv=none; d=google.com; s=arc-20160816; b=HbkByobpoPuyRAAcTywarVlYxVmwNttw2zXjGi9/wNo/FI9ZgXWHf+3oqozDvwPIuy EwErZulwxnOGgdewGpbPfndneVhfqmWWHmDIlQY9v9hmxhruHc2UVgCVRVnPENJ7Zsnr o63Se1yLWu0+2ajb6He9ssRc93ggtCy4bX/6UJ7kiVlhOifUfup8vu2/A+FJphjobW+F dl0hDRLL3/ZFf8D/3YXhiZZHj28AuUrXQEzHcHAcDVOk96WGHYbqYimguBr/GjKyFadh epE4m1BXQOaZbJv6FP10CvnOScltYBSuK/CyUKOcbT5pesIUvDZnHmVDFVThrx9/2PCp RJOQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from:dkim-signature:arc-authentication-results; bh=0JcBFVB5yFWH79mN6/TnXq+rmNF9uc5Kgmo2oBGDng8=; b=trmE1e4JThfVSAUG72V13Pcz3le6ciBVqOhEB9bfZNH1ZGsYM4C7IYSlAhSRZbHh/B BVXpP6inIOcsJoTaJxXvcjsbQX+jdC/kRLhPDugzwtKR6mslZJsUPMeTvt5P8J3DbtGt sxzF54yf4HRPyEIOZxX8NKHHh2SM69LuY+NewOuXiqR1hEAX+OrpUNJQkGHuJgLhadC+ h96xeF42i7wcHZRdKvwky4Hi5+FwuOoYye6MRkA8U0j/EKkIJCP0n7xbJ16SjFHIVzyM caS2R+KpoHjKb/sxkGLEwuyCHJFHr5BdYVtoKfO16wWFuGHW/nwJUez1ajfGpWGor8+D eYYw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@pobox.com header.s=sasl header.b=UxWBnUEY; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b7si5502890pge.372.2017.08.30.20.10.27; Wed, 30 Aug 2017 20:10:27 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@pobox.com header.s=sasl header.b=UxWBnUEY; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751581AbdHaDKZ (ORCPT + 26 others); Wed, 30 Aug 2017 23:10:25 -0400 Received: from pb-smtp2.pobox.com ([64.147.108.71]:60148 "EHLO sasl.smtp.pobox.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751333AbdHaDJj (ORCPT ); Wed, 30 Aug 2017 23:09:39 -0400 Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 6716791C25; Wed, 30 Aug 2017 23:09:38 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=from:to:cc :subject:date:message-id:in-reply-to:references; s=sasl; bh=jjdb ApHS+DL+SRJSQEg6GRJAQ3M=; b=UxWBnUEY+nJVyjGpGEuYMauTADBm/UAXYRdX /kP/aD1LoFIehlClxB9jI+c4Q7RKbtei07DIjcq1Tzd223aVMM2fYdprqUSclnwL Ng54Y6L1rrcR3RyaOOfSLBjcJmtHQgMnZlBV17xGxcSNpgeHp/EB+AmwmtNJSqE5 n/vm/xo= Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 5EE1591C24; Wed, 30 Aug 2017 23:09:38 -0400 (EDT) Received: from yoda.home (unknown [70.80.200.199]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id A642991C20; Wed, 30 Aug 2017 23:09:37 -0400 (EDT) Received: from xanadu.home (xanadu.home [192.168.2.2]) by yoda.home (Postfix) with ESMTP id 817392DA06F2; Wed, 30 Aug 2017 23:09:36 -0400 (EDT) From: Nicolas Pitre To: Alexander Viro Cc: linux-fsdevel@vger.kernel.org, linux-embedded@vger.kernel.org, linux-kernel@vger.kernel.org, Chris Brandt Subject: [PATCH v3 5/5] cramfs: rehabilitate it Date: Wed, 30 Aug 2017 23:09:32 -0400 Message-Id: <20170831030932.26979-6-nicolas.pitre@linaro.org> X-Mailer: git-send-email 2.9.5 In-Reply-To: <20170831030932.26979-1-nicolas.pitre@linaro.org> References: <20170831030932.26979-1-nicolas.pitre@linaro.org> X-Pobox-Relay-ID: D28DFA5C-8DF9-11E7-A4CB-9D2B0D78B957-78420484!pb-smtp2.pobox.com Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Update documentation, pointer to latest tools, appoint myself as maintainer. Given it's been unloved for so long, I don't expect anyone will protest. Signed-off-by: Nicolas Pitre Tested-by: Chris Brandt --- Documentation/filesystems/cramfs.txt | 42 ++++++++++++++++++++++++++++++++++++ MAINTAINERS | 4 ++-- fs/cramfs/Kconfig | 9 +++++--- 3 files changed, 50 insertions(+), 5 deletions(-) -- 2.9.5 diff --git a/Documentation/filesystems/cramfs.txt b/Documentation/filesystems/cramfs.txt index 4006298f67..8875d306bc 100644 --- a/Documentation/filesystems/cramfs.txt +++ b/Documentation/filesystems/cramfs.txt @@ -45,6 +45,48 @@ you can just change the #define in mkcramfs.c, so long as you don't mind the filesystem becoming unreadable to future kernels. +Memory Mapped cramfs image +-------------------------- + +The CRAMFS_PHYSMEM Kconfig option adds support for loading data directly +from a physical linear memory range (usually non volatile memory like Flash) +to cramfs instead of going through the block device layer. This saves some +memory since no intermediate buffering is necessary to hold the data before +decompressing. + +And when data blocks are kept uncompressed and properly aligned, they will +automatically be mapped directly into user space whenever possible providing +eXecute-In-Place (XIP) from ROM of read-only segments. Data segments mapped +read-write (hence they have to be copied to RAM) may still be compressed in +the cramfs image in the same file along with non compressed read-only +segments. Both MMU and no-MMU systems are supported. This is particularly +handy for tiny embedded systems with very tight memory constraints. + +The filesystem type for this feature is "cramfs_physmem" to distinguish it +from the block device (or MTD) based access. The location of the cramfs +image in memory is system dependent. You must know the proper physical +address where the cramfs image is located and specify it using the +physaddr=0x******** mount option (for example, if the physical address +of the cramfs image is 0x80100000, the following command would mount it +on /mnt: + +$ mount -t cramfs_physmem -o physaddr=0x80100000 none /mnt + +To boot such an image as the root filesystem, the following kernel +commandline parameters must be provided: + + "rootfstype=cramfs_physmem rootflags=physaddr=0x80100000" + + +Tools +----- + +A version of mkcramfs that can take advantage of the latest capabilities +described above can be found here: + +https://github.com/npitre/cramfs-tools + + For /usr/share/magic -------------------- diff --git a/MAINTAINERS b/MAINTAINERS index 44cb004c76..12f8155cfe 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -3612,8 +3612,8 @@ F: drivers/cpuidle/* F: include/linux/cpuidle.h CRAMFS FILESYSTEM -W: http://sourceforge.net/projects/cramfs/ -S: Orphan / Obsolete +M: Nicolas Pitre +S: Maintained F: Documentation/filesystems/cramfs.txt F: fs/cramfs/ diff --git a/fs/cramfs/Kconfig b/fs/cramfs/Kconfig index 5b4e0b7e13..ae1fe6c795 100644 --- a/fs/cramfs/Kconfig +++ b/fs/cramfs/Kconfig @@ -1,5 +1,5 @@ config CRAMFS - tristate "Compressed ROM file system support (cramfs) (OBSOLETE)" + tristate "Compressed ROM file system support (cramfs)" select ZLIB_INFLATE help Saying Y here includes support for CramFs (Compressed ROM File @@ -15,8 +15,11 @@ config CRAMFS cramfs. Note that the root file system (the one containing the directory /) cannot be compiled as a module. - This filesystem is obsoleted by SquashFS, which is much better - in terms of performance and features. + This filesystem is limited in capabilities and performance on + purpose to remain small and low on RAM usage. It is most suitable + for small embedded systems. For a more capable compressed filesystem + you should look at SquashFS which is much better in terms of + performance and features. If unsure, say N.