From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot creates broken jffs2 image
Date: Tue, 9 Nov 2010 18:43:10 +0100 [thread overview]
Message-ID: <20101109184310.257314b0@surf> (raw)
In-Reply-To: <AANLkTi=zp_NcMLOBTK5v+Hc=ryLOwT5YuNg9TXrrtdu=@mail.gmail.com>
Hello,
On Tue, 9 Nov 2010 16:25:23 +0100
Bj?rn Forsman <bjorn.forsman@gmail.com> wrote:
> 3) look at the build log and retrieve the mkfs.jffs2 command that
> buildroot used:
> echo
> " /home/bjornfor/forks/buildroot-skipper/output/host/usr/sbin/mkfs.jffs2
> -e 0x20000 -p -l -s 0x800 -n
> -d /home/bjornfor/forks/buildroot-skipper/output/target
> -o /home/bjornfor/forks/buildroot-skipper/output/images/rootfs.jffs2"
> >> /home/bjornfor/forks/buildroot-skipper/output/build/_fakeroot.fs
>
> 4) issue the command with *host* mkfs.jffs2 instead (using the exact
> same arguments):
> mkfs.jffs2 -e 0x20000 -p -l -s 0x800 -n -d
> /home/bjornfor/forks/buildroot-skipper/output/target -o
> /home/bjornfor/forks/buildroot-skipper/output/images/rootfs.jffs2.v2
>
> 5) flash new jffs2 image and mount. This time with *no errors*.
>
> Any ideas on why this is happening?
Not sure, but steps 3) and steps 4) are not identical. In step 3),
mkfs.jffs2 is called by fakeroot, which first creates the device files.
In step 4), you don't have anything creating the device files.
Could you try doing step 4 (i.e calling mkfs.jffs2 directly), but by
calling the mkfs.jffs2 built by Buildroot (in $(HOST_DIR)) ?
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-11-09 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 15:25 [Buildroot] Buildroot creates broken jffs2 image Bjørn Forsman
2010-11-09 17:43 ` Thomas Petazzoni [this message]
2010-11-10 17:29 ` Bjørn Forsman
2010-11-11 9:09 ` Thomas Petazzoni
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=20101109184310.257314b0@surf \
--to=thomas.petazzoni@free-electrons.com \
--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