All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: apgmoorthy <moorthy.apg@samsung.com>
Cc: 'Amit Kumar Sharma' <amitsharma.9@samsung.com>,
	vishak.g@samsung.com, 'Artem Bityutskiy' <dedekind1@gmail.com>,
	'Amul Saha' <amul.saha@samsung.com>,
	kyungmin.park@samsung.com, linux-mtd@lists.infradead.org,
	'David Woodhouse' <dwmw2@infradead.org>
Subject: RE: MLC Support in JFFS2
Date: Mon, 22 Jun 2009 16:41:56 +0300	[thread overview]
Message-ID: <1245678116.9487.46.camel@localhost.localdomain> (raw)
In-Reply-To: <AC2E6612F7284933840F22ED22E239CE@sisodomain.com>

On Mon, 2009-06-22 at 19:03 +0530, apgmoorthy wrote:
> Yes it do that .
> There are two things in Handling MLCs
> 1.Paired Page Handling
> This is done in Flex-OneNAND Driver.
> flexonenand_lsb_page_recovery will handle that in MLC area. 

Ah, ok you do this at the driver level - good.

> 2.NOP==1
> This scenario has to be dealt in synchronization with JFFS2.
> This is what i asked about. 
> Pathces , in the links(above)are addressing this.

OK, I see.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

  reply	other threads:[~2009-06-22 13:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22  5:56 MLC Support in JFFS2 apgmoorthy
2009-06-22  7:47 ` Artem Bityutskiy
2009-06-22 13:33   ` apgmoorthy
2009-06-22 13:41     ` Artem Bityutskiy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-05-25 10:52 [patch 01/14] mtd: Flex-OneNAND support apgmoorthy
2009-05-27 13:55 ` Artem Bityutskiy
2009-06-09 13:38   ` David Woodhouse
2009-06-11  9:23     ` Amul Saha
2009-06-11  9:35       ` Artem Bityutskiy
2009-06-12 10:26         ` Amul Saha
2009-06-12 10:42           ` Artem Bityutskiy
2009-06-12 11:57             ` Amul Saha
2009-06-12 12:03               ` Artem Bityutskiy
2009-06-12 13:16                 ` Amul Saha
2009-06-12 13:32                   ` David Woodhouse
     [not found]                     ` <42F6638D897B4BA7B729CBC244D9F6E4@sisodomain.com>
2009-06-22 19:15                       ` MLC Support in JFFS2 David Woodhouse
2009-06-23 12:52                         ` apgmoorthy
2009-06-23 13:19                           ` David Woodhouse
2009-06-24  6:50                             ` apgmoorthy
2010-03-31  9:53                         ` Amul Kumar Saha
2010-03-31 13:07                           ` massimo cirillo
2010-04-05 11:10                             ` Amul Kumar Saha
2010-04-05 11:52                               ` massimo cirillo
2010-04-09  9:21                                 ` Amul Kumar Saha
2010-04-13  9:45                                   ` massimo cirillo
     [not found]                                     ` <D4189C368A9B4BD986B7B98A0F05953B@sisodomain.com>
2010-04-15 21:03                                       ` massimo cirillo
2010-04-15 21:26                                         ` massimo cirillo
2007-11-23 15:39 payagond

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=1245678116.9487.46.camel@localhost.localdomain \
    --to=dedekind@infradead.org \
    --cc=amitsharma.9@samsung.com \
    --cc=amul.saha@samsung.com \
    --cc=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=moorthy.apg@samsung.com \
    --cc=vishak.g@samsung.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.