From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] migrating a BSP from 2012.03.0 to 2019.03.1 ,
Date: Thu, 18 Apr 2019 16:19:33 +0200 [thread overview]
Message-ID: <20190418141933.kcigkjqx6pmh3row@pengutronix.de> (raw)
In-Reply-To: <DM6PR02MB5977E7EBDD5AD5C9AADD5A9BFD280@DM6PR02MB5977.namprd02.prod.outlook.com>
On Fri, Apr 12, 2019 at 03:27:20PM +0000, Patrick Murray wrote:
> That was a path problem.
>
> I am now getting an error "git binary diffs"
>
> applying '0053-ENGR00141654-Mx53-SMD-Add-audio-support-for-upgradin.patch'
> patching file arch/arm/mach-mx5/board-mx53_loco.c
> patching file arch/arm/mach-mx5/board-mx53_smd.c
> applying '0054-ENGR00141732-SDMA-Fix-bootup-stop-at-sdma-firmware-l.patch'
> patching file drivers/dma/imx-sdma.c
> patching file firmware/Makefile
> File firmware/imx/sdma/sdma-imx25-to1.bin: git binary diffs are not supported.
> File firmware/imx/sdma/sdma-imx31-to1.bin: git binary diffs are not supported.
> File firmware/imx/sdma/sdma-imx31-to2.bin: git binary diffs are not supported.
> File firmware/imx/sdma/sdma-imx35-to1.bin: git binary diffs are not supported.
> File firmware/imx/sdma/sdma-imx35-to2.bin: git binary diffs are not supported.
> File firmware/imx/sdma/sdma-imx50-to1.bin: git binary diffs are not supported.
> File firmware/imx/sdma/sdma-imx51-to3.bin: git binary diffs are not supported.
> File firmware/imx/sdma/sdma-imx53-to1.bin: git binary diffs are not supported.
> make: *** [/opt/lib/ptxdist-2019.03.1/rules/post/ptxd_make_world_extract.make:34: /opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4/platform-phyFLEX-i.MX6/state/kernel-header.extract] Error 1
> make: Target '/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4/platform-phyFLEX-i.MX6/state/prolink6_driver.compile' not remade because of errors.
This is a problem with your BSP. You have patches that can only be applied
with git. You can do that by calling ptxdist with '--git' or enable it in
'ptxdist setup'. Note: this can break other packages that may react
differently when the source tree is a git repository.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2019-04-18 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 12:33 Patrick Murray
2019-04-12 13:33 ` Ian Abbott
2019-04-12 14:12 ` Michael Olbrich
2019-04-12 15:27 ` Patrick Murray
2019-04-18 14:19 ` Michael Olbrich [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=20190418141933.kcigkjqx6pmh3row@pengutronix.de \
--to=m.olbrich@pengutronix.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