From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Armin Kuster <akuster808@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [[PATCH] qemuppc64: add machine
Date: Tue, 09 Sep 2014 09:05:27 +0100 [thread overview]
Message-ID: <1410249927.19272.42.camel@ted> (raw)
In-Reply-To: <1410227590-14190-2-git-send-email-akuster808@gmail.com>
On Mon, 2014-09-08 at 18:53 -0700, Armin Kuster wrote:
> override USER_CLASSES as prelink does not currently
> work on ppc64
> ---
> meta/conf/machine/qemuppc64.conf | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
> create mode 100644 meta/conf/machine/qemuppc64.conf
>
> diff --git a/meta/conf/machine/qemuppc64.conf b/meta/conf/machine/qemuppc64.conf
> new file mode 100644
> index 0000000..86916e5
> --- /dev/null
> +++ b/meta/conf/machine/qemuppc64.conf
> @@ -0,0 +1,16 @@
> +#@TYPE: Machine
> +#@NAME: qemu PPC 64 Emulator setup
> +#@DESCRIPTION: Machine configuration for running an PPC system under qemu emulation
> +
> +require conf/machine/include/qemu.inc
> +DEFAULTTUNE ?= "ppc64p6"
> +require conf/machine/include/tune-power6.inc
> +
> +#prelink broken
> +USER_CLASSES = "buildstats image-mklibs "
This is horrible. Can we somehow blacklist qemuppc64 in the prelink
class itself?
USER_CLASSES_remove = "prelink"
would be better than overriding the users choice like above...
Cheers,
Richard
> +KERNEL_IMAGETYPE = "vmlinux"
> +
> +IMAGE_FSTYPES = "ext2 ext3"
> +
> +SERIAL_CONSOLE ?= "ttyS0"
> --
> 1.9.1
>
next prev parent reply other threads:[~2014-09-09 8:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 1:53 [PATCH] Adding new qemuppc64 machine config Armin Kuster
2014-09-09 1:53 ` [[PATCH] qemuppc64: add machine Armin Kuster
2014-09-09 8:05 ` Richard Purdie [this message]
2014-09-09 14:46 ` Mark Hatle
2014-09-09 15:13 ` akuster808
2014-09-09 15:03 ` akuster808
2014-09-11 2:41 ` akuster808
2014-09-09 5:03 ` [PATCH] Adding new qemuppc64 machine config akuster808
2014-09-09 15:02 ` Richard Purdie
2014-09-09 23:12 ` akuster808
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=1410249927.19272.42.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=akuster808@gmail.com \
--cc=openembedded-core@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