From: Stephan.Linke@epygi.de (Stephan Linke)
To: linux-mtd@lists.infradead.org
Subject: canT use jffs2 with nand
Date: Thu, 6 Mar 2003 17:58:21 +0100 [thread overview]
Message-ID: <FCEAKDJJAPHPLJFINDAJCEHLCOAA.Stephan.Linke@epygi.de> (raw)
Hi,
I'm trying to use some nand chips on my board. Some selfmade tests in the bootloader show that they are already working fin in the
system.
But I have trouble using them in linux.
When trying to use touch to create an empty file on a JFFS2 mounted on the nand I get the following result: "nand_write_ecc: Attempt
to write not page aligned data" which is actualy true since the FS is trying to write only 12 bytes...
I tried to use YAFFS first but the result was more difficult to "translate".
Writing an mounting a cramfs image worked fine.
Any help is appreciated.
Thanks, Stephan
P.S.: I have pretty new MTD and YAFFS sources and a 2.4.18 kernel.
next reply other threads:[~2003-03-06 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 16:58 Stephan Linke [this message]
2003-03-06 21:46 ` canT use jffs2 with nand Thomas Gleixner
2003-03-07 9:46 ` Stephan Linke
2003-03-08 19:36 ` Thomas Gleixner
2003-03-07 11:43 ` Stephan Linke
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=FCEAKDJJAPHPLJFINDAJCEHLCOAA.Stephan.Linke@epygi.de \
--to=stephan.linke@epygi.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