mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Copying kernel and uboot to /boot in target filesystem image
Date: Fri, 21 Dec 2018 16:52:27 +0100	[thread overview]
Message-ID: <CABDcavaNzbhe9mofXrXF+yR=5QhaX_7LmfN7+jcWseq+cXgDdQ@mail.gmail.com> (raw)
In-Reply-To: <2440974.noABVAjmvV@ada>

Hello,

El vie., 21 dic. 2018 a las 15:16, Alexander Dahl (<ada@thorsis.com>) escribió:
>
> Hello,
>
> Am Freitag, 21. Dezember 2018, 14:27:12 CET schrieb Guillermo Rodriguez
> Garcia:
> > > PTXCONF_U_BOOT is in platformconfig, so I guess your .in file can only
> > > depend on it, if it extends the platformconfig as well, not the normal
> > > ptxconfig?
> > I see. How can I have my .in file "extend" the platformconfig ?
>
> Just move it from the folder 'rules' to 'platforms' or maybe better to config/
> yourplatform/platforms. You call 'make platformconfig' then and find it
> somewhere there.
>
> It's probably good to see some other platform packages in the ptxdist source
> in 'platforms' or in DistroKit e.g. in 'configs/platform-v7a/platforms'. IIRC
> the categories in the first line of the .in file differ.
>
> I'm not sure if all possibilities for the accompaning .make files apply, nor
> if that topic is covered in the documentation, but it should give you a
> starting point.

This got me on the right track, although it looks like it doesn't
matter whether the file is in rules, or platform or whatever -- what
matters is actually the category in the first line of the .in file.
In fact, I already have a modified u-boot.in in my BSP's rules
directory, so I just added a new option there; if this option is
enabled, any selected u-boot files will be installed to /boot in the
target filesystem, in addition to copying them to the platform image
directory.

Thank you for the pointer!

Guillermo

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2018-12-21 15:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-21 12:17 Guillermo Rodriguez Garcia
2018-12-21 13:01 ` Alexander Dahl
2018-12-21 13:27   ` Guillermo Rodriguez Garcia
2018-12-21 14:16     ` Alexander Dahl
2018-12-21 15:52       ` Guillermo Rodriguez Garcia [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='CABDcavaNzbhe9mofXrXF+yR=5QhaX_7LmfN7+jcWseq+cXgDdQ@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