Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 04/10] meta-rt: add linux-yocto-rt_3.0 recipe
Date: Thu, 11 Aug 2011 20:40:15 -0400	[thread overview]
Message-ID: <4E44766F.6090201@windriver.com> (raw)
In-Reply-To: <21924dcdc775dde5b7144cf26367663dbc0cfaeb.1313092152.git.dvhart@linux.intel.com>

On 11-08-11 7:08 PM, Darren Hart wrote:
> Add the initial linux-yocto-rt_3.0 recipe.
>
> TODO: replace the AUTOREV with real commit ids.

I think you did this!

>
> Signed-off-by: Darren Hart<dvhart@linux.intel.com>
> Signed-off-by: Bruce Ashfield<bruce.ashfield@windriver.com>
> ---
>   meta-rt/recipes-kernel/linux/linux-yocto-rt_3.0.bb |   55 ++++++++++++++++++++
>   1 files changed, 55 insertions(+), 0 deletions(-)
>   create mode 100644 meta-rt/recipes-kernel/linux/linux-yocto-rt_3.0.bb
>
> diff --git a/meta-rt/recipes-kernel/linux/linux-yocto-rt_3.0.bb b/meta-rt/recipes-kernel/linux/linux-yocto-rt_3.0.bb
> new file mode 100644
> index 0000000..7eaeb0f
> --- /dev/null
> +++ b/meta-rt/recipes-kernel/linux/linux-yocto-rt_3.0.bb
> @@ -0,0 +1,55 @@
> +inherit kernel
> +require recipes-kernel/linux/linux-yocto.inc
> +
> +KMACHINE = "yocto/standard/preempt-rt/base"

I just noticed this on the way through, this could likely just
be set to "common-pc", all it really is supposed to be
is a fallback if a machine specific override doesn't work.

(I see that you actually do this in patch 8/10 for 2.6.34 anyway).

> +KMACHINE_qemux86  = "common-pc"
> +KMACHINE_qemux86-64  = "common-pc-64"
> +KMACHINE_qemuarm  = "arm-versatile-926ejs"
> +# qemuppc hangs at boot
> +#KMACHINE_qemuppc  = "qemu-ppc32"
> +# qemumips panics at boot
> +#KMACHINE_qemumips = "mti-malta32-be"
> +
> +KBRANCH = ${KMACHINE}

And instead of the above, you could just say:

KBRANCH = "yocto/standard/preempt-rt/base"

to have a fallback in place that keeps the fetcher chugging along.
That's all that the KMACHINE default was doing in the end anyway.

Sorry I didn't see this earlier, but seeing it in front of me
here, it jumped out.

The rest looks good.

Bruce

> +KBRANCH_qemux86 = "yocto/standard/preempt-rt/base"
> +KBRANCH_qemux86-64 = "yocto/standard/preempt-rt/base"
> +KBRANCH_qemuarm  = "yocto/standard/preempt-rt/base"
> +#KBRANCH_qemuppc  = "yocto/standard/preempt-rt/base"
> +#KBRANCH_qemumips = "yocto/standard/preempt-rt/base"
> +KMETA = meta
> +
> +LINUX_VERSION ?= "3.0"
> +LINUX_KERNEL_TYPE = "preempt-rt"
> +LINUX_VERSION_EXTENSION ?= "-yocto-${LINUX_KERNEL_TYPE}"
> +
> +SRCREV_machine_qemux86 = "7e1e5b6c8a13c615feb0d7b6d37988a094aae98f"
> +SRCREV_machine_qemux86-64 = "7e1e5b6c8a13c615feb0d7b6d37988a094aae98f"
> +SRCREV_machine_qemuarm = "7e1e5b6c8a13c615feb0d7b6d37988a094aae98f"
> +#SRCREV_machine_qemuppc = "7e1e5b6c8a13c615feb0d7b6d37988a094aae98f"
> +#SRCREV_machine_qemumips = "7e1e5b6c8a13c615feb0d7b6d37988a094aae98f"
> +SRCREV_machine = "7e1e5b6c8a13c615feb0d7b6d37988a094aae98f"
> +SRCREV_meta = "7782fc673afd6a1c742409896ae787560d96fce8"
> +
> +PR = "r0"
> +PV = "${LINUX_VERSION}+git${SRCPV}"
> +SRCREV_FORMAT = "meta_machine"
> +
> +SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.0.git;protocol=git;nocheckout=1;branch=${KBRANCH},meta;name=machine,meta"
> +
> +COMPATIBLE_MACHINE = "(qemux86|qemux86-64|qemuarm)"
> +
> +# Functionality flags
> +KERNEL_REVISION_CHECKING ?= "t"
> +KERNEL_FEATURES=features/netfilter
> +KERNEL_FEATURES_append=" features/taskstats"
> +KERNEL_FEATURES_append_qemux86=" cfg/sound"
> +KERNEL_FEATURES_append_qemux86-64=" cfg/sound"
> +
> +YOCTO_KERNEL_META_DATA=t
> +
> +# extra tasks
> +addtask kernel_link_vmlinux after do_compile before do_install
> +addtask validate_branches before do_patch after do_kernel_checkout
> +addtask kernel_configcheck after do_configure before do_compile
> +
> +require recipes-kernel/linux/linux-tools.inc




  reply	other threads:[~2011-08-12  0:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11 23:08 [PATCH 00/10] Refresh meta-rt and move the recipes under meta Darren Hart
2011-08-11 23:08 ` [PATCH 01/10] meta-rt: refresh linux-yocto-rt recipe Darren Hart
2011-08-11 23:08 ` [PATCH 02/10] meta-rt: rt-tests v0.73 instead of AUTOREV Darren Hart
2011-08-11 23:08 ` [PATCH 03/10] meta-rt: canonicalize directory structure Darren Hart
2011-08-11 23:08 ` [PATCH 04/10] meta-rt: add linux-yocto-rt_3.0 recipe Darren Hart
2011-08-12  0:40   ` Bruce Ashfield [this message]
2011-08-12  2:56     ` Darren Hart
2011-08-12  3:23     ` Darren Hart
2011-08-12 13:36       ` Bruce Ashfield
2011-08-11 23:08 ` [PATCH 05/10] meta-rt: remove atom-pc support from the main layer Darren Hart
2011-08-11 23:08 ` [PATCH 06/10] meta-rt: rename minimal-rt images to -rt, drop live image Darren Hart
2011-08-11 23:08 ` [PATCH 07/10] meta-rt: add an -rt-sdk image Darren Hart
2011-08-11 23:08 ` [PATCH 08/10] meta-rt: default KMACHINE and SRCREV_machine to avoid parsing errors Darren Hart
2011-08-11 23:08 ` [PATCH 09/10] Move meta-rt recipes to oe-core (meta) Darren Hart
2011-08-11 23:08 ` [PATCH 10/10] recipes-rt: add a README documenting the contents of recipes-rt Darren Hart
2011-08-12 17:55 ` [PATCH 00/10] Refresh meta-rt and move the recipes under meta Saul Wold

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=4E44766F.6090201@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=dvhart@linux.intel.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