All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Sam Nelson <sam.nelson@ti.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: [PATCH] mpm-transport: Add new recipe for multiproc transport library and test code
Date: Thu, 18 Dec 2014 12:31:50 -0500	[thread overview]
Message-ID: <20141218173150.GJ29971@edge> (raw)
In-Reply-To: <1418918057-13812-1-git-send-email-sam.nelson@ti.com>

On Thu, Dec 18, 2014 at 10:54:17AM -0500, Sam Nelson wrote:
> - mpm-transport provide basic transport layer for moving data between different processing nodes
> - Support communication with the process nodes using shared memory and hyperlink interface
> 
> Signed-off-by: Sam Nelson <sam.nelson@ti.com>
> ---
>  recipes-ti/mpm-transport/mpm-transport_git.bb |   37 +++++++++++++++++++++++++
>  1 file changed, 37 insertions(+)
>  create mode 100644 recipes-ti/mpm-transport/mpm-transport_git.bb
> 
> diff --git a/recipes-ti/mpm-transport/mpm-transport_git.bb b/recipes-ti/mpm-transport/mpm-transport_git.bb
> new file mode 100644
> index 0000000..fe67195
> --- /dev/null
> +++ b/recipes-ti/mpm-transport/mpm-transport_git.bb
> @@ -0,0 +1,37 @@
> +DESCRIPTION = "Multiproc transport layer for KeyStone devices: Provide basic transport layer for moving data between different processing nodes"
> +HOMEPAGE = "http://git.ti.com/cgit/cgit.cgi/keystone-linux/mpm-transport.git"
> +LICENSE = "BSD-3-Clause & MIT"
> +LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=2c17cd1dc60dc06a4c4f2a2c45472a51"
> +COMPATIBLE_MACHINE = "keystone"
> +DEPENDS = "common-csl-ip hyplnk-lld edma3-lld mmap-lld"
> +
> +SRC_URI = "git://git.ti.com/keystone-linux/mpm-transport.git;protocol=git;branch=${BRANCH}"
> +
> +BRANCH = "master"
> +# This commit corresponds to tag DEV.MPM-TRANSPORT-01.00.04.00E
> +SRCREV = "56640c6296f9f4816140364b7620b1d1a483ac40"
> +PV = "1.0.4.0"
> +PR = "r0"
> +
> +S = "${WORKDIR}/git"
> +
> +PACKAGES =+ "${PN}-test"
> +FILES_${PN}-test = "${bindir}/mpm_transport_test.out ${bindir}/mpm_transport_hyplnk_loopback.out ${bindir}/mpm_transport_hyplnk_remote.out ${bindir}/mpm_transport_hyplnk_loopback_dma.out ${bindir}/mpm_transport_hyplnk_loopback64.out"
> +
> +do_compile () {
> +	cd ${S}
> +	make PDK_INSTALL_PATH=${STAGING_INCDIR}
> +}
> +
> +do_install() {
> +	make installbin BASE_DIR=${S} INSTALL_BIN_BASE_DIR=${D}/${bindir}
> +
> +	install -d ${D}${includedir}/
> +	install -c -m 755 ${S}/include/* ${D}${includedir}/

Do you want to make a ${PN}-dev package with those headers for the devkit? Or 
do you only need those on the target?


> +	install -d ${D}${libdir}/
> +	cp  -a ${S}/lib/* ${D}${libdir}/
> +
> +	install -d ${D}${sysconfdir}/mpm/
> +	install -c -m 755 ${S}/scripts/mpm_config.json ${D}${sysconfdir}/mpm/mpm_config.json
> +}
> -- 
> 1.7.9.5
> 
> -- 
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti


  reply	other threads:[~2014-12-18 17:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-18 15:54 [PATCH] mpm-transport: Add new recipe for multiproc transport library and test code Sam Nelson
2014-12-18 17:31 ` Denys Dmytriyenko [this message]
2014-12-18 17:38   ` Nelson, Sam
2014-12-18 17:40     ` Denys Dmytriyenko
2014-12-18 17:40       ` Nelson, Sam

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=20141218173150.GJ29971@edge \
    --to=denys@ti.com \
    --cc=meta-ti@yoctoproject.org \
    --cc=sam.nelson@ti.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.