From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] ti-cgt-pru: add package for PRU Host toolchain
Date: Thu, 24 Nov 2016 16:44:20 +0100 [thread overview]
Message-ID: <20161124164420.792cab0f@free-electrons.com> (raw)
In-Reply-To: <1479324273-13589-1-git-send-email-ash.charles@savoirfairelinux.com>
Hello,
On Wed, 16 Nov 2016 14:24:32 -0500, Ash Charles wrote:
> diff --git a/package/ti-cgt-pru/Config.in.host b/package/ti-cgt-pru/Config.in.host
> new file mode 100644
> index 0000000..440f774
> --- /dev/null
> +++ b/package/ti-cgt-pru/Config.in.host
> @@ -0,0 +1,11 @@
> +config BR2_PACKAGE_HOST_TI_CGT_PRU
> + bool "host ti-cgt-pru"
> + depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86"
depends on BR2_arm
would probably be nice here.
> + help
> + This package provides the Code Generation Tools for the PRU
> + unit found on some TI processors e.g. AM3358.
> +
> + Note: this is a binary cross toolchain that runs on x86 hosts
> + targeting ARM PRU cores.
No need to align this second line.
> index 0000000..a4c8566
> --- /dev/null
> +++ b/package/ti-cgt-pru/ti-cgt-pru.mk
> @@ -0,0 +1,29 @@
> +################################################################################
> +#
> +# ti-cgt-pru
> +#
> +################################################################################
> +
> +TI_CGT_PRU_VERSION = 2.1.3
> +TI_CGT_PRU_SOURCE = ti_cgt_pru_$(TI_CGT_PRU_VERSION)_linux_installer_x86.bin
> +TI_CGT_PRU_SITE = "http://software-dl.ti.com/codegen/esd/cgt_public_sw/PRU/$(TI_CGT_PRU_VERSION)/"
Remove double quotes.
> +TI_CGT_PRU_LICENSE = BSD-3c, MIT, TI-TSPA
> +TI_CGT_PRU_LICENSE_FILES = PRU_Code_Generation_Tools_2.1.x_manifest.html
> +
> +define HOST_TI_CGT_PRU_EXTRACT_CMDS
> + chmod +x $(DL_DIR)/$(TI_CGT_PRU_SOURCE)
> + $(DL_DIR)/$(TI_CGT_PRU_SOURCE) --prefix $(@D) --mode unattended
Add:
mv $(@D)/ti-cgt-pru_2.1.3/* $(@D)
rmdir $(@D)/ti-cgt-pru_2.1.3/
> +endef
> +
> +# Since this is largely prebuilt toolchain and likes to live in its own
> +# directory, put is in $(HOST_DIR)/ti-cgt-pru_$(CGT_PRU_VERION)
> +# Packages wanting to use this toolchain need to use this path as TI's
> +# standard PRU_CGT path.
> +
> +PRU_CGT = $(HOST_DIR)/ti-cgt-pru_$(TI_CGT_PRU_VERSION)
I'd think I'd prefer:
TI_PRU_CGT = $(HOST_DIR)/usr/share/ti-cgt-pru/
> +define HOST_TI_CGT_PRU_INSTALL_CMDS
> + $(INSTALL) -d $(PRU_CGT)
We usually use 'mkdir -p' instead.
> + cp -af $(@D)/$(notdir $(PRU_CGT)) $(HOST_DIR)
cp -dpfr $(@D)/* $(TI_PRU_CGT)
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-11-24 15:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 19:24 [Buildroot] [PATCH 1/2] ti-cgt-pru: add package for PRU Host toolchain Ash Charles
2016-11-16 19:24 ` [Buildroot] [PATCH 2/2] ti-pru-support: add staging files for PRU firmware Ash Charles
2016-11-24 15:48 ` Thomas Petazzoni
2016-11-24 20:25 ` Arnout Vandecappelle
2016-11-21 23:51 ` [Buildroot] [PATCH 1/2] ti-cgt-pru: add package for PRU Host toolchain Ash Charles
2016-11-24 15:44 ` Thomas Petazzoni [this message]
2016-11-24 20:16 ` Arnout Vandecappelle
2016-11-24 20:07 ` Arnout Vandecappelle
2016-11-25 17:49 ` [Buildroot] [PATCH v2 1/3] " Ash Charles
2016-11-25 17:49 ` [Buildroot] [PATCH v2 2/3] pru-software-support: add library for PRU firmware Ash Charles
2016-11-26 11:27 ` Arnout Vandecappelle
2016-11-26 14:05 ` Thomas Petazzoni
2016-11-26 14:34 ` Ash Charles
2016-11-25 17:50 ` [Buildroot] [PATCH v2 3/3] pru-sample: add sample PRU application Ash Charles
2016-11-25 20:30 ` Thomas Petazzoni
2016-11-26 11:22 ` Arnout Vandecappelle
2016-11-26 14:06 ` Thomas Petazzoni
2016-11-27 12:41 ` Ash Charles
2016-11-27 13:47 ` Thomas Petazzoni
2016-11-28 11:34 ` Ash Charles
2016-11-29 23:41 ` Arnout Vandecappelle
2016-11-30 1:12 ` Ash Charles
2016-11-26 11:07 ` [Buildroot] [PATCH v2 1/3] ti-cgt-pru: add package for PRU Host toolchain Arnout Vandecappelle
2016-11-26 14:51 ` Ash Charles
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=20161124164420.792cab0f@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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