From patchwork Tue Feb 9 11:34:13 2010 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: "Robert P. J. Day" X-Patchwork-Id: 44904 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from bombadil.infradead.org (bombadil.infradead.org [18.85.46.34]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 4C501B7D26 for ; Tue, 9 Feb 2010 22:37:39 +1100 (EST) Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.69 #1 (Red Hat Linux)) id 1NeoNM-0007YF-TI; Tue, 09 Feb 2010 11:35:28 +0000 Received: from astoria.ccjclearline.com ([64.235.106.9]) by bombadil.infradead.org with esmtps (Exim 4.69 #1 (Red Hat Linux)) id 1NeoNI-0007Xo-4A for linux-mtd@lists.infradead.org; Tue, 09 Feb 2010 11:35:27 +0000 Received: from cpe002129687b04-cm001225dbafb6.cpe.net.cable.rogers.com ([99.235.241.187] helo=crashcourse.ca) by astoria.ccjclearline.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1NeoNG-0001F0-W3 for linux-mtd@lists.infradead.org; Tue, 09 Feb 2010 06:35:23 -0500 Date: Tue, 9 Feb 2010 06:34:13 -0500 (EST) From: "Robert P. J. Day" X-X-Sender: rpjday@localhost To: MTD mailing list Subject: [PATCH] Web site: A few grammatical fixes in Docs/General. Message-ID: User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - astoria.ccjclearline.com X-AntiAbuse: Original Domain - lists.infradead.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - crashcourse.ca X-Source: X-Source-Args: X-Source-Dir: X-CRM114-Version: 20090807-BlameThorstenAndJenny ( TRE 0.7.6 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20100209_063524_290823_8EB2F923 X-CRM114-Status: GOOD ( 26.72 ) X-Spam-Score: 0.0 (/) X-Spam-Report: SpamAssassin version 3.2.5 on bombadil.infradead.org summary: Content analysis details: (0.0 points) pts rule name description ---- ---------------------- -------------------------------------------------- _SUMMARY_ X-BeenThere: linux-mtd@lists.infradead.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-mtd-bounces@lists.infradead.org Errors-To: linux-mtd-bounces+incoming=patchwork.ozlabs.org@lists.infradead.org Signed-off-by: Robert P. J. Day --- in addition to a few picky fixes on that page, toward the bottom of that page, one reads: "This is wrong in most cases. The mtdblock In other words, please, do ^^^ ??? not use mtdblock unless you know exactly what you are doing. there seems to be something missing there, i'll leave it to people higher up the food chain to decide what to do there. rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA Linux Consulting, Training and Kernel Pedantry. Web page: http://crashcourse.ca Twitter: http://twitter.com/rpjday ======================================================================== diff --git a/doc/general.xml b/doc/general.xml index 8368b2e..14ba8ff 100644 --- a/doc/general.xml +++ b/doc/general.xml @@ -30,7 +30,7 @@ AG-AND, ECC'd NOR, etc.

MTD subsystem does not deal with block devices like MMC, eMMC, SD, CompactFlash, etc. These devices are not raw flashes but they have a Flash Translation layer inside, which makes them look like block devices. These -devices are subject of the Linux block subsystem, not MTD. Please, refer +devices are the subject of the Linux block subsystem, not MTD. Please, refer to this FAQ section for a short list of the main differences between block and MTD devices. And the raw flash vs. FTL devices UBIFS section @@ -46,15 +46,15 @@ discusses this in more details.

them as bad or checking if an eraseblock is bad, getting information about MTD devices, etc. -
  • The sysfs interface is relatively and it provides full - information about each MTD device in the system. This interface is +
  • The sysfs interface is relatively newer and it provides + full information about each MTD device in the system. This interface is easily extensible and developers are encouraged to use the sysfs interface instead of older ioctl or /proc/mtd interfaces, when possible.
  • The /proc/mtd proc file system file provides general MTD information. This is a legacy interface and the sysfs interface - provide more information.
    • + provides more information.

    MTD subsystem supports bare NAND flashes with @@ -77,7 +77,7 @@ starting from kernel version 2.6.29 and they live in the drivers/mtd/tests directory of the linux kernel source codes. You may compile the tests as kernel modules by enabling them in the kernel configuration menu by marking: "Device Drivers" -> -"Memory Technology Devices (MTD)" -> "MTD tests support" (or +"Memory Technology Device (MTD) support" -> "MTD tests support" (or the MTD_TESTS symbol in the .config file).

    If you have a pre-2.6.29 kernel, you may find the tests