linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Sudhakar Rajashekhara" <sudhakar.raj@ti.com>
To: "'David Woodhouse'" <dwmw2@infradead.org>,
	"'David Brownell'" <david-b@pacbell.net>
Cc: davinci-linux-open-source@linux.davincidsp.com,
	linux-mtd@lists.infradead.org
Subject: RE: [PATCH] [MTD] m25p80: memory accessor interface for SPI MTD driver
Date: Thu, 24 Sep 2009 14:38:35 +0530	[thread overview]
Message-ID: <010b01ca3cf6$98e55c30$cab01490$@raj@ti.com> (raw)
In-Reply-To: <1253385381.6317.29.camel@macbook.infradead.org>

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

  reply	other threads:[~2009-09-24  9:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-03 21:02 [PATCH] [MTD] m25p80: memory accessor interface for SPI MTD driver Sudhakar Rajashekhara
2009-08-04  1:24 ` David Brownell
2009-08-18  7:24   ` Sudhakar Rajashekhara
2009-09-19 18:36   ` David Woodhouse
2009-09-24  9:08     ` Sudhakar Rajashekhara [this message]
2009-09-24 14:33       ` David Woodhouse

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='010b01ca3cf6$98e55c30$cab01490$@raj@ti.com' \
    --to=sudhakar.raj@ti.com \
    --cc=david-b@pacbell.net \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).