[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070608161526.GA3729@infradead.org>
Date: Fri, 8 Jun 2007 17:15:26 +0100
From: Christoph Hellwig <hch@...radead.org>
To: Jared Hulbert <jaredeh@...il.com>
Cc: Christoph Hellwig <hch@...radead.org>, carsteno@...ibm.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 Fri, Jun 08, 2007 at 09:11:47AM -0700, Jared Hulbert wrote:
> >On Fri, Jun 08, 2007 at 09:05:32AM -0700, Jared Hulbert wrote:
> >> Okay so we need some driver that opens/closes this ROM. This has been
> >> done from the dcss block device but that doesn't make sense for most
> >> embedded systems. The MTD allows for this with point(),unpoint().
> >> That should work just fine. It does introduce the MTD as a dependancy
> >> which is unnecessary in many systems, but it will work now.
> >
> >The Linux solution to this problem would be to introduce an option for
> >mtd write support. That way the majority of the code doesn't heave to
> >be compiled for the read-only case but you still get a uniform interface.
>
> You mean make an MTD-light interface possible?
I wouldn't call it that. The interface should stay the same except that
write operations are not supported. In mtd_info you'd just have
point/unpoint and read/read_oob but no write operations and all the backing
code wouldn't be compiled in aswell.
-
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