[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6934efce0706071334w54eea3d9mfed1670f527ff831@mail.gmail.com>
Date: Thu, 7 Jun 2007 13:34:12 -0700
From: "Jared Hulbert" <jaredeh@...il.com>
To: "Christoph Hellwig" <hch@...radead.org>, carsteno@...ibm.com,
"Jared Hulbert" <jaredeh@...il.com>,
"Nick Piggin" <nickpiggin@...oo.com.au>,
"Andrew Morton" <akpm@...ux-foundation.org>,
richard.griffiths@...driver.com,
"Richard Griffiths" <res07ml0@...izon.net>,
Linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2.6.21] cramfs: add cramfs Linear XIP
On 6/7/07, Christoph Hellwig <hch@...radead.org> wrote:
> On Thu, Jun 07, 2007 at 07:07:54PM +0200, Carsten Otte wrote:
> > I've had a few beer long discussion with Joern Engel and David
> > Woodhouse on this one. To cut a long discussion short: the current XIP
> > infrastructure is not sufficient to be used on top of mtd. We'd need
> > some extenstions:
> > - on get_xip_page() we'd need to state if we want the reference
> > read-only or read+write
> > - we need a put_xip_page() to return references
> > - and finally we need a callback for the referece, so that the mtd
> > driver can ask to get its reference back (in order to unmap from
> > userland when erasing a block)
>
> And we'll need that even when using cramfs. There's not way we'd
> merge a hack where the user has to specify a physical address on
> the mount command line.
Why not? For the use case in question the user usually manually
burned the image to a physical address before hand. Many of these
system don't have MTD turned on for this Flash, they don't need it
because they don't write to this Flash once the system is up.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists