From: "A.L. Klyutchenya" <asoneofus@nm.ru>
To: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: K9F5608U0B-YIB0000: 528 byte in page, or 512?
Date: Tue, 22 Apr 2003 13:06:58 +0400 [thread overview]
Message-ID: <200304221249.50740.asoneofus@nm.ru> (raw)
In-Reply-To: <200304021228.44997.tglx@linutronix.de>
2 Апрель 2003 14:28, Thomas Gleixner написал:
> On Tuesday 01 April 2003 13:02, A.L. Klyutchenya wrote:
> > Dear sir,
> > Thank you for quick answer.
> >
> > 1 Апрель 2003 07:36, Charles Manning написал:
> > > This is NAND flash. Do not try to treat it as NOR flash.
> > > Use it with mtd/nand and use YAFFS or JFFS2 file system.
> >
> > I want to write the first image, for booting system. I
> > create this image (with kernel, MTD & Co). I have a
> > possibility his write. Herewith: I have an physical access
> > to page: size 256+256+16, and block on 32 pages. While NO
> > MTD and NO kernel!
> >
> > > You must write NAND in whole pages, not on a per-byte
> > > basis.
> >
> > I understand that page it is necessary to write, but what
> > bring the first image: chain on 512+512.... or 512+16 free +
> > 512+16 free...
> >
> > As even so write? :-) (to hrdware-level)
>
> Please read http://linux-mtd.infraded.org/tech/nand.html
I read, and don't find answer.
1) make jffs2 image: correct erase block-size for NAND (512+16
page x 32) is 0x4200 or (512 page x 32) 0x4000?
2) for writing jffs2 image to NAND use only 512byte space on each
page, or 512+16?
--
ВсехБлаг!
____ __
/ | / / А. Л. Клютченя
/ /| | / / (asoneofus)
/ /_| |/ / mail: asoneofus@kde.ru
/ ____ _ \ www: http://www.qt.kde.ru
/ / | | \ \ icq: 113679387
/_/ |_| \_\
next prev parent reply other threads:[~2003-04-22 9:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 22:07 K9F5608U0B-YIB0000: 528 byte in page, or 512? A.L. Klyutchenya
2003-04-01 3:36 ` Charles Manning
2003-04-01 11:02 ` A.L. Klyutchenya
2003-04-02 10:28 ` Thomas Gleixner
2003-04-22 9:06 ` A.L. Klyutchenya [this message]
2003-04-23 20:32 ` Charles Manning
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=200304221249.50740.asoneofus@nm.ru \
--to=asoneofus@nm.ru \
--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