All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: rpurdie@linux.intel.com
Cc: yocto@yoctoproject.org
Subject: Re: [PATCH 1/3] yocto-kernel: factor common routes, update to 2.6.37 and branch renaming
Date: Wed, 08 Dec 2010 15:49:27 -0500	[thread overview]
Message-ID: <4CFFEF57.800@windriver.com> (raw)
In-Reply-To: <64f083b7e51bae434b4ae449edc81795e89f9f1c.1291786378.git.bruce.ashfield@windriver.com>

On 10-12-08 09:35 AM, Bruce Ashfield wrote:
> In order to extend and create more kernel recipes based on the
> supported yocto kernel common routines need to be placed in
> re-usable blocks.
>
> To accomplish this meta/recipes-kernel/linux/linux-yocto_git.bb
> is broken into three parts:
>

<snip>

>   }
>
> -COMPATIBLE_MACHINE = "(qemuarm|qemux86|qemuppc|qemumips|qemux86-64|atom-pc|routerstationpro|mpc8315e-rdb|beagleboard)"
> -
> -LINUX_VERSION = "v2.6.34"
> -LINUX_VERSION_EXTENSION = "-wr-${LINUX_KERNEL_TYPE}"
> -PR = "r13"
> +SRC_URI = "git://git.pokylinux.org/linux-yocto-2.6.37;protocol=git;fullclone=1;branch=${KBRANCH};name=machine \


Richard,

This URI is only accessible via ssh, but the contents of the kernel
are definitely there. What do we need to change to make this
beastie public ? This is what is causing part of my SRCREV issues.

Cheers,

Bruce


> +           git://git.pokylinux.org/linux-yocto-2.6.37;protocol=git;noclone=1;branch=meta;name=meta"
>
> -S = "${WORKDIR}/linux"
> -B = "${WORKDIR}/linux-${KMACHINE}-${LINUX_KERNEL_TYPE}-build"


  parent reply	other threads:[~2010-12-08 20:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08 14:35 [PATCH 0/3] linux-yocto: refactor recipes and update the kernel Bruce Ashfield
2010-12-08 14:35 ` [PATCH 1/3] yocto-kernel: factor common routes, update to 2.6.37 and branch renaming Bruce Ashfield
2010-12-08 20:20   ` Bruce Ashfield
2010-12-08 21:17     ` Bruce Ashfield
2010-12-09  1:31     ` Darren Hart
2010-12-08 20:49   ` Bruce Ashfield [this message]
2010-12-09 20:49   ` Darren Hart
2010-12-09 20:53     ` Bruce Ashfield
2010-12-10  1:33     ` Bruce Ashfield
2010-12-08 14:35 ` [PATCH 2/3] linux-libc-headers-yocto: use common linux-yocto routines Bruce Ashfield
2010-12-08 14:35 ` [PATCH 3/3] qemu: update arm timer handling Bruce Ashfield
2010-12-08 19:05 ` [PATCH 0/3] linux-yocto: refactor recipes and update the kernel Bruce Ashfield
2010-12-09 15:56 ` Bruce Ashfield
2010-12-09 18:34   ` Elizabeth Flanagan
  -- strict thread matches above, loose matches on Subject: below --
2010-12-10 16:02 Bruce Ashfield
2010-12-10 16:02 ` [PATCH 1/3] yocto-kernel: factor common routes, update to 2.6.37 and branch renaming 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=4CFFEF57.800@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=rpurdie@linux.intel.com \
    --cc=yocto@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.