From: Bernhard Fischer <rep.nop@aon.at>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot, NAND flash and missing mkfs.jffs2 option
Date: Tue, 28 Nov 2006 21:15:14 +0100 [thread overview]
Message-ID: <20061128201514.GC27344@aon.at> (raw)
In-Reply-To: <1164737384.456c7b6809f9d@imp3-g19.free.fr>
On Tue, Nov 28, 2006 at 07:09:44PM +0100, julien.boibessot at free.fr wrote:
>Hi !
>
>I have found that on my NAND flash, if I want to burn a JFFS2 rootfs image
>generated with buildroot, I need to add "-n" option to JFFS2_OPTS variable in
>target/jffs2/jffs2.mk Makefile.
>
>Otherwise when mounting my rootfs, I have a lot of warning messages like this
>one:
> CLEANMARKER node found at 0x00...... has totlen 0xc != normal 0x0
>
>Was anybody aware of that special case ?
>Should I send you a patch to support NAND flash ?
I think there is at least one report at bugs.busybox.net about jffs2,
namely an endian fix and maybe another report. It would be great if you
could verify that the endian patch does break nothing for you, so that i
can apply it safely and check if there is already a report WRT jffs2 and
-n. If there is already such a report, then i ask you to be so kind and
to point me to it and also point out further problems you did encounter
with jffs2 (like the -n you mentioned above).
TIA,
Bernhard
next prev parent reply other threads:[~2006-11-28 20:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 18:09 [Buildroot] Buildroot, NAND flash and missing mkfs.jffs2 option julien.boibessot at free.fr
2006-11-28 20:15 ` Bernhard Fischer [this message]
2006-11-29 13:04 ` julien.boibessot at free.fr
2006-11-29 13:17 ` Bernhard Fischer
2006-11-29 17:21 ` julien.boibessot at free.fr
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=20061128201514.GC27344@aon.at \
--to=rep.nop@aon.at \
--cc=buildroot@busybox.net \
/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