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 14:27:12 +0100 [thread overview]
Message-ID: <CABDcavaRsV=RgPKrzYXoki869pUFVAyGvz-a63XzaS1U=Ai=3g@mail.gmail.com> (raw)
In-Reply-To: <1830142.py3oA8sHQX@ada>
Hi Alexander,
El vie., 21 dic. 2018 a las 14:02, Alexander Dahl (<ada@thorsis.com>) escribió:
>
> Hei hei,
>
> Am Freitag, 21. Dezember 2018, 13:17:52 CET schrieb Guillermo Rodriguez
> Garcia:
> > I want to have ptxdist copy the generated kernel and uboot binaries to
> > the /boot directory in the target filesystem image.
>
> What about KERNEL_INSTALL in platformconfig? Do you have more files which are
> not covered by that?
I didn't know about that option. That's good -- it covers the kernel
and dts file. But I also need to copy the SPL and uboot binaries.
>
> > For this I need to setup a package that would depend on the kernel and
> > uboot packages, so that these are generated first. In the .in file I
> > added the following:
> >
> > select U_BOOT if ROOTFS_EXTRA_COPY_UBOOT_FILES
> > select KERNEL if ROOTFS_EXTRA_COPY_KERNEL_FILES
> >
> > But for u-boot I get the following:
> >
> > warning: 'select' used by config symbol 'ROOTFS_EXTRA' refers to
> > undefined symbol 'U_BOOT'
> >
> > Why is this, and how can I solve it?
>
> 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 ?
Thanks,
Guillermo
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-12-21 13:27 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 [this message]
2018-12-21 14:16 ` Alexander Dahl
2018-12-21 15:52 ` 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='CABDcavaRsV=RgPKrzYXoki869pUFVAyGvz-a63XzaS1U=Ai=3g@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