From: Darren Hart <dvhart@linux.intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 1/2] linux-wrs: implement BSP bootstrapping via fallback branches
Date: Fri, 12 Nov 2010 10:55:33 -0800 [thread overview]
Message-ID: <4CDD8DA5.3040106@linux.intel.com> (raw)
In-Reply-To: <260f3ad367b34221104b71380d329e092b6c93c6.1289583673.git.bruce.ashfield@windriver.com>
Hey Bruce,
Dropping yocto list as this is a development discussion (and the webpage
says those take place on poky@yoctoproject.org). Someone correct me if
I've got this wrong.
On 11/12/2010 10:40 AM, Bruce Ashfield wrote:
> When creating a new BSP there isn't always an upstream branch
> to validate SRCREVs against. Therefore, creating a new BSP
> required extra manipulations of the git repository, even though
> the branch for the build would be dynamically created.
>
> To fix this, provide a fallback to the 'standard' branch if
> WRMACHINE is not assigned a specific value for the given MACHINE.
> The fallback saved in KBRANCH, and represents the branch that
It seems that KBRANCH_FALLBACK might be a bit more self-descriptive.
Unless I'm misunderstanding it's purpose...
OK reading the patch, KBRANCH is basically the new variable we store the
kernel branch in, and it is set to standard if WRMACHINE is not set -
KBRANCH itself is not the fallback. Code looks good, commit message was
ambiguous (to me).
> we should build, even if no fallback is required. Some substeps
> of the recipe have been updated to use KBRANCH rather than
> enforcing MACHINE-KERNELTYPE.
>
> Signed-off-by: Bruce Ashfield<bruce.ashfield@windriver.com>
> ---
> meta/recipes-kernel/linux/linux-wrs_git.bb | 40 ++++++++++++++++++++++-----
> 1 files changed, 32 insertions(+), 8 deletions(-)
>
> diff --git a/meta/recipes-kernel/linux/linux-wrs_git.bb b/meta/recipes-kernel/linux/linux-wrs_git.bb
> index 1f2b11e..209648b 100644
> --- a/meta/recipes-kernel/linux/linux-wrs_git.bb
> +++ b/meta/recipes-kernel/linux/linux-wrs_git.bb
> @@ -10,10 +10,10 @@ PV = "2.6.34+git${SRCPV}"
> # To use a staged, on-disk bare clone of a Wind River Kernel, use a
> # variant of the below
> # SRC_URI = "git://///path/to/kernel/default_kernel.git;fullclone=1"
> -SRC_URI = "git://git.pokylinux.org/linux-2.6-windriver.git;protocol=git;fullclone=1;branch=${WRMACHINE}-${LINUX_KERNEL_TYPE};name=machine \
> +SRC_URI = "git://git.pokylinux.org/linux-2.6-windriver.git;protocol=git;fullclone=1;branch=${KBRANCH};name=machine \
> git://git.pokylinux.org/linux-2.6-windriver.git;protocol=git;noclone=1;branch=wrs_meta;name=meta"
>
> -WRMACHINE = "${MACHINE}"
> +WRMACHINE = "UNDEFINED"
Not a critique, just a question - why "UNDEFINED" instead of just not set?
--
Darren Hart
Yocto Linux Kernel
next prev parent reply other threads:[~2010-11-12 18:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 18:40 [PATCH 0/2] linux-wrs: improve BSP-bootstrap process Bruce Ashfield
2010-11-12 18:40 ` [PATCH 1/2] linux-wrs: implement BSP bootstrapping via fallback branches Bruce Ashfield
2010-11-12 18:55 ` Darren Hart [this message]
2010-11-12 19:01 ` Bruce Ashfield
2010-11-12 18:40 ` [PATCH 2/2] linux-wrs: BSP bootstrap Bruce Ashfield
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=4CDD8DA5.3040106@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=bruce.ashfield@windriver.com \
--cc=poky@yoctoproject.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 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.