From: tom.zanussi@linux.intel.com
To: poky@yoctoproject.org
Cc: Tom Zanussi <tom.zanussi@linux.intel.com>
Subject: [PATCH 0/8] yocto-bsp 3.8-rt support and related fixes
Date: Thu, 4 Apr 2013 17:09:20 -0500 [thread overview]
Message-ID: <cover.1365112661.git.tom.zanussi@linux.intel.com> (raw)
From: Tom Zanussi <tom.zanussi@linux.intel.com>
This adds 3.8-rt support to yocto-bsp along with other assorted fixes
that it exposed in a cascading way; basically when testing BSPs with
3.8-rt, the problem described in YOCTO #4145 showed up, which I tracked
down to a missing close() in the script, but once that was fixed, it
showed a problem in the kernel tools when checking out an existing
branch, and once that was fixed, it showed a problem that was tracked
down to a problem that was fixed in the -rt2 patchset, both of which
were subsequently pulled into the oe-core and kernel repos.
But I didn't stop there, and the rest of the patches here deal with
smaller changes mainly due to the need to reflect changes in the main
metadata and kernel repos.
The following changes since commit 5444db05034e5e693846ccb5543732e790b1d4c7:
ref-manual: Added preliminary migration raw text. (2013-04-04 14:13:46 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib.git tzanussi/yocto-bsp-3.8-rt-and-fixes
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=tzanussi/yocto-bsp-3.8-rt-and-fixes
Tom Zanussi (8):
yocto-bsp: add KBRANCH for existing kbranch cases
yocto-bsp: add linux-yocto-3.8-rt to templates
yocto-bsp: have replace_file() close file before copying
yocto-bsp: pass in file object to replace_file()
yocto-bsp: use specific bsp metadata for qemu machines
yocto-bsp: qemu machine template updates
yocto-bsp: set SRCREV for arm-based qemu machines
yocto-bsp: change qemu-based mips BSP default branch
scripts/lib/bsp/engine.py | 3 +-
...linux-yocto-dev\": }} linux-yocto-dev.bbappend" | 3 ++
...yocto-rt_3.4\": }} linux-yocto-rt_3.4.bbappend" | 3 ++
...yocto-rt_3.8\": }} linux-yocto-rt_3.8.bbappend" | 32 +++++++++++++
...o-tiny_3.4\": }} linux-yocto-tiny_3.4.bbappend" | 3 ++
...linux-yocto_3.4\": }} linux-yocto_3.4.bbappend" | 3 ++
...linux-yocto_3.8\": }} linux-yocto_3.8.bbappend" | 3 ++
.../defconfig" | 2 +-
...linux-yocto-dev\": }} linux-yocto-dev.bbappend" | 3 ++
...yocto-rt_3.4\": }} linux-yocto-rt_3.4.bbappend" | 3 ++
...yocto-rt_3.8\": }} linux-yocto-rt_3.8.bbappend" | 32 +++++++++++++
...o-tiny_3.4\": }} linux-yocto-tiny_3.4.bbappend" | 3 ++
...linux-yocto_3.4\": }} linux-yocto_3.4.bbappend" | 3 ++
...linux-yocto_3.8\": }} linux-yocto_3.8.bbappend" | 3 ++
...linux-yocto-dev\": }} linux-yocto-dev.bbappend" | 3 ++
...yocto-rt_3.4\": }} linux-yocto-rt_3.4.bbappend" | 3 ++
...yocto-rt_3.8\": }} linux-yocto-rt_3.8.bbappend" | 32 +++++++++++++
...o-tiny_3.4\": }} linux-yocto-tiny_3.4.bbappend" | 3 ++
...linux-yocto_3.4\": }} linux-yocto_3.4.bbappend" | 3 ++
...linux-yocto_3.8\": }} linux-yocto_3.8.bbappend" | 3 ++
...linux-yocto-dev\": }} linux-yocto-dev.bbappend" | 3 ++
...yocto-rt_3.4\": }} linux-yocto-rt_3.4.bbappend" | 3 ++
...yocto-rt_3.8\": }} linux-yocto-rt_3.8.bbappend" | 32 +++++++++++++
...o-tiny_3.4\": }} linux-yocto-tiny_3.4.bbappend" | 3 ++
...linux-yocto_3.4\": }} linux-yocto_3.4.bbappend" | 3 ++
...linux-yocto_3.8\": }} linux-yocto_3.8.bbappend" | 3 ++
.../arch/qemu/conf/machine/{{=machine}}.conf | 8 ++--
.../{{=machine}}-standard.scc" | 7 +++
...linux-yocto-dev\": }} linux-yocto-dev.bbappend" | 5 +-
...yocto-rt_3.4\": }} linux-yocto-rt_3.4.bbappend" | 3 ++
...yocto-rt_3.8\": }} linux-yocto-rt_3.8.bbappend" | 55 ++++++++++++++++++++++
...o-tiny_3.4\": }} linux-yocto-tiny_3.4.bbappend" | 3 ++
...linux-yocto_3.4\": }} linux-yocto_3.4.bbappend" | 5 +-
...linux-yocto_3.8\": }} linux-yocto_3.8.bbappend" | 8 +++-
...linux-yocto-dev\": }} linux-yocto-dev.bbappend" | 3 ++
...yocto-rt_3.4\": }} linux-yocto-rt_3.4.bbappend" | 3 ++
...yocto-rt_3.8\": }} linux-yocto-rt_3.8.bbappend" | 32 +++++++++++++
...o-tiny_3.4\": }} linux-yocto-tiny_3.4.bbappend" | 3 ++
...linux-yocto_3.4\": }} linux-yocto_3.4.bbappend" | 3 ++
...linux-yocto_3.8\": }} linux-yocto_3.8.bbappend" | 3 ++
40 files changed, 324 insertions(+), 10 deletions(-)
create mode 100644 "scripts/lib/bsp/substrate/target/arch/arm/recipes-kernel/linux/{{ if kernel_choice == \"linux-yocto-rt_3.8\": }} linux-yocto-rt_3.8.bbappend"
create mode 100644 "scripts/lib/bsp/substrate/target/arch/i386/recipes-kernel/linux/{{ if kernel_choice == \"linux-yocto-rt_3.8\": }} linux-yocto-rt_3.8.bbappend"
create mode 100644 "scripts/lib/bsp/substrate/target/arch/mips/recipes-kernel/linux/{{ if kernel_choice == \"linux-yocto-rt_3.8\": }} linux-yocto-rt_3.8.bbappend"
create mode 100644 "scripts/lib/bsp/substrate/target/arch/powerpc/recipes-kernel/linux/{{ if kernel_choice == \"linux-yocto-rt_3.8\": }} linux-yocto-rt_3.8.bbappend"
create mode 100644 "scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/{{ if kernel_choice == \"linux-yocto-rt_3.8\": }} linux-yocto-rt_3.8.bbappend"
create mode 100644 "scripts/lib/bsp/substrate/target/arch/x86_64/recipes-kernel/linux/{{ if kernel_choice == \"linux-yocto-rt_3.8\": }} linux-yocto-rt_3.8.bbappend"
--
1.7.11.4
next reply other threads:[~2013-04-04 22:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 22:09 tom.zanussi [this message]
2013-04-04 22:09 ` [PATCH 1/8] yocto-bsp: add KBRANCH for existing kbranch cases tom.zanussi
2013-04-04 22:09 ` [PATCH 2/8] yocto-bsp: add linux-yocto-3.8-rt to templates tom.zanussi
2013-04-04 22:09 ` [PATCH 3/8] yocto-bsp: have replace_file() close file before copying tom.zanussi
2013-04-04 22:09 ` [PATCH 4/8] yocto-bsp: pass in file object to replace_file() tom.zanussi
2013-04-04 22:09 ` [PATCH 5/8] yocto-bsp: use specific bsp metadata for qemu machines tom.zanussi
2013-04-04 22:09 ` [PATCH 6/8] yocto-bsp: qemu machine template updates tom.zanussi
2013-04-04 22:09 ` [PATCH 7/8] yocto-bsp: set SRCREV for arm-based qemu machines tom.zanussi
2013-04-04 22:09 ` [PATCH 8/8] yocto-bsp: change qemu-based mips BSP default branch tom.zanussi
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=cover.1365112661.git.tom.zanussi@linux.intel.com \
--to=tom.zanussi@linux.intel.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.