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 0/3] linux-yocto: refactor recipes and update the	kernel
Date: Thu, 09 Dec 2010 10:56:37 -0500	[thread overview]
Message-ID: <4D00FC35.8050101@windriver.com> (raw)
In-Reply-To: <cover.1291786378.git.bruce.ashfield@windriver.com>

On 10-12-08 09:35 AM, Bruce Ashfield wrote:
> Richard,
>
> Consider these patches for merging. I've been building and working
> with these for 2 weeks now, and while they aren't perfect, they
> work and we need more eyes on 2.6.37.

Does anyone with the right admin privs have time to look
into this ?

 >  git clone git://git.pokylinux.org/linux-yocto-2.6.37
fatal: destination path 'linux-yocto-2.6.37' already exists and is not 
an empty directory.
yow-bashfiel-d2 [/tmp]> rm -rf linux-yocto-2.6.37/
yow-bashfiel-d2 [/tmp]> git clone git://git.pokylinux.org/linux-yocto-2.6.37
Initialized empty Git repository in /tmp/linux-yocto-2.6.37/.git/
fatal: The remote end hung up unexpectedly
yow-bashfiel-d2 [/tmp]> git clone 
git://git.pokylinux.org/linux-2.6-windriver
Initialized empty Git repository in /tmp/linux-2.6-windriver/.git/
^Cmote: Counting objects: 125026

------

In other words, the 2.6.37 repo is only reachable by a ssh
based clone :)

When I get that working, I can fixup the SRCREV issue and
resubmit this for merge.

Cheers,

Bruce

>
> What we get is the following:
>
>   - factoring of the code into some reusable routines in the form
>     of a linux-yocto bbclass. The -stable, -devel and libc headers
>     recipes are all using this common code
>
>   - A new branching scheme for the 2.6.37 kernel that generalizes
>     the branch names and shows their hierarchy. The tools that
>     process the kernel needed a lot of 'unlearning' about the
>     old structure (this took a lot of my time working on this).
>
>     If this needs to be tweaked more, we can do it later, since
>     the big changes are done and agreed on, and we can't delay
>     scaling this out to more boards much longer.
>
>   - A -stable recipe that continues to build the 2.6.34 kernel
>     and a move of the main recipe to track the development
>     2.6.37-rc5 tree. The qemu* targets have their defaults
>     changed to 2.6.37-rc, while the hardware targets remain
>     on 2.6.34 for a bit longer. To ease the switch over, I
>     put the SRCREVs for 2.6.37 into the recipe itself. We
>     can move these as .37 becomes the default.
>
>   - perf is moved into a linux-tools.inc, we can add more to
>     this and re-use it more easily from here
>
>   - BSP boostrapping is streamlined (docs to follow).
>
> The temporary commenting of the preferred libc-headers provider
> was intentional. There is something strange happening when
> headers are generated for 2.6.34 that was breaking libc builds.
> To avoid holding up this series, we'll go with the default
> libc headers for a short while.
>
> I've built and booted all the qemu* targets on 2.6.37
> (minimal and sato), I've built most of the hardware
> targets. I noticed some strangeness with the mouse on
> ARM, and that will need to be looked at further. I've done
> some audits on the kernel configuration in 2.6.37, and
> while it looks sane, full BSP testing will tell us if
> anything major changed (that I missed).
>
> If there are better suggestions on how we can stage and
> get mileage on this code, I'm all ears, but this is a kernel
> uprev, so I expect some issues (there always is even though
> I've done plenty of these). If we don't want anything
> destabilizing in the tree, I'm fine with this and we just
> need to come up with a plan.
>
> What remains (I'm only one person!):
>
>   - BSP porting and full BSP testing
>   - Investigation into the libc-headers issue
>   - Continued cleanup
>   - Feature merging into 2.6.37 (lttng, yaffs, etc)
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
>    Branch: zedd/kernel
>    Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Thanks,
>      Bruce Ashfield<bruce.ashfield@windriver.com>
> ---
>
>
> Bruce Ashfield (3):
>    yocto-kernel: factor common routes, update to 2.6.37 and branch
>      renaming
>    linux-libc-headers-yocto: use common linux-yocto routines
>    qemu: update arm timer handling
>
>   meta-emenlow/conf/machine/emenlow.conf             |    3 +-
>   meta/classes/kernel-yocto.bbclass                  |  202 +++++++++++++++++
>   .../conf/distro/include/poky-default-revisions.inc |    2 +-
>   meta/conf/machine/atom-pc.conf                     |    3 +-
>   meta/conf/machine/beagleboard.conf                 |    3 +-
>   meta/conf/machine/include/qemu.inc                 |    1 +
>   meta/conf/machine/mpc8315e-rdb.conf                |    3 +-
>   meta/conf/machine/routerstationpro.conf            |    3 +-
>   .../qemu-0.12.4/arm_timer-fix-oneshot-mode.patch   |   32 +++
>   .../arm_timer-reload-timer-when-enabled.patch      |   40 ++++
>   meta/recipes-devtools/qemu/qemu_0.12.4.bb          |    4 +-
>   .../linux-libc-headers-yocto_git.bb                |   25 +--
>   meta/recipes-kernel/linux/linux-tools.inc          |   19 ++
>   .../recipes-kernel/linux/linux-yocto-stable_git.bb |   41 ++++
>   meta/recipes-kernel/linux/linux-yocto.inc          |   23 ++
>   meta/recipes-kernel/linux/linux-yocto_git.bb       |  232 +++-----------------
>   16 files changed, 415 insertions(+), 221 deletions(-)
>   create mode 100644 meta/classes/kernel-yocto.bbclass
>   create mode 100644 meta/recipes-devtools/qemu/qemu-0.12.4/arm_timer-fix-oneshot-mode.patch
>   create mode 100644 meta/recipes-devtools/qemu/qemu-0.12.4/arm_timer-reload-timer-when-enabled.patch
>   create mode 100644 meta/recipes-kernel/linux/linux-tools.inc
>   create mode 100644 meta/recipes-kernel/linux/linux-yocto-stable_git.bb
>   create mode 100644 meta/recipes-kernel/linux/linux-yocto.inc
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



  parent reply	other threads:[~2010-12-09 15:56 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
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 [this message]
2010-12-09 18:34   ` Elizabeth Flanagan
  -- strict thread matches above, loose matches on Subject: below --
2010-12-10 16:02 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=4D00FC35.8050101@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.