From: Alexander Dahl <post@lespocky.de>
To: Alex Vazquez <avazquez.dev@gmail.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Generate UBIFS Images
Date: Thu, 21 Jan 2021 07:54:13 +0100 [thread overview]
Message-ID: <20210121065412.im6mt7aw7darqyfg@falbala.internal.home.lespocky.de> (raw)
In-Reply-To: <CAOTEMUSuHyC0QZsh-_qxU2cFaCZME-N4kJmq79eXA0ErVei0UA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1802 bytes --]
Hello Alex,
On Wed, Jan 20, 2021 at 11:56:55PM +0100, Alex Vazquez wrote:
> I have some questions about generating UBIFS images.
> First, I am using ptxdist-2018.05. For this version, I use Generate
> UBIFS Images (NO new version).
I would recommend to use the new approach, that should also work with
ptxdist-2018.05 already.
> - For the latest versions of ptxdist, it is possible to indicate
> arguments to generate the *.ubifs?
It is. Recent ptxdist versions use 'genimage' [1] to create those
images. If the default genimage config files are not sufficient for
you, you can just put your own config to your BSP.
For example: in a BSP for an at91sam9g20 based board with the ptxdist
platform named "foo", I put two files to
'configs/platform-foo/config/images':
- ubi.config
- ubifs.config
You find the files distributed with ptxdist also in 'config/images',
e.g. in /usr/local/lib/ptxdist-2021.01.0/config/images or in the
ptxdist source git tree. You can start with those files and adapt them
to your needs. (For ubi/ubifs you actually should pick those as a
start, because there are several placeholders for flash memory
parameters to be substituted in there).
There's some documentation on image packages, I found this:
https://www.ptxdist.org/doc/ref_make_variables.html#image-packages
Not sure if someone should write some more explanation on that?
genimage itself is documented at [1] however.
Greets
Alex
[1] https://github.com/pengutronix/genimage/
--
/"\ 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: 181 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2021-01-21 6:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 22:56 Alex Vazquez
2021-01-21 6:54 ` Alexander Dahl [this message]
2021-01-24 18:29 ` Alex Vazquez
2021-01-25 5:55 ` Sascha Hauer
2021-01-25 12:01 ` 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=20210121065412.im6mt7aw7darqyfg@falbala.internal.home.lespocky.de \
--to=post@lespocky.de \
--cc=avazquez.dev@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