From: Konstantin Kletschke <lists@ku-gbr.de>
To: linux-mtd@lists.infradead.org
Subject: Re: General performance of NAND operations i.e mount and ls
Date: Fri, 7 Sep 2007 09:44:51 +0200 [thread overview]
Message-ID: <20070907074450.GB2143@z1.synertronixx> (raw)
In-Reply-To: <1189144034.14370.73.camel@sauron>
Am 2007-09-07 08:47 +0300 schrieb Artem Bityutskiy:
> It is long because you enabled paranoid checks. One of them scans whole
Ah okay, "Extra self checks"...
> media and makes sure it is really empty and contains only 0xFFs. You may
> disable paranoid checks to make it faster.
I disabled these.
> Yeah, your flash driver is not OK. It reports 2 in mtd->subpage_sft, but
> it is unable to write in sub-page chunks (512 bytes) - it returns -EIO.
Hm okay, this may be since this is my first NAND driver and its only a
couple of hours old, so its possible the case I messed up something.
> You should either teach it to write sub-pages (preferable) or report 0
I don't know how to implement these sub pages since I found no example
on how to do this yet, so I tried to disable them. I put a 0 into the
variable, but it is set to 2 in nand base:
printk("mtd->subpage_sft is now %i\n", mtd->subpage_sft);
if (!(chip->options & NAND_NO_SUBPAGE_WRITE) &&
!(chip->cellinfo & NAND_CI_CELLTYPE_MSK)) {
switch(chip->ecc.steps) {
case 2:
mtd->subpage_sft = 1;
break;
case 4:
case 8:
mtd->subpage_sft = 2;
break;
}
}
chip->subpagesize = mtd->writesize >> mtd->subpage_sft;
printk("mtd->subpage_sft is now %i\n", mtd->subpage_sft);
gives:
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron NAND 1GiB 3,3V 8-bit)
2 NAND chips detected
mtd->subpage_sft is now 0
mtd->subpage_sft is now 2
Scanning device for bad blocks
Creating 1 MTD partitions on "NAND 1GiB 3,3V 8-bit":
0x00000000-0x80000000 : "NAND Flash"
Hm, I investigate where this comes from ATM.
Regards Konsti
PS.: Your examples of NAND performance are astonishing, but I don't see
where I even could waste performance on my setup :-)
--
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
next prev parent reply other threads:[~2007-09-07 7:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 8:12 General performance of NAND operations i.e mount and ls Konstantin Kletschke
2007-09-06 8:27 ` Artem Bityutskiy
2007-09-06 8:44 ` Konstantin Kletschke
2007-09-06 9:11 ` Artem Bityutskiy
2007-09-06 9:37 ` Konstantin Kletschke
2007-09-06 10:53 ` Artem Bityutskiy
2007-09-06 11:21 ` Artem Bityutskiy
2007-09-06 11:11 ` Artem Bityutskiy
2007-09-06 16:03 ` Konstantin Kletschke
2007-09-07 5:47 ` Artem Bityutskiy
2007-09-07 7:44 ` Konstantin Kletschke [this message]
2012-06-25 12:01 ` JFFS2 CRC problems Stefan Roese
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=20070907074450.GB2143@z1.synertronixx \
--to=lists@ku-gbr.de \
--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