mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Riesch <michael.riesch@wolfvision.net>
To: ptxdist@pengutronix.de, m.olbrich@pengutronix.de
Cc: m.tretter@pengutronix.de, Sascha Hauer <sha@pengutronix.de>
Subject: Re: [ptxdist] [PATCH v4 4/4] barebox: add integration of firmware blobs
Date: Mon, 24 Jan 2022 09:33:13 +0100	[thread overview]
Message-ID: <ab25cad2-9c4e-6827-24a7-1bac525b2fa1@wolfvision.net> (raw)
In-Reply-To: <20220121094744.GE12549@pengutronix.de>

Hello Michael,

On 1/21/22 10:47, Michael Olbrich wrote:
> [...]
> We're looking at what to do in PTXdist right now. Currently, the idea is
> that one package dumps all files somewhere in sysroot. Then we have some
> minimal barebox integration that adds the individual files with source and
> destination to a list. And in the barebox prepare stage all files in that
> list are copied into the barebox source tree.
> 
> Just dumping all files from a tarball into the barebox source tree would be
> easier, but I don't think its feasible. Just look at the current case: We
> have an upstream Tarball with fixed names that include versions. So we need
> to do some mapping somewhere anyways.
> 
> But having consistent locations where to put the files would make writing
> the mappings easier.
> 
> Michael

If I understand correctly the remaining open issue are the mappings from
files in sysroot (installed by binary vendor packages and/or open-source
packages) to files in the barebox source tree. These mappings are
implemented in the barebox.insertvendorhere.make rule files, which are
likely to be maintained in board support packages.

Therefore I am going to submit a v5 of the series that adds
 - the section for binary firmware blobs
 - the firmware-rockchip package as example of a binary vendor package
 - the generic helpers to inject files into a package source tree
 - the generic usage of those helpers in the barebox package

(i.e., the generic part) and includes a mapping barebox.rockchip.make,
which implements the only currently available (and hence best) way to
integrate sdram init, OPTEE and TF-A for recent Rockchip RK356x boards,
to showcase how this feature is supposed to be used. This mapping shall
be marked as RFC and can be considered for inclusion in ptxdist (as
reasonable default that can be overwritten) or (at a later stage) in
DistroKit.

This way the exact form of the mappings can be discussed further and the
generic part is moved towards being merged. Sounds good?

Best regards,
Michael

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de


      reply	other threads:[~2022-01-24  8:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-20 12:08 [ptxdist] [PATCH v4 0/4] Add support for Rockchip " Michael Riesch
2021-12-20 12:08 ` [ptxdist] [PATCH v4 1/4] platforms: add section for non-free " Michael Riesch
2021-12-20 12:08 ` [ptxdist] [PATCH v4 2/4] add package for rockchip firmware binaries Michael Riesch
2022-01-07 13:56   ` Michael Olbrich
2022-01-10  6:05     ` Michael Riesch
2022-01-21  7:28       ` Michael Olbrich
2021-12-20 12:08 ` [ptxdist] [PATCH v4 3/4] scripts: add helper to inject files into a source directory Michael Riesch
2021-12-20 12:08 ` [ptxdist] [PATCH v4 4/4] barebox: add integration of firmware blobs Michael Riesch
2022-01-07 14:09   ` Michael Olbrich
2022-01-10  6:39     ` Michael Riesch
2022-01-21  7:54       ` Michael Olbrich
2022-01-21  8:43         ` Sascha Hauer
2022-01-21  9:47           ` Michael Olbrich
2022-01-24  8:33             ` Michael Riesch [this message]

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=ab25cad2-9c4e-6827-24a7-1bac525b2fa1@wolfvision.net \
    --to=michael.riesch@wolfvision.net \
    --cc=m.olbrich@pengutronix.de \
    --cc=m.tretter@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    --cc=sha@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