From: Andrew Morton <akpm@linux-foundation.org>
To: David Howells <dhowells@redhat.com>
Cc: dwmw2@infradead.org, bernds_cb1@t-online.de, dhowells@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] NOMMU: Make it possible for RomFS to use MTD devices directly
Date: Thu, 19 Feb 2009 16:12:11 -0800 [thread overview]
Message-ID: <20090219161211.9b80c129.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090212104010.26766.20813.stgit@warthog.procyon.org.uk>
On Thu, 12 Feb 2009 10:40:10 +0000
David Howells <dhowells@redhat.com> wrote:
> Change RomFS so that it can use MTD devices directly - without the intercession
> of the block layer - as well as using block devices.
>
> This permits RomFS:
>
> (1) to use the MTD direct mapping facility available under NOMMU conditions if
> the underlying device is directly accessible by the CPU (including XIP);
>
> (2) and thus to be used when the block layer is disabled.
>
> RomFS can be configured with support just for MTD devices, just for Block
> devices or for both. If RomFS is configured for both, then it will treat
> mtdblock device files as MTD backing stores, not block layer backing stores.
My x86_64 usualconfig just exploded with
fs/romfs/storage.c:18:2: error: #error no ROMFS backing store interface configured
http://userweb.kernel.org/~akpm/config-akpm2.txt
next prev parent reply other threads:[~2009-02-20 0:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 10:40 [PATCH 1/4] NOMMU: Present backing device capabilities for MTD chardevs David Howells
2009-02-12 10:40 ` [PATCH 2/4] NOMMU: Add support for direct mapping through mtdconcat if possible David Howells
2009-02-12 10:40 ` [PATCH 3/4] NOMMU: Make it possible for RomFS to use MTD devices directly David Howells
2009-02-20 0:12 ` Andrew Morton [this message]
2009-02-20 12:11 ` David Howells
2009-02-20 12:31 ` David Howells
2009-02-12 10:40 ` [PATCH 4/4] MTD: Fix a bad dependency in the Blackfin code David Howells
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090219161211.9b80c129.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bernds_cb1@t-online.de \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.