On Sun, Sep 20, 2009 at 00:06:21, David Woodhouse wrote:
> On Mon, 2009-08-03 at 18:24 -0700, David Brownell wrote:
> >
> > If that's going to be possible, shouldn't it work for any
> > MTD device? And the lack of protection bothers me a bit
> > more here than with EEPROMs and NVRAM, since it seems kind
> > of easy to clobber UBI (or JFFS2 etc) data. Maybe there
> > should be a way to make jus a specific partition available
> > this way?
>
> Hrm, I'm unconvinced by the second version of the patch. I don't really
> like adding this to the core MTD code, and I particularly dislike the
> extra ->setup() method in struct mtd_partition.
>
> Couldn't this be done as a wrapper round MTD devices, set up by the
> board driver? Perhaps we could provide a template mtd_macc_{read,write}
> function which board drivers can use, but I don't really like the
> patches I've seen.
>
David,
Can you elaborate a bit more on what you would like to see in this patch?
>From your explanation above I did not understand completely what should
be done.
Regards,
Sudhakar
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
