From: Nethra <nethra_gmit@yahoo.co.in>
To: linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] jffs2 file system
Date: Fri, 23 Feb 2007 19:38:05 -0800 (PST) [thread overview]
Message-ID: <9130715.post@talk.nabble.com> (raw)
In-Reply-To: <10456.15332.qm@web307.biz.mail.mud.yahoo.com>
mkfs.jffs2 -r /mnt -e 0x20000 -o image.jffs2 -b
board is PQ2FADS-ZU, u-boot is u-boot-1.1.1 and linux is montavista2.6.10
is mkfs.jffs2 is architecture dependent?
nethra
Ben Warren wrote:
>
>
> --- Nethra <nethra_gmit@yahoo.co.in> wrote:
>
>>
>>
>> thanks ben,
>>
>> I have already tried to build jffs2 image as per
>> link mentioned using
>> mkfs.jffs2 utility, but mkfs.jffs2 is absent in
>> host...so i downloded
>> mkfs.jffs2 from net and used the same to create the
>> image.Is it the correct
>> way?
>>
>
> Sounds reasonable.
>
>> it is giveing error when booting...
>>
>> nethra
>
> OK, what's the error? Did you set the endianness
> correctly when using mkfs.jffs2?
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>
--
View this message in context: http://www.nabble.com/jffs2-file-system-tf3271928.html#a9130715
Sent from the linuxppc-embedded mailing list archive at Nabble.com.
next prev parent reply other threads:[~2007-02-24 3:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 10:16 jffs2 file system Nethra
2007-02-22 10:27 ` Juergen Beisert
2007-02-22 10:58 ` [PATCH] " Nethra
2007-02-22 11:29 ` Juergen Beisert
2007-02-23 4:28 ` Nethra
2007-02-23 14:55 ` Ben Warren
2007-02-24 3:19 ` Nethra
2007-02-24 3:25 ` Ben Warren
2007-02-24 3:38 ` Nethra [this message]
2007-02-24 3:45 ` Nethra
2007-02-22 11:44 ` Josh Boyer
2007-02-24 8:38 ` [PATCH] " Nethra
2007-02-24 17:30 ` Juergen Beisert
2007-02-26 3:28 ` Nethra
2007-02-24 22:15 ` Ben Warren
2007-02-26 3:04 ` Nethra
2007-02-26 9:14 ` Nethra
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=9130715.post@talk.nabble.com \
--to=nethra_gmit@yahoo.co.in \
--cc=linuxppc-embedded@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.