From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Extra args to mkfs.ubifs with new image creation options
Date: Thu, 12 Dec 2019 20:13:38 +0100 [thread overview]
Message-ID: <20191212191337.3ngya23f5l7o3wea@falbala.internal.home.lespocky.de> (raw)
In-Reply-To: <CABDcavb8mbB-BUMfxc+nx4ai_-YJ0WwHOTp3tqvNR58C5AsArg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1182 bytes --]
Hello,
On Thu, Dec 12, 2019 at 07:23:10PM +0100, Guillermo Rodriguez Garcia wrote:
> I am trying to switch from the "legacy" ptxdist image creation options
> to the new system based on genimage. This is because I want to
> generate an ubi image out of three separate volumes, and the legacy
> approach does not support this very well.
Did you already find the genimage docs? Look for pengutronix at
GitHub. genimage works with config files, everything is set there.
> I am still trying to see how it all works; first issue I have found
> is, how to specify extra arguments to mkfs.ubifs? In particular I need
> to add --space-fixup; however I don't see any place where I could
> configure this with the new system.
ptxdist ships those genimage config files in folder 'config/images'
and you can "overwrite" those in your BSP as you would do with rules.
HTH & Greets
Alex
--
/"\ ASCII RIBBON | »With the first link, the chain is forged. The first
\ / CAMPAIGN | speech censured, the first thought forbidden, the
X AGAINST | first freedom denied, chains us all irrevocably.«
/ \ HTML MAIL | (Jean-Luc Picard, quoting Judge Aaron Satie)
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 92 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-12-12 19:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 18:23 Guillermo Rodriguez Garcia
2019-12-12 19:13 ` Alexander Dahl [this message]
2019-12-13 8:32 ` Guillermo Rodriguez Garcia
2019-12-13 16:14 ` Ahmad Fatoum
2019-12-16 12:34 ` 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=20191212191337.3ngya23f5l7o3wea@falbala.internal.home.lespocky.de \
--to=post@lespocky.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