All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sekhar Nori <nsekhar@ti.com>
To: "Gupta, Pekon" <pekon@ti.com>
Cc: "Fernando Gomes" <fernando.gomes@efacec.com>,
	"davinci-linux-open-source@linux.davincidsp.com"
	<Davinci-linux-open-source@linux.davincidsp.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"Aníbal Almeida Pinto" <anibal.pinto@efacec.com>
Subject: Re: JFFS2 impact when don't have sub page access
Date: Fri, 2 Aug 2013 11:00:27 +0530	[thread overview]
Message-ID: <51FB43F3.7020909@ti.com> (raw)
In-Reply-To: <20980858CB6D3A4BAE95CA194937D5E73E9F0091@DBDE04.ent.ti.com>

On Friday 02 August 2013 10:27 AM, Gupta, Pekon wrote:
> Hello,
> 
>> Hi,
>>
>> I' am using an OMAP L138 with a NAND SLC (MT29F4G08)
>>
>> I was making some tests with Ubifs but found some errors due to OMAP
>> don't support sub pages access:
>>
> TI OMAP2-NAND supports sub-pages for SLC NAND.
>  http://lists.infradead.org/pipermail/linux-mtd/attachments/20130405/a146567f/attachment.obj
> 
> This patch was accepted in mainline linux-3.10,
> And tested on AM335x with 2K/64 NAND.
> 
> You can follow this patch details here..
> http://lists.infradead.org/pipermail/linux-mtd/2013-March/046285.html

Yes, but Aníbal is talking about OMAP-L138 which is actually a DaVinci
part and uses drivers/mtd/nand/davinci_nand.c

May be you can clarify whether absence of subpage support will lead to
the kind of errors Aníbal reported?

Also, the subject talks about JFFS2. There is no known affect of absence
of subpage support on JFFS2, right?

Thanks,
Sekhar

  reply	other threads:[~2013-08-02  5:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-31 14:24 JFFS2 impact when don't have sub page access Aníbal Almeida Pinto
2013-08-02  4:57 ` Gupta, Pekon
2013-08-02  5:30   ` Sekhar Nori [this message]
2013-08-02  6:25     ` Gupta, Pekon
2013-08-02 10:47       ` Aníbal Almeida Pinto
2013-08-02 11:52         ` Gupta, Pekon
2013-08-02 12:42           ` Aníbal Almeida Pinto

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=51FB43F3.7020909@ti.com \
    --to=nsekhar@ti.com \
    --cc=Davinci-linux-open-source@linux.davincidsp.com \
    --cc=anibal.pinto@efacec.com \
    --cc=fernando.gomes@efacec.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=pekon@ti.com \
    /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.