From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] user question about ubi nand
Date: Sat, 27 Feb 2016 23:12:23 +0100 [thread overview]
Message-ID: <87r3fxreew.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <56D19A42.2000809@mind.be> (Arnout Vandecappelle's message of "Sat, 27 Feb 2016 13:44:50 +0100")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Hi,
>> Thanks, that config was hidden behind another one, and a little tricky
>> to find, but once I knew what I wanted it worked great.
> Ah yes, it makes sense from the perspective of the buildroot logic (buildroot
> primarily builds a filesystem, and for ubifs you can optionally embed that into
> a UBI image, and only in that case there is a config file possible). But from a
> user it is not completel logical.
> We should perhaps restructure the filesystem creation a little into a part
> about the actual filesystem and a part about making images out of the
> filesystems. Because we now already have a few different ways of making images
> that are not just filesystems (isohybrid, ubi). And in the defconfigs we use
> genimage instead...
FYI, I think it makes sense to add a genimage (post-)filesystem option,
now that we use it is in several defconfigs.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2016-02-27 22:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 3:34 [Buildroot] user question about ubi nand Steve Calfee
2016-02-24 9:49 ` Jörg Krause
2016-02-24 15:59 ` Steve Calfee
2016-02-24 23:00 ` Arnout Vandecappelle
2016-02-25 21:14 ` Steve Calfee
2016-02-27 12:44 ` Arnout Vandecappelle
2016-02-27 22:12 ` Peter Korsgaard [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=87r3fxreew.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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