From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Question related to multiple UBI volumes in UBI image
Date: Wed, 26 Oct 2016 11:15:00 +0200 [thread overview]
Message-ID: <20161026091500.msd7sbhm3uhltdqt@pengutronix.de> (raw)
In-Reply-To: <CABDcavYHjkcsmKGfufiptbOT5Gw9S264aZnEHTxnmWDhkSocNw@mail.gmail.com>
Hi,
On Wed, Oct 26, 2016 at 10:16:05AM +0200, Guillermo Rodriguez Garcia wrote:
> I have two questions related to handling of multiple UBI volumes in ptxdist.
>
> 1. I see it is possible to create an additional "data" volume. Is it
> possible to tell ptxdist what to put in this additional volume? Or is
> it always empty?
If you use the new image mechanism, then that's possible. The config file
is config/images/ubi.config and you just need to copy it to the same
location in your BSP and add another 'partition' with the data ubifs image.
You should also overwrite the .in file (platforms/image-root-ubi.in) to add
the dependency to your data image.
> 2. It looks like the autoresize flag is always set in the ubinize
> config file that is used to generate the ubi images. Is it possible to
> configure this?
> Related: How does ubi handle an image that has more than one volume
> with the autoresize flag set in all of them?
I think ubinize will fail. Afaik only one autoresize volume is supported by
ubi.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-10-26 9:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 8:16 Guillermo Rodriguez Garcia
2016-10-26 9:10 ` Guillermo Rodriguez Garcia
2016-10-26 9:15 ` Michael Olbrich [this message]
2016-10-26 14:53 ` Guillermo Rodriguez Garcia
2016-10-26 15:02 ` Michael Olbrich
2016-10-26 15:11 ` Guillermo Rodriguez Garcia
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=20161026091500.msd7sbhm3uhltdqt@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.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