From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Question related to multiple UBI volumes in UBI image
Date: Wed, 26 Oct 2016 11:10:19 +0200 [thread overview]
Message-ID: <CABDcavY1LiaS0pjrP5eOyydwiaa+oj2BGxvaHHPSQVO3ra3eRw@mail.gmail.com> (raw)
In-Reply-To: <CABDcavYHjkcsmKGfufiptbOT5Gw9S264aZnEHTxnmWDhkSocNw@mail.gmail.com>
Partially answering myself:
2016-10-26 10:16 GMT+02:00 Guillermo Rodriguez Garcia
<guille.rodriguez@gmail.com>:
> Hello all,
>
> 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?
>
> 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 now see that the autoresize flag is only set for the "root" UBI
volume, but not for the "data" volume. So the ubi image does not
actually contains two volumes with the autoresize flag set.
However the two questions still remain. I would actually like to
disable autoresize for both volumes, and to put some initial data in
the "data" volume. Does ptxdist support this?
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-10-26 9:10 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 [this message]
2016-10-26 9:15 ` Michael Olbrich
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=CABDcavY1LiaS0pjrP5eOyydwiaa+oj2BGxvaHHPSQVO3ra3eRw@mail.gmail.com \
--to=guille.rodriguez@gmail.com \
--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