public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: kyungmin.park@samsung.com
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: OneNAND: Update OOB free table
Date: Fri, 22 Dec 2006 11:17:25 +0200	[thread overview]
Message-ID: <1166779045.3939.58.camel@sauron> (raw)
In-Reply-To: <31196440.367141166752320332.JavaMail.weblogic@ep_ml29>

[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]

On Fri, 2006-12-22 at 01:52 +0000, Kyungmin Park wrote:
> Okay, I understand the MTD_OOB_AUTO concept. but now JFFS2 only use the MTD_OOB_PLACE. 
> so JFFS2 skip the ecc position for backward compatibility.
...
> 
> Now OneNAND don't support MTD_OOB_AUTO, but if the jffs2 supports the this one. I will support it.
> I think it's more reasonable to handle oob in driver level instead of filesystem.

I take care about this in JFFS, you take care in OneNAND, OK?

> Actually, I'm not sure where's the right place. But if we don't touch the watchdong.
> it will soft lockup when mounting the JFFS2 with big partition. (I just borrowed it from nand.)

Anyway, you should not touch watchdog. You problem is fixed by adding
cond_resched() at the right places. What you did - you shut up watchdog
which screamed about a real error, instead of solving the error.

I have prepared a patch - it is in my dedekind-mtd-2.6.git GIT tree. It
is also attached.

> No, I used it in infradead.org. but I just used for commit.

Cool.

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

[-- Attachment #2: onenand-sched.diff --]
[-- Type: application/mbox, Size: 3144 bytes --]

  reply	other threads:[~2006-12-22  9:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-22  1:52 OneNAND: Update OOB free table Kyungmin Park
2006-12-22  9:17 ` Artem Bityutskiy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-12-26  7:15 Kyungmin Park
2006-12-18  4:24 Kyungmin Park
2006-12-18 14:23 ` Artem Bityutskiy
2006-12-21 11:15 ` Artem Bityutskiy
2006-12-21 12:35   ` Artem Bityutskiy
2006-12-15  2:38 Kyungmin Park
2006-12-15  8:33 ` Timo Teras
2006-12-15 10:41 ` Artem Bityutskiy
2006-12-15 11:19   ` Timo Teras
2006-12-08  0:11 Kyungmin Park
2006-12-08  8:43 ` Timo Teras
2006-12-11 12:20 ` Timo Teras

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=1166779045.3939.58.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=kyungmin.park@samsung.com \
    --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