All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sudhakar Rajashekhara" <sudhakar.raj@ti.com>
To: "'David Brownell'" <david-b@pacbell.net>
Cc: linux-mtd@lists.infradead.org,
	davinci-linux-open-source@linux.davincidsp.com,
	dwmw2@infradead.org
Subject: RE: [PATCH] [MTD] m25p80: memory accessor interface for SPI MTD driver
Date: Tue, 18 Aug 2009 12:54:06 +0530	[thread overview]
Message-ID: <00d301ca1fd4$df01ded0$9d059c70$@raj@ti.com> (raw)
In-Reply-To: <200908031824.01795.david-b@pacbell.net>

On Tue, Aug 04, 2009 at 06:54:01, David Brownell wrote:
> On Monday 03 August 2009, Sudhakar Rajashekhara wrote:
> > On TI's da850/omap-l138 EVM, MAC address is stored in SPI flash.
> > This patch implements memory accessor interface for SPI MTD
> > driver which enables the kernel to access flash data.
> 
> 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?
> 

I have submitted the modified version of this patch which
implements the accessor interface in mtdpart.c file so that
it works for any mtd drivers (NAND, NOR, SPI).

Regards, Sudhakar

  reply	other threads:[~2009-08-18  7:24 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 [this message]
2009-09-19 18:36   ` David Woodhouse
2009-09-24  9:08     ` Sudhakar Rajashekhara
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='00d301ca1fd4$df01ded0$9d059c70$@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 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.