From: Michael Olbrich <m.olbrich@pengutronix.de>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Question related to multiple UBI volumes in UBI image
Date: Wed, 26 Oct 2016 17:02:42 +0200 [thread overview]
Message-ID: <20161026150242.ecpac4ie6shr57do@pengutronix.de> (raw)
In-Reply-To: <CABDcavaU6t3cqO8=ONDymmM3-+kD_V5YQ0AfWn1OBqT_e=vukA@mail.gmail.com>
On Wed, Oct 26, 2016 at 04:53:21PM +0200, Guillermo Rodriguez Garcia wrote:
> 2016-10-26 11:15 GMT+02:00 Michael Olbrich <m.olbrich@pengutronix.de>:
> > 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.
>
> Thank you for your answer, I didn't know about the "new image mechanism".
>
> I see it depends on an external 'genimage' tool. I am a bit nervous
> about switching at this stage. What I ended up doing is creating a
> local rules/post/image_ubi.make file in my BSP. This just redefines
> the $(IMAGEDIR)/root.ubi target so that instead of using the default
> ubi.ini file from ptxdist, it will use a custom ubi.ini file.
>
> I assume that I can override a .make file in rules/post just I would
> override a .make file in rules/. I have confirmed that this works -- I
> just want to make sure it is not working just out of luck :-)
>
> Do you see any obvious problems with this approach?
rules/post/ works differently. You don't replace files from ptxdist. So
you'll get some ugly 'warning: overriding recipe for target ...' warnings,
right? That was one of the reasons for the new image mechanism.
Other than that it should work fine. Your files in rules/post/ will always
be sourced last.
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 15:02 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
2016-10-26 14:53 ` Guillermo Rodriguez Garcia
2016-10-26 15:02 ` Michael Olbrich [this message]
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=20161026150242.ecpac4ie6shr57do@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