public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Kyungmin Park <kmpark@infradead.org>
Cc: apgmoorthy <moorthy.apg@samsung.com>,
	linux-mtd@lists.infradead.org,
	Kyungmin Park <kyungmin.park@samsung.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] [PATCH] [MTD] Flex-OneNAND MTD Driver available.
Date: Fri, 26 Sep 2008 09:26:09 +0300	[thread overview]
Message-ID: <1222410369.5012.9.camel@sauron> (raw)
In-Reply-To: <9c9fda240809252230s6373acf8v4dd2b942eba360a7@mail.gmail.com>


On Fri, 2008-09-26 at 14:30 +0900, Kyungmin Park wrote:
> Thank you for your kind comments.
> 
> Yes that's I concerned it breaks the other NAND ABI. Actually In
> OneNAND it doesn't use eccpos since OneNAND controller handle all ECC
> functions. we don't need to concern it.

Right.

> As pages are bigger, it requires more eccpos and other fields are
> similar. we need more flexible filed definitions.

Right.

> Well how do you think that at this time it only describes the 64 bytes
> only for temporarily and next time it adds remaining parts if it is
> really needed.

Well, it is not very nice, but I guess it should be OK for this case,
because people are not supposed to look at OOB of MLC OneNAND anyway. So
I would go this way, although I'm not sure dwmw2 would agree on this.

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

  reply	other threads:[~2008-09-26  6:26 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-19 12:31 [ANNOUNCE] [PATCH] [MTD] Flex-OneNAND MTD Driver available AYYANARPONNUSAMY GANGHEYAMOORTHY
2008-09-22  7:11 ` Kyungmin Park
2008-09-24 12:35   ` apgmoorthy
2008-09-26  0:31     ` Kyungmin Park
2008-09-26  4:51       ` Artem Bityutskiy
2008-09-26  5:30         ` Kyungmin Park
2008-09-26  6:26           ` Artem Bityutskiy [this message]
2008-09-26  8:01         ` Amit Kumar Sharma
2008-09-26  8:19           ` Artem Bityutskiy
2008-09-29  9:28             ` apgmoorthy
2008-10-09 22:57               ` Kyungmin Park
     [not found]                 ` <1224331498.6770.1362.camel@macbook.infradead.org>
2008-10-20  5:04                   ` apgmoorthy
2008-10-20  5:54                     ` Artem Bityutskiy
2008-10-22  6:43                       ` apgmoorthy
2008-10-24 14:26                         ` Adrian Hunter
2008-11-03 10:32                           ` apgmoorthy
2008-11-05  8:52                             ` Adrian Hunter
2008-11-07 14:26                               ` Rohit
2008-11-10 15:20                                 ` Adrian Hunter
2008-11-11  3:31                                   ` Amit Kumar Sharma
2008-11-11  7:28                                     ` Adrian Hunter
2008-11-12  5:43                                   ` Rohit
2008-10-20 10:53                     ` David Woodhouse
2008-10-21  5:22                   ` apgmoorthy
2008-10-10  6:34               ` David Woodhouse
     [not found] <000001c92f46$18a67c70$3dd66c6b@sisodomain.com>
2008-10-16  4:28 ` Kyungmin Park
2008-10-20  3:01 ` Kyungmin Park

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=1222410369.5012.9.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=kmpark@infradead.org \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=moorthy.apg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox