From: Kyungmin Park <kyungmin.park@samsung.com>
To: Artem Bityutskiy <dedekind@infradead.org>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: OneNAND git
Date: Thu, 11 Jan 2007 02:25:18 +0000 (GMT) [thread overview]
Message-ID: <18889392.556981168482318504.JavaMail.weblogic@ep_ml19> (raw)
Hi Artem Bityutskiy,
Okay no problem. I will clone your tree.
But, first, To David Woodhouse please merge the Artem's onenand git tree for mtd git tree. then I will clone it.
Thank you,
Kyungmin Park
------- Original Message -------
Sender : Artem Bityutskiy<dedekind@infradead.org>
Date : Jan 10, 2007 22:18
Title : Re: OneNAND git
Hi Kyungmin,
On Wed, 2007-01-10 at 00:43 +0000, Kyungmin Park wrote:
> I saw your tree. and please append the last patch, read-while-load in DDP handling.
> also we have to add "[MTD] OneNAND: fix onenand_wait bug".
Yeah, they are there.
> Then what's your opinion of JFFS2 patch?
>
> [JFFS2] Skip ECC position in NAND family flash
>
> In OneNAND it updates the spare ecc area automatically when write the
> cleanmark in spare area
I think the problem should be fixed by means of MTD_OOB_AUTO option
instead.
> The remaing patches are following.
>
> 1. [MTD] OneNAND: add subpage write support
It is cool to support this of course. I just forgot about it.
BTW, here is the idea how to test this. Just report mtd->writesize = 512
instead of 2048 temporarily. Then run some JFFS2 tests. O course, this
is just a hack for testing and you should report 2048 in mtd->writesize.
> 2. [JFFS2] fix wrong ref-flash_offset usage.
I think it is not OneNAND-related. I've put it to my
dedekind-mtd-2.6.git tree - will bug dwmw2 to pull from it. OK?
> I think thres's no problem of the removal of cond_resched in OneNAND driver.
> If you don't agree this one, I can revert it.
Revert a revert? :-)
Yes, I do not agree. Having large loops with no cond_resched() is not
nice. For example, MTD may be asked to read 64MiB of data at one go. And
we do this without releasing CPU and cause huge delays. This is bad.
Now I have all the patches in place in my tree. I offer you to consider
to clone my tee and maintain it instead. I do not actually wish to be a
OneNAND maintainer, just collected all the patches and made a bit neater
git tree. Some of them didn't apply cleanly, so I did some hand work.
Also, I change the author of my patch to me instead of you. :-)
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next reply other threads:[~2007-01-11 2:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 2:25 Kyungmin Park [this message]
[not found] <846526.522131168389817787.JavaMail.weblogic@ep_ml20>
2007-01-10 13:18 ` OneNAND git Artem Bityutskiy
-- strict thread matches above, loose matches on Subject: below --
2007-01-10 0:46 Kyungmin Park
2007-01-09 12:24 Artem Bityutskiy
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=18889392.556981168482318504.JavaMail.weblogic@ep_ml19 \
--to=kyungmin.park@samsung.com \
--cc=dedekind@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