From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH][meta-oe] cpupower: add recipes
Date: Tue, 12 Apr 2016 11:05:18 +0200 [thread overview]
Message-ID: <20160412090518.GA2564@jama> (raw)
In-Reply-To: <1459236536-15190-1-git-send-email-rongqing.li@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 2140 bytes --]
On Tue, Mar 29, 2016 at 03:28:56PM +0800, rongqing.li@windriver.com wrote:
> From: Roy Li <rongqing.li@windriver.com>
>
> cpupower is tools to shows and sets processor power related values
>
> Signed-off-by: Roy Li <rongqing.li@windriver.com>
> ---
> meta-oe/recipes-kernel/cpupower/cpupower.bb | 41 +++++++++++++++++++++++++++++
> 1 file changed, 41 insertions(+)
> create mode 100644 meta-oe/recipes-kernel/cpupower/cpupower.bb
>
> diff --git a/meta-oe/recipes-kernel/cpupower/cpupower.bb b/meta-oe/recipes-kernel/cpupower/cpupower.bb
> new file mode 100644
> index 0000000..d53deac
> --- /dev/null
> +++ b/meta-oe/recipes-kernel/cpupower/cpupower.bb
> @@ -0,0 +1,41 @@
> +SUMMARY = "Shows and sets processor power related values"
> +DESCRIPTION = "cpupower is a collection of tools to examine and tune power \
> +saving related features of your processor."
> +LICENSE = "GPLv2"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
> +DEPENDS = "pciutils"
> +
> +inherit kernelsrc kernel-arch
> +
> +do_configure[depends] += "virtual/kernel:do_shared_workdir"
> +do_populate_lic[depends] += "virtual/kernel:do_patch"
> +
> +PROVIDES = "virtual/cpupower"
> +
> +B = "${WORKDIR}/${BPN}-${PV}"
> +
> +EXTRA_OEMAKE = '\
> + -C ${S}/tools/power/cpupower \
> + O=${B} \
> + CROSS=${TARGET_PREFIX} \
> + ARCH=${ARCH} \
> + CC="${CC}" \
> + AR="${AR}" \
> +'
> +do_compile() {
> + unset CFLAGS
> + oe_runmake all
Use 4 spaces for indentation.
> +}
> +
> +do_install() {
> + unset CFLAGS
> + oe_runmake DESTDIR=${D} install
> + chown root:root ${D}/${libdir}/*
> +}
> +
> +python do_package_prepend() {
> + d.setVar('PKGV', d.getVar("KERNEL_VERSION", True).split("-")[0])
> +}
> +
> +PACKAGE_ARCH = "${MACHINE_ARCH}"
> +RDEPENDS_${PN} = "bash"
> --
> 1.9.1
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2016-04-12 9:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 7:28 [PATCH][meta-oe] cpupower: add recipes rongqing.li
2016-03-30 18:13 ` Khem Raj
2016-04-12 9:05 ` Martin Jansa [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=20160412090518.GA2564@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/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