From: Karl Krach <mailinglists@blueSpirit.la>
To: u-boot@lists.denx.de
Subject: [U-Boot] Problems with creating an UBIFS partition with uboot
Date: Sat, 19 Jun 2010 12:29:13 +0200 [thread overview]
Message-ID: <4C1C9BF9.50607@blueSpirit.la> (raw)
In-Reply-To: <AANLkTikEmw9mceVUsSfLfuLDIhQYmmnfR9sT-CFMbZXi@mail.gmail.com>
Hello Matthew,
thanks a lot, I will try this approach on Monday, when I'm back at work.
> At a glance, one problem is the use of ubinize, which is intended to
> work when doing "bare NAND" flashing with no awareness of UBI. I.e.
> if you tried these steps with "rootfs.ubifs" rather than
> "rootfs.ubi.img", they'd probably work. However, that doesn't explain
> why the last attempt (doing a straight "nand write") also fails, since
> that should work with the ubinized image.
I like this apprach, since buildroot creates an ubifs file for me, so I
don't need the extra step to create the image with ubinize.
Best regards,
Charly
prev parent reply other threads:[~2010-06-19 10:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 18:37 [U-Boot] Problems with creating an UBIFS partition with uboot Karl Krach
2010-06-18 22:02 ` Matthew L. Creech
2010-06-19 10:29 ` Karl Krach [this message]
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=4C1C9BF9.50607@blueSpirit.la \
--to=mailinglists@bluespirit.la \
--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