From: Martin Egholm Nielsen <martin@egholm-nielsen.dk>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: Reading or writing jffs2 - how?
Date: Tue, 21 Dec 2004 10:01:16 +0100 [thread overview]
Message-ID: <41C7E65C.7030002@egholm-nielsen.dk> (raw)
In-Reply-To: <87ekhkc26l.fsf@deepthought.outer.space.org>
Hi Detlev,
>>The problem has been solved...
>>The reason that "ls" didn't work from u-boot, was that the boards'
>>u-boot config-file included an erroneous nand-size:
>>#define CONFIG_JFFS2_NAND_SIZE 64*1024*1024
> Yes, I was about to check the options available in U-Boot and ask you
> to verify those but you beat me to it.
:-)
>>My board had only one configuration-file associated, but multiple
>>nand-size configurations.
>>The jffs2-image problems were related to the endianess problems of
>>mkfs.jffs2:
>>http://lists.infradead.org/pipermail/linux-mtd/2004-January/009091.html
> Another reason for using our ELDK - it has a working mkfs.jff2 ;)
Noo?! I used mkfs.jffs2 from ELDK 3.0:
# mkfs.jffs2 --version
mkfs.jffs2 revision 1.25
# which mkfs.jffs2
/usr/local/eldk/usr/bin/mkfs.jffs2
# cat /usr/local/eldk/version
ELDK version 3.0
ppc_4xx: Build 2004-02-16
But ofcourse, I guess the above error blocked u-boot from putting the
correct image in the nand...
BR,
Martin Egholm
next prev parent reply other threads:[~2004-12-21 9:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-15 12:56 [U-Boot-Users] Reading or writing jffs2 - how? Martin Egholm Nielsen
2004-12-15 20:47 ` Detlev Zundel
2004-12-15 20:56 ` Detlev Zundel
2004-12-16 15:11 ` [U-Boot-Users] " Martin Egholm Nielsen
2004-12-16 15:17 ` Martin Egholm Nielsen
2004-12-20 14:09 ` Martin Egholm Nielsen
2004-12-20 17:25 ` Detlev Zundel
2004-12-21 9:01 ` Martin Egholm Nielsen [this message]
2004-12-21 9:12 ` Wolfgang Denk
2004-12-21 9:30 ` Martin Egholm Nielsen
2004-12-21 12:07 ` Wolfgang Denk
2004-12-21 12:46 ` Martin Egholm Nielsen
2004-12-21 19:19 ` Detlev Zundel
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=41C7E65C.7030002@egholm-nielsen.dk \
--to=martin@egholm-nielsen.dk \
--cc=u-boot@lists.denx.de \
/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