public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Kyungmin Park" <kmpark@infradead.org>
To: <vwool@ru.mvista.com>
Cc: linux-mtd@lists.infradead.org
Subject: bug in drivers/mtd/onenand/onenand_base.c?
Date: Thu, 22 Mar 2007 20:44:45 +0900	[thread overview]
Message-ID: <000001c76c77$80f44a70$06100a3b@user001b2c71e3> (raw)

Hi Vitaly Wool,

Sorry, I'm not office so I can't access my computer.
To help your work I send the URL related this problem.
This problem is reported previous time but not commit it.

Please check this mail. It would help your work.
http://linux.omap.com/pipermail/linux-omap-open-source/2007-March/009395.htm
l

I saw your mtd git tree related with yaffs. I tested the yaffs on onenand
before. But as you know it failed.
Now with your patch how many bytes are needed in yaffs if ecc provided?
Maybe we need to modify onenand read & write function to support read/write
with oob simultaneously.
Currently it only supports separated read or oob function only, instead of
both.

If the yaffs requires less or equal with 20 bytes, it will work with
OneNAND. Of course, if the page is 1KB, it can't. Since it has only 10 bytes
OOB.

I hope yaffs can run with OneNAND.

Thank you,
Kyungmin Park

             reply	other threads:[~2007-03-22 11:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22 11:44 Kyungmin Park [this message]
     [not found] ` <46028A4F.9010907@ru.mvista.com>
2007-03-23  2:11   ` Onenand and yaffs [was: Re: bug in drivers/mtd/onenand/onenand_base.c?] Kyungmin Park
     [not found] <46025ABF.3000100@nokia.com>
2007-03-22 10:40 ` bug in drivers/mtd/onenand/onenand_base.c? Vitaly Wool
  -- strict thread matches above, loose matches on Subject: below --
2007-03-22  9:36 Vitaly Wool
2007-03-22 10:34 ` Artem Bityutskiy
2007-03-22 10:40   ` Adrian Hunter

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='000001c76c77$80f44a70$06100a3b@user001b2c71e3' \
    --to=kmpark@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=vwool@ru.mvista.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