From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] msr-tools: add recipe
Date: Sun, 18 Jan 2015 10:35:43 +0100 [thread overview]
Message-ID: <m9fupf$ln2$1@ger.gmane.org> (raw)
In-Reply-To: <1421446794-11403-1-git-send-email-ben.shelton@ni.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ben Shelton schreef op 16-01-15 om 23:19:
> msr-tools provides the rdmsr and wrmsr tools to read and write Intel
> model-specific registers on the x86 and x64 architectures.
>
> Signed-off-by: Ben Shelton <ben.shelton@ni.com> ---
> meta-oe/recipes-devtools/msr-tools/msr-tools_1.3.bb | 21
> +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644
> meta-oe/recipes-devtools/msr-tools/msr-tools_1.3.bb
>
> diff --git a/meta-oe/recipes-devtools/msr-tools/msr-tools_1.3.bb
> b/meta-oe/recipes-devtools/msr-tools/msr-tools_1.3.bb new file mode
> 100644 index 0000000..5544920 --- /dev/null +++
> b/meta-oe/recipes-devtools/msr-tools/msr-tools_1.3.bb @@ -0,0 +1,21 @@
> +SUMMARY = "utilies to read and write Intel model-specific registers"
> +HOMEPAGE = "https://01.org/msr-tools" +LICENSE = "GPLv2"
> +LIC_FILES_CHKSUM =
> "file://Makefile;beginline=1;endline=11;md5=678a3928c856042424c734f4a7586e65"
>
>
+SECTION = "devel"
> + +SRC_URI =
> "https://01.org/sites/default/files/downloads/msr-tools/msr-tools-${PV}.zip"
>
>
+SRC_URI[md5sum] = "67d18527f64fd707c9b7a79f13d19fd5"
> +SRC_URI[sha256sum] =
> "f9457b5340f5f274da4239a461f0db6b514142b40461559d9c6150f05aab1d1e" + +S =
> "${WORKDIR}/msr-tools-master" + +COMPATIBLE_HOST =
> '(i.86|x86_64).*-linux' + +do_install() { + install -d ${D}/${bindir}
> + install rdmsr ${D}/${bindir}/ + install wrmsr ${D}/${bindir}/
${bindir} already includes the slash, please change the above to
${D}${bindir} and use -m0755 to get the proper permissions. And since this
writes to registers ${sbindir} might be a better place for it.
> +} + +FILES_${PN} += "${bindir}/*"
${bindir} is in FILES by default, please drop this assignment.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org
iD8DBQFUu35vMkyGM64RGpERAtLCAJ94f2vQN8QJHU0V6bhn4+LaIZLR4ACbBLxv
j0iHOMvXRl6w5z1AjSVg3L0=
=V22G
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2015-01-18 9:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 22:19 [meta-oe][PATCH] msr-tools: add recipe Ben Shelton
2015-01-18 9:35 ` Koen Kooi [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='m9fupf$ln2$1@ger.gmane.org' \
--to=koen@dominion.thruhere.net \
--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