* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2013-08-23 18:08 Bruce Ashfield
2013-08-23 18:08 ` [PATCH 1/5] kern-tools: usability, bug fixes and no guilt Bruce Ashfield
` (6 more replies)
0 siblings, 7 replies; 61+ messages in thread
From: Bruce Ashfield @ 2013-08-23 18:08 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
Richard/Saul,
Here's my consolidated set of changes that represent the biggest chunk
of work for the Yocto 1.5 release. The obvious change is that the 3.10
kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
mark on). I've built and booted core-image-sato for all the oe-core
qemu machines.
3.10 also the latest LTSI and will be updated with that content when it
becomes available.
Other features of the 3.10 kernel include:
- refreshed -rt support
- refreshed yaffs2, aufs3
- cryptodev
- bfs, edf, and OCF staged features
- scrubbed and updated meta data for v3.10
- improved tools support for meta data updates and queue maintenance
- patch carry forward from all previous linux-yocto kernels and
configuration.
I've also tested linux-yocto-rt and linux-yocto-tiny for the new, shiny tree.
I've also bumped the linux-libc-headers to 3.10 and have fixed gst-plugins-good
to adapt to a changed #define in the exported headers.
Other parts of this update include an uprev of guilt, and in fact, a
restoration of "normal" guil operations, since the kernel tree is now
manipulated and maintained via a smaller, more contained script. This
was necessary for both usability reasons and the fact that all of guilts
protections were being removed for the kernel's use .. which makes you
ask the quesetion "why use it". It was time for a change.
The patches are pretty self explanitory and all contain detailed long
logs .. but the summary is:
[PATCH 1/5] kern-tools: usability, bug fixes and no guilt
[PATCH 2/5] guilt: update to latest git version
[PATCH 3/5] linux-libc-headers: update to v3.10
[PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
[PATCH 5/5] linux-yocto: introduce v3.10
** There is one pending activity. As part of thsi update to 3.10, we want
to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
routerstationpro BSP is still using it as its preferred version. I'm
a one man show on this update, and I wasn't able to get the 100+ patches
ported to 3.10 AND get this update out before the M4 cutoff.
** I'm still attempting to udpate all the reference boards, and
once done, I'll send a follow up patch.
** Please test, I've done my best, but things can slip through. We'll
work issues in the stabilization period.
Cheers,
Bruce
The following changes since commit 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
kern-tools: usability, bug fixes and no guilt
guilt: update to latest git version
linux-libc-headers: update to v3.10
gst-plugins-good: fix 3.10 libc-headers build failure
linux-yocto: introduce v3.10
meta/classes/kernel-yocto.bbclass | 2 +
meta/conf/distro/include/tcmode-default.inc | 2 +-
.../guilt/files/guilt-import-commit.patch | 96 ------
meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
.../guilt/files/guilt-push-no-series.patch | 29 --
meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
.../guilt/files/guilt-set-git_exec_path.patch | 29 --
...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
meta/recipes-devtools/guilt/files/guilt.patch | 319 --------------------
.../guilt/files/improve_auto_header_gen.patch | 71 -----
.../files/make_git_commands_conditional.patch | 48 ---
.../guilt/files/optional_head_check.patch | 60 ----
.../guilt/files/uninstall_force.patch | 14 -
.../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
.../kern-tools/kern-tools-native_git.bb | 6 +-
.../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
.../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
.../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
23 files changed, 150 insertions(+), 861 deletions(-)
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-import-commit.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-init.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
delete mode 100644 meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
delete mode 100644 meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
delete mode 100644 meta/recipes-devtools/guilt/files/optional_head_check.patch
delete mode 100644 meta/recipes-devtools/guilt/files/uninstall_force.patch
rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb => guilt-native_git.bb} (45%)
create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
delete mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
create mode 100644 meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
--
1.7.10.4
^ permalink raw reply [flat|nested] 61+ messages in thread
* [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
2013-08-23 18:08 [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
@ 2013-08-23 18:08 ` Bruce Ashfield
2013-08-23 18:08 ` [PATCH 2/5] guilt: update to latest git version Bruce Ashfield
` (5 subsequent siblings)
6 siblings, 0 replies; 61+ messages in thread
From: Bruce Ashfield @ 2013-08-23 18:08 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
Updating the kern-tools SRCREV to pick up the following fixes:
60a894e kgit-s2q: add proper commit ID handling for mixed am/apply usage
3b08257 kgit-s2q: delete pruning of path support.
c5868b4 kgit-s2q: Restore implicit exit status to "git apply" section
1bd00b9 kgit-scc: mask warnings from cleanup phase 5
bb75299 kgit-s2q: fix commit warp when running "git am --abort"
ef9571b kgit-scc: cleanup git rebase-apply dir
fdb7d21 kgit-scc: ensure treegen stops if a meta series fails
008987b config: add kconfig cleaning options
69ff569 kgit-s2q: strip blank lines and comments
e7b4540 kgit-init: disable garbage collection on a new tree
417eaed kgit-s2q: delete old LTSI patch dir finding code
21f2200 kgit-scc: better error checking on resume
ad5084c kern-tools: use .meta as meta data container
1deb5d8 kgit-meta: don't push patches without a series file
eb431a1 kgit-s2q: aid patch reject resolution via helper scripts
f859c40 kgit-s2q: only use patch annotations when explicitly asked
333ae18 kgit: speed patch application by batching patches
bf6991d kgit: teach tools about non-default meta dirs
bcfc712 kgit-s2q: usability improvements
cb28803 kgit-s2q: fix patch prefix stripping.
37f40e1 kgit-s2q: warn/exit with error if patch not in series
f4704d2 kgit-s2q: consistent rm usage
e11819c kgit-s2q: standardize on use of git mailinfo
36a5eda kgit: remove guilt dependency
c461a4f spp/scc: export mark commands to meta-series
5311162 updateme: ensure that generated features are only used once
4f7a263 kgit-checkpoint: clear .gitignore for meta branch
21ee6f2 updateme: enforce a matching machine
b08749d kgit-scc: remove -meta files after consruction
These are bug fixes, usability changes as well as the removal of the
guilt dependency. During the uprev of the guilt package, the amount of
circumvention of the typical guilt workflow and checks meant that using
it as a series -> branch manager was no longer appropriate. As a result
a new tools kgit-s2q (series 2 queue) was created based on git-quiltimport,
git am, and the LTSI tree generation scripts.
The result is better series to branch validation, faster application and
a simpler management model. This tool is backwards compatible with any
tree previously constructed with guilt. We are now "guilt free"
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
meta/classes/kernel-yocto.bbclass | 2 ++
meta/recipes-kernel/kern-tools/kern-tools-native_git.bb | 6 +++---
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass
index d513ad2..fcc00e3 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -262,6 +262,8 @@ python do_kernel_configcheck() {
# set the default to 'meta'. Otherwise, kconf_check is not passed a valid
# meta-series for processing
kmeta = d.getVar( "KMETA", True ) or "meta"
+ if not os.path.exists(kmeta):
+ kmeta = "." + kmeta
pathprefix = "export PATH=%s:%s; " % (d.getVar('PATH', True), "${S}/scripts/util/")
cmd = d.expand("cd ${S}; kconf_check -config- %s/meta-series ${S} ${B}" % kmeta)
diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
index c414fed..f6fca9e 100644
--- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
+++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
@@ -2,11 +2,11 @@ DESCRIPTION = "Scripts and utilities for managing Yocto branched kernels."
LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://git/tools/kgit;beginline=5;endline=9;md5=d8d1d729a70cd5f52972f8884b80743d"
-DEPENDS = "git-native guilt-native"
+DEPENDS = "git-native"
-SRCREV = "fbcdcb8e23c38352b46235598f34d7b345f458f1"
+SRCREV = "60a894e1018ab55f4014fbfb2a56624d26d94504"
PR = "r12"
-PV = "0.1+git${SRCPV}"
+PV = "0.2+git${SRCPV}"
inherit native
--
1.7.10.4
^ permalink raw reply related [flat|nested] 61+ messages in thread
* [PATCH 2/5] guilt: update to latest git version
2013-08-23 18:08 [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
2013-08-23 18:08 ` [PATCH 1/5] kern-tools: usability, bug fixes and no guilt Bruce Ashfield
@ 2013-08-23 18:08 ` Bruce Ashfield
2013-08-23 18:08 ` [PATCH 3/5] linux-libc-headers: update to v3.10 Bruce Ashfield
` (4 subsequent siblings)
6 siblings, 0 replies; 61+ messages in thread
From: Bruce Ashfield @ 2013-08-23 18:08 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
Uprev guilt to the latest guilt version from its upstream repository.
As part of the uprev all of the previous changes required for the
yocto kernel tools to use git to manipulate series files have been
dropped. These changes were specific to circumventing parts of guilt's
internal santiy checking to allow specific Yocto kernel manipluation
of sub-series files.
Since the kernel tools no longer need guilt, we can use an up to date
and nearly pure upstream version of guilt.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
.../guilt/files/guilt-import-commit.patch | 96 ------
meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
.../guilt/files/guilt-push-no-series.patch | 29 --
meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
.../guilt/files/guilt-set-git_exec_path.patch | 29 --
...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
meta/recipes-devtools/guilt/files/guilt.patch | 319 --------------------
| 71 -----
.../files/make_git_commands_conditional.patch | 48 ---
.../guilt/files/optional_head_check.patch | 60 ----
.../guilt/files/uninstall_force.patch | 14 -
.../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
13 files changed, 6 insertions(+), 849 deletions(-)
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-import-commit.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-init.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
delete mode 100644 meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
delete mode 100644 meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
delete mode 100644 meta/recipes-devtools/guilt/files/optional_head_check.patch
delete mode 100644 meta/recipes-devtools/guilt/files/uninstall_force.patch
rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb => guilt-native_git.bb} (45%)
diff --git a/meta/recipes-devtools/guilt/files/guilt-import-commit.patch b/meta/recipes-devtools/guilt/files/guilt-import-commit.patch
deleted file mode 100644
index bd746c5..0000000
--- a/meta/recipes-devtools/guilt/files/guilt-import-commit.patch
+++ /dev/null
@@ -1,96 +0,0 @@
-guilt: import commits via git format-patch
-
-Rather than attempting to process commits directly, it
-is preferable to try dumping the change via git format-patch
-to take advantage of the proper header/subject/from lines that
-are generated.
-
-If patches cannot be exported, fall back to importing
-commits via a more custom method.
-
-Upstream-Status: Inappropriate [oe-specific]
-
-Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
-
----
- guilt-import-commit | 40 +++++++++++++++++++++++++++++-----------
- 1 file changed, 29 insertions(+), 11 deletions(-)
-
---- a/guilt-import-commit
-+++ b/guilt-import-commit
-@@ -20,46 +20,64 @@ fi
- disp "About to begin conversion..." >&2
- disp "Current head: `cat $GIT_DIR/refs/heads/$branch`" >&2
-
-+# try git-format-patch first, if it fails fall back to internal
-+# methods.
-+patches=`git-format-patch -o $GUILT_DIR/$branch $rhash`
-+if [ -z "$patches" ]; then
-+ need_custom_patches="1"
-+fi
-+
- for rev in `git rev-list $rhash`; do
-+ if [ ! -z "$need_custom_patches" ]; then
- s=`git log --pretty=oneline -1 $rev | cut -c 42-`
-
- fname=`echo $s | sed -e "s/&/and/g" -e "s/[ :]/_/g" -e "s,[/\\],-,g" \
-- -e "s/['\\[{}]//g" -e 's/]//g' -e 's/\*/-/g' \
-+ -e "s/['\\()<>[{}]//g" -e 's/]//g' -e 's/\*/-/g' \
- -e 's/\?/-/g' | tr A-Z a-z`
-
-- disp "Converting `echo $rev | cut -c 1-8` as $fname"
-+ disp "Converting `echo $rev | cut -c 1-8` as $fname.patch"
-
- mangle_prefix=1
- fname_base=$fname
-- while [ -f "$GUILT_DIR/$branch/$fname" ]; do
-+ while [ -f "$GUILT_DIR/$branch/$fname.patch" ]; do
- fname="$fname_base-$mangle_prefix"
- mangle_prefix=`expr $mangle_prefix + 1`
-- disp "Patch under that name exists...trying '$fname'"
-+ disp "Patch under that name exists...trying '$fname.patch'"
- done
-
- (
- do_make_header $rev
- echo ""
- git diff --binary $rev^..$rev
-- ) > $GUILT_DIR/$branch/$fname
-+ ) > $GUILT_DIR/$branch/$fname.patch
-
- # FIXME: grab the GIT_AUTHOR_DATE from the commit object and set the
- # timestamp on the patch
-
-- # insert the patch name into the series file
-- series_insert_patch $fname
-+ patches="$patches $fname.patch"
-+ fi
-
-- # Only reset if the commit was on this branch
-- if head_check $rev 2> /dev/null; then
-+ # Only reset if the commit was on this branch
-+ if head_check $rev 2> /dev/null; then
- # BEWARE: "git reset" ahead! Is there a way to verify that
- # we really created a patch? - We don't want to lose any
- # history.
- git reset --hard $rev^ > /dev/null
-- elif [ -z "$warned" ]; then
-+ elif [ -z "$warned" ]; then
- disp "Warning: commit $rev is not the HEAD...preserving commit" >&2
- disp "Warning: (this message is displayed only once)" >&2
- warned=t
-- fi
-+ fi
-+done
-+
-+rpatches=`echo "$patches" | sed 's% %\n%g' | tac`
-+for patch in $rpatches; do
-+
-+ iname=`echo $patch | sed s%$GUILT_DIR/$branch/%%`
-+ echo "Inserting $iname"
-+
-+ # insert the patch name into the series file
-+ series_insert_patch $iname
- done
-
- disp "Done." >&2
diff --git a/meta/recipes-devtools/guilt/files/guilt-init.patch b/meta/recipes-devtools/guilt/files/guilt-init.patch
deleted file mode 100644
index 1583346..0000000
--- a/meta/recipes-devtools/guilt/files/guilt-init.patch
+++ /dev/null
@@ -1,25 +0,0 @@
-guilt: allow previously initialized branches to be re-initialized
-
-Upstream-Status: Inappropriate [oe-specific]
-
-Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
-
----
- guilt-init | 6 +++---
- 1 file changed, 3 insertions(+), 3 deletions(-)
-
---- a/guilt-init
-+++ b/guilt-init
-@@ -20,9 +20,9 @@ while case $# in 0) break ;; esac; do
- shift
- done
-
--if [ -d "$GUILT_DIR/$branch" ]; then
-- die "Branch $branch appears to be already initialized (GIT_DIR=$GIT_DIR)"
--fi
-+# if [ -d "$GUILT_DIR/$branch" ]; then
-+# die "Branch $branch appears to be already initialized (GIT_DIR=$GIT_DIR)"
-+# fi
-
- [ ! -d "$GUILT_DIR" ] && mkdir "$GUILT_DIR"
- mkdir -p "$GUILT_DIR/$branch"
diff --git a/meta/recipes-devtools/guilt/files/guilt-pop.patch b/meta/recipes-devtools/guilt/files/guilt-pop.patch
deleted file mode 100644
index 9c05427..0000000
--- a/meta/recipes-devtools/guilt/files/guilt-pop.patch
+++ /dev/null
@@ -1,73 +0,0 @@
-guilt: pop and delete tags
-
-Add support for popping to a tag and the ability to delete
-a tag while popping from the tree
-
-Upstream-Status: Inappropriate [oe-specific]
-
-Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
-
----
- guilt-pop | 28 ++++++++++++++++++++++++++--
- 1 file changed, 26 insertions(+), 2 deletions(-)
-
---- a/guilt-pop
-+++ b/guilt-pop
-@@ -17,6 +17,13 @@ while [ $# -gt 0 ]; do
- -n)
- num=t
- ;;
-+ -t|--t)
-+ tag=$2
-+ shift
-+ ;;
-+ -d|--d) # can only be used with --t
-+ delete_tag=t
-+ ;;
- *)
- break
- ;;
-@@ -24,7 +31,7 @@ while [ $# -gt 0 ]; do
- shift
- done
-
--# "guilt-pop" or "guilt-pop foo" or "guilt-pop -n foo"
-+# "guilt-pop" or "guilt-pop foo" or "guilt-pop -n foo" or "guilt-pop -t <tag>"
- if [ -z "$all" ] && [ $# -gt 1 ]; then
- usage
- fi
-@@ -44,12 +51,26 @@ fi
- patch="$1"
- [ ! -z "$all" ] && patch="-a"
-
-+
-+# tag processing will just roll into another one of
-+# the pop types, number or patch name
-+if [ ! -z "$tag" ]; then
-+ git-rev-list HEAD ^$tag > /dev/null 2>/dev/null
-+ if [ $? -eq 0 ]; then
-+ revs="`git-rev-list HEAD ^$tag`"
-+ num=`echo "$revs" | wc -l`
-+ patch=$num
-+ else
-+ echo "Cannot find tag $tag";
-+ exit 0
-+ fi
-+fi
-+
- if [ ! -s "$applied" ]; then
- disp "No patches applied."
- exit 0
- elif [ "$patch" = "-a" ]; then
- # we are supposed to pop all patches
--
- sidx=`wc -l < $applied`
- eidx=0
- elif [ ! -z "$num" ]; then
-@@ -96,3 +117,6 @@ pop_many_patches `git rev-parse refs/pat
- p=`get_top`
- [ ! -z "$p" ] && disp "Now at $p." || disp "All patches popped."
-
-+if [ ! -z "$delete_tag" ]; then
-+ git tag -d $tag
-+fi;
diff --git a/meta/recipes-devtools/guilt/files/guilt-push-no-series.patch b/meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
deleted file mode 100644
index 3446f10..0000000
--- a/meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
+++ /dev/null
@@ -1,29 +0,0 @@
-guilt-push: Avoid duplicate hits in a series
-
-If a series file becomes mangled and a patch name appears in there
-more than once, then the guilt-push will fail a horrible and
-incomprehensible death. Make it fail in a sensible way.
-
-Upstream-Status: Inappropriate [oe-specific]
-
-Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
-
----
-
- guilt-push | 5 +++++
- 1 file changed, 5 insertions(+)
-
---- a/guilt-push
-+++ b/guilt-push
-@@ -90,6 +90,11 @@ else
- if [ -z "$eidx" ]; then
- die "Patch $patch is not in the series or is guarded."
- fi
-+
-+ matches=`echo $eidx | wc -w`
-+ if [ $matches -gt 1 ]; then
-+ die "Patch $patch is in the series multiple times"
-+ fi
- fi
-
- # make sure that there are no unapplied changes
diff --git a/meta/recipes-devtools/guilt/files/guilt-push.patch b/meta/recipes-devtools/guilt/files/guilt-push.patch
deleted file mode 100644
index 5ec290b..0000000
--- a/meta/recipes-devtools/guilt/files/guilt-push.patch
+++ /dev/null
@@ -1,42 +0,0 @@
-guilt: add support for pushing and tagging
-
-It can be handy to push AND tag at the same time.
-
-Upstream-Status: Inappropriate [oe-specific]
-
-Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
-
----
-
- guilt-push | 16 +++++++++++++++-
- 1 file changed, 15 insertions(+), 1 deletion(-)
-
---- a/guilt-push
-+++ b/guilt-push
-@@ -19,7 +19,11 @@ while [ $# -gt 0 ]; do
- -n)
- num=t
- ;;
-- *)
-+ -t|--t)
-+ tag=$2
-+ shift
-+ ;;
-+ *)
- break
- ;;
- esac
-@@ -126,3 +130,13 @@ do
- fi
- done
-
-+ret=$?
-+if [ $ret -ne 0 ]; then
-+ exit $ret
-+fi
-+
-+# if a tag was specified, tag the tree now.
-+if [ -n "$tag" ]; then
-+ git-rev-parse HEAD > "$GIT_DIR/refs/tags/$tag"
-+fi
-+
diff --git a/meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch b/meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
deleted file mode 100644
index a40ec6f..0000000
--- a/meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
+++ /dev/null
@@ -1,29 +0,0 @@
-guilt: set GIT_EXEC_PATH in guilt wrapper
-
-git has the habit of tracking the directory where it was
-installed. If you build git, relocate git and then remove
-the old directory --exec-path will return that original
-(now non-existent) directory. We insist that git and
-guilt be in the same directory to ensure they are matched,
-so we use the environment variable GIT_EXEC_PATH to
-force the issue.
-
-Upstream-Status: Inappropriate [oe-specific]
-
-Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
-
----
- guilt | 2 ++
- 1 file changed, 2 insertions(+)
-
---- a/guilt
-+++ b/guilt
-@@ -23,6 +23,8 @@ esac
- # we change directories ourselves
- SUBDIRECTORY_OK=1
-
-+export GIT_EXEC_PATH=`dirname $0`/../libexec/git-core
-+
- if [ -z "$DO_NOT_USE_GITREPO_COMMANDS" ]; then
- . "$(git --exec-path)/git-sh-setup"
- fi
diff --git a/meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch b/meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
deleted file mode 100644
index 579d9bc..0000000
--- a/meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
+++ /dev/null
@@ -1,28 +0,0 @@
-From d7fb5d4e159071b6255181fcf436300038fe9e6c Mon Sep 17 00:00:00 2001
-From: Bruce Ashfield <bruce.ashfield@windriver.com>
-Date: Wed, 16 Jan 2013 20:48:11 -0500
-Subject: [PATCH] guilt: update supported git versions to 1.8.x
-
-guilt errors on the new 1.8.x git series, when it shouldn't, since
-1.8.x works fine with the existing guilt version.
-
-Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
----
- guilt | 1 +
- 1 file changed, 1 insertion(+)
-
-diff --git a/guilt b/guilt
-index 346f929..6505653 100755
---- a/guilt
-+++ b/guilt
-@@ -37,6 +37,7 @@ case "$gitver" in
- 1.5.*) ;; # git config
- 1.6.*) ;; # git config
- 1.7.*) ;; # git config
-+ 1.8.*) ;; # git config
- *) die "Unsupported version of git ($gitver)" ;;
- esac
-
---
-1.7.10.4
-
diff --git a/meta/recipes-devtools/guilt/files/guilt.patch b/meta/recipes-devtools/guilt/files/guilt.patch
deleted file mode 100644
index 8e5b61e..0000000
--- a/meta/recipes-devtools/guilt/files/guilt.patch
+++ /dev/null
@@ -1,319 +0,0 @@
-guilt: enhanced patch queue management
-
-guilt prefers to track the status and series of patches
-under .git/patches. But this location doesn't allow the
-status of a quilt queue to be committed to a secondary
-repository and later restored.
-
-This change does three things:
-
- - allows GUILT_BASE to be changed (with a default to "wrs")
- - allows shadow tracking of the patches (for rebase)
- - enhances the header detection and creation of patches
- as they are pushed onto the tree.
-
-Upstream-Status: Inappropriate [oe-specific]
-
-Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
-
----
- guilt | 183 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++---------
- 1 file changed, 159 insertions(+), 24 deletions(-)
-
---- a/guilt
-+++ b/guilt
-@@ -153,14 +153,16 @@ get_branch()
-
- verify_branch()
- {
-- [ ! -d "$GIT_DIR/patches" ] &&
-+ [ ! -d "$GUILT_DIR" ] &&
- die "Patches directory doesn't exist, try guilt-init"
-- [ ! -d "$GIT_DIR/patches/$branch" ] &&
-+ [ ! -d "$GUILT_DIR/$branch" ] &&
- die "Branch $branch is not initialized, try guilt-init"
-- [ ! -f "$GIT_DIR/patches/$branch/series" ] &&
-+ [ ! -f "$GUILT_DIR/$branch/series" ] &&
- die "Branch $branch does not have a series file"
-- [ ! -f "$GIT_DIR/patches/$branch/status" ] &&
-+ [ ! -f "$GUILT_DIR/$branch/status" ] &&
- die "Branch $branch does not have a status file"
-+ [ -f "$GUILT_DIR/$branch/applied" ] &&
-+ die "Warning: Branch $branch has 'applied' file - guilt is not compatible with stgit"
- [ -f "$GIT_DIR/patches/$branch/applied" ] &&
- die "Warning: Branch $branch has 'applied' file - guilt is not compatible with stgit"
- }
-@@ -339,6 +341,17 @@ BEGIN{}
- '
- }
-
-+# usage: do_get_only_patch patchfile
-+# similar to do_get_patch except everything leading up to
-+# the first diff line and after the last chunk are removed
-+do_get_only_patch()
-+{
-+ cat "$1" | awk '
-+BEGIN{}
-+/^(diff )/,/^(-- |END{})/
-+' | sed '/^-- *$/D'
-+}
-+
- # usage: do_get_header patchfile
- do_get_header()
- {
-@@ -352,8 +365,13 @@ do_get_header()
- BEGIN{skip=0}
- /^Subject:/ && (NR==1){print substr($0, 10); next}
- /^From:/{skip=1; next}
-+/^Author:/{skip=1; next}
-+/^Date:/{skip=1; next}
-+/^commit/{skip=1; next}
- /^[ \t\f\n\r\v]*$/ && (skip==1){skip=0; next}
- /^(diff |---$|--- )/{exit}
-+/^diff --git/{exit}
-+/^Index: /{exit}
- {print $0}
- END{}
- '
-@@ -415,6 +433,15 @@ series_insert_patch()
- mv "$series.tmp" "$series"
- }
-
-+series_append_patch()
-+{
-+ # unlike series_insert_patch, which inserts the passed
-+ # patch after the current top patch, this function always
-+ # appends the patch to the series
-+
-+ echo $1 >> "$series"
-+}
-+
- # usage: series_remove_patch <patchname>
- series_remove_patch()
- {
-@@ -473,8 +500,7 @@ remove_patch_refs()
- # usage: pop_many_patches <commitish> <number of patches>
- pop_many_patches()
- {
-- assert_head_check
--
-+ head_check "`tail -1 < "$applied" | cut -d: -f 1`"
- (
- cd_to_toplevel
-
-@@ -508,50 +534,149 @@ remove_ref()
- )
- }
-
-+prep_patch()
-+{
-+ patch=$1;
-+ tgt=$2;
-+
-+ if test -f $patch; then
-+ case $patch in
-+ *.gz) gzip -dc $patch > $tgt ;;
-+ *.bz2) bzip2 -dc $patch > $tgt ;;
-+ *) cp $patch $tgt ;;
-+ esac;
-+ fi;
-+}
-+
- # usage: commit patchname parent
- commit()
- {
- (
- TMP_MSG=`get_tmp_file msg`
-+ TMP_PATCH=`get_tmp_file patch`
-+ TMP_PATCH_OUT=`get_tmp_file patch_out`
-+ TMP_INFO=`get_tmp_file info`
-
- p="$GUILT_DIR/$branch/$1"
- pname="$1"
-+ prep_patch "$p" "$TMP_PATCH"
-+ p=$TMP_PATCH
-+
- cd_to_toplevel
-
- git diff-files --name-only | (while read n; do git update-index "$n" ; done)
-
-+ # borrowed from git-am
-+ header_type=git
-+ git mailinfo "$TMP_MSG" "$TMP_PATCH_OUT" \
-+ <"$p" >"$TMP_INFO";
-+
-+ # skip pine's internal folder data
-+ grep '^Author: Mail System Internal Data$' \
-+ <"$TMP_INFO" >/dev/null
-+
-+ git stripspace < "$TMP_MSG" > "$TMP_MSG.clean"
-+ mv "$TMP_MSG.clean" "$TMP_MSG"
-+ git stripspace < "$TMP_INFO" > "$TMP_INFO.clean"
-+ mv "$TMP_INFO.clean" "$TMP_INFO"
-+
-+ # If mailinfo couldn't get something , try another way
- # grab a commit message out of the patch
-- do_get_header "$p" > "$TMP_MSG"
-+ if [ ! -s "$TMP_MSG" ] || [ ! -s "$TMP_INFO" ]; then
-+ do_get_header "$p" > "$TMP_MSG"
-+ header_type=guilt
-+ fi
-
-- # make a default commit message if patch doesn't contain one
-- [ ! -s "$TMP_MSG" ] && echo "patch $pname" > "$TMP_MSG"
-+ # last try: make a default commit message if patch doesn't contain one
-+ [ ! -s "$TMP_MSG" ] && echo "auto_msg: patch $pname" > "$TMP_MSG"
-
-- # extract a From line from the patch header, and set
-- # GIT_AUTHOR_{NAME,EMAIL}
-- author_str=`sed -n -e '/^From:/ { s/^From: //; p; q; }; /^(diff |---$|--- )/ q' "$p"`
-- if [ ! -z "$author_str" ]; then
-+
-+ if [ "$header_type" = "guilt" ]; then
-+
-+ # extract a From line from the patch header, and set
-+ # GIT_AUTHOR_{NAME,EMAIL}
-+ author_str=`sed -n -e '/^From:/ { s/^From: //; p; q }; /^(diff |---)/ q' "$p"`
-+ if [ ! -z "$author_str" ]; then
- GIT_AUTHOR_NAME=`echo $author_str | sed -e 's/ *<.*$//'`
- export GIT_AUTHOR_NAME="${GIT_AUTHOR_NAME:-" "}"
- export GIT_AUTHOR_EMAIL="`echo $author_str | sed -e 's/[^<]*//'`"
-- fi
-+ fi
-+
-+
-+ # check in the patch for a subject
-+ SUBJECT="$(sed -n '/^Subject/ s/Subject: //p' "$p")"
-+ if [ -z "$SUBJECT" ]; then
-+ # if we can't find a subject in the patch, then let's construct
-+ # one from the header of the patch itself
-+ SUBJECT=`cat "$TMP_MSG" | head -n 1`
-+ if [ ${#SUBJECT} -gt 60 ]; then
-+ SUBJECT=${SUBJECT: -60}
-+ fi
-+ fi
-+
-+ if [ -z "$SUBJECT" ]; then
-+ # if we are *still* without a subject, then just use
-+ # the patch name
-+ SUBJECT=`echo $1 | sed 's%^patch *%%'`
-+
-+ if [ ${#SUBJECT} -gt 60 ]; then
-+ SUBJECT=${SUBJECT: -60}
-+ fi
-+ fi
-
-- # must strip nano-second part otherwise git gets very
-- # confused, and makes up strange timestamps from the past
-- # (chances are it decides to interpret it as a unix
-- # timestamp).
-- export GIT_AUTHOR_DATE="`stat -c %y "$p" | sed -e '
-+ SUBJECT=`echo $SUBJECT | sed s'%^ *%%'`
-+
-+ if [ ! -z "$SUBJECT" ]; then
-+ echo "$SUBJECT" >> $TMP_MSG.subject
-+ echo "" >> $TMP_MSG.subject
-+ cat "$TMP_MSG" >> $TMP_MSG.subject
-+ mv "$TMP_MSG.subject" "$TMP_MSG"
-+ fi
-+
-+ # must strip nano-second part otherwise git gets very
-+ # confused, and makes up strange timestamps from the past
-+ # (chances are it decides to interpret it as a unix
-+ # timestamp).
-+ export GIT_AUTHOR_DATE="`stat -c %y "$p" | sed -e '\
- s/^\([0-9]\{4\}\)-\([0-9]\{2\}\)-\([0-9]\{2\}\) \([0-9]\{2\}\):\([0-9]\{2\}\):\([0-9]\{2\}\)\.[0-9]* \(.*\)$/\1-\2-\3 \4:\5:\6 \7/'`"
-- export GIT_COMMITTER_DATE="$GIT_AUTHOR_DATE"
-+ export GIT_COMMITTER_DATE="$GIT_AUTHOR_DATE"
-+ else
-+ # using git headers, closely related to git-am
-+
-+ GIT_AUTHOR_NAME="$(sed -n '/^Author/ s/Author: //p' "$TMP_INFO")"
-+ GIT_AUTHOR_EMAIL="$(sed -n '/^Email/ s/Email: //p' "$TMP_INFO")"
-+ GIT_AUTHOR_DATE="$(sed -n '/^Date/ s/Date: //p' "$TMP_INFO")"
-+ if test -z "$GIT_AUTHOR_EMAIL"
-+ then
-+ echo "Warning: patch does not have a valid e-mail address."
-+ GIT_AUTHOR_EMAIL=$GIT_AUTHOR_NAME
-+ fi
-+
-+ SUBJECT="$(sed -n '/^Subject/ s/Subject: //p' "$TMP_INFO")"
-+ if [ ! -z "$SUBJECT" ]; then
-+ echo "$SUBJECT" >> $TMP_MSG.subject
-+ echo "" >> $TMP_MSG.subject
-+ cat "$TMP_MSG" >> $TMP_MSG.subject
-+ mv "$TMP_MSG.subject" "$TMP_MSG"
-+ fi
-+ export GIT_AUTHOR_NAME GIT_AUTHOR_EMAIL GIT_AUTHOR_DATE
-+ fi
-
- # commit
- treeish=`git write-tree`
- commitish=`git commit-tree $treeish -p $2 < "$TMP_MSG"`
-+ if [ ! $? -eq 0 ]; then
-+ echo "ERROR. Could not commit tree"
-+ git-reset --hard HEAD^
-+ exit 1
-+ fi
- git update-ref HEAD $commitish
-
- # mark patch as applied
- git update-ref "refs/patches/$branch/$pname" HEAD
-
-- rm -f "$TMP_MSG"
-+ rm -f "$TMP_MSG" "$TMP_LOG" "$TMP_PATCH" "$TMP_INFO" "$TMP_PATCH_OUT"
-+
- )
- }
-
-@@ -568,7 +693,7 @@ push_patch()
- bail_action="$2"
- reject="--reject"
-
-- assert_head_check
-+ head_check "`tail -1 < "$applied" | cut -d: -f 1`"
- cd_to_toplevel
-
- # apply the patch if and only if there is something to apply
-@@ -671,7 +796,7 @@ refresh_patch()
- # incldiffstat
- __refresh_patch()
- {
-- assert_head_check
-+ head_check "`tail -1 < "$applied" | cut -d: -f 1`"
-
- (
- TMP_DIFF=`get_tmp_file diff`
-@@ -711,6 +836,10 @@ __refresh_patch()
-
- head -n "-$N" < "$applied" > "$applied.tmp"
- mv "$applied.tmp" "$applied"
-+
-+ # update the shadow status.
-+ ref=`cat $GIT_DIR/refs/tags/${branch}_top`
-+ echo "$ref:$1" >> $applied_shadow
- )
- }
-
-@@ -791,7 +920,12 @@ diffstat=`git config --bool guilt.diffst
- # The following gets run every time this file is source'd
- #
-
--GUILT_DIR="$GIT_DIR/patches"
-+
-+# GUILT_DIR="$GIT_DIR/patches"
-+if [ -z "$GUILT_BASE" ]; then
-+ GUILT_BASE=wrs
-+fi
-+GUILT_DIR="$GUILT_BASE/patches"
-
- branch=`get_branch`
-
-@@ -814,6 +948,7 @@ fi
- # very useful files
- series="$GUILT_DIR/$branch/series"
- applied="$GUILT_DIR/$branch/status"
-+applied_shadow="$GUILT_DIR/$branch/shadow_status"
- guards_file="$GUILT_DIR/$branch/guards"
-
- # determine a pager to use for anything interactive (fall back to more)
diff --git a/meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch b/meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
deleted file mode 100644
index fa7dd8a..0000000
--- a/meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
+++ /dev/null
@@ -1,71 +0,0 @@
-guilt: improve the generation of an automatic header
-
-Patches that do not have a proper header are encountered when generating
-a tree. This improves the detection of these patches and generates a sane
-header so the eventual commit will be coherent
-
-Upstream-Status: Inappropriate [oe-specific]
-
-Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
-
----
-
- guilt | 24 ++++++++++++++++++------
- 1 file changed, 18 insertions(+), 6 deletions(-)
-
---- a/guilt
-+++ b/guilt
-@@ -591,7 +591,12 @@ commit()
- fi
-
- # last try: make a default commit message if patch doesn't contain one
-- [ ! -s "$TMP_MSG" ] && echo "auto_msg: patch $pname" > "$TMP_MSG"
-+ if [ ! -s "$TMP_MSG" ]; then
-+ echo "auto_msg: importing `basename $pname`" > "$TMP_MSG"
-+ echo "" >> "$TMP_MSG"
-+ echo "This is an automatic import of patch $pname, no headers were" >> "$TMP_MSG"
-+ echo "detected and a default message was constructed" >> "$TMP_MSG"
-+ fi
-
-
- if [ "$header_type" = "guilt" ]; then
-@@ -599,12 +604,14 @@ commit()
- # extract a From line from the patch header, and set
- # GIT_AUTHOR_{NAME,EMAIL}
- author_str=`sed -n -e '/^From:/ { s/^From: //; p; q }; /^(diff |---)/ q' "$p"`
-- if [ ! -z "$author_str" ]; then
-- GIT_AUTHOR_NAME=`echo $author_str | sed -e 's/ *<.*$//'`
-- export GIT_AUTHOR_NAME="${GIT_AUTHOR_NAME:-" "}"
-- export GIT_AUTHOR_EMAIL="`echo $author_str | sed -e 's/[^<]*//'`"
-+ if [ -z "$author_str" ]; then
-+ author_str="auto commit <unknown@unknown>"
- fi
-
-+ GIT_AUTHOR_NAME=`echo $author_str | sed -e 's/ *<.*$//'`
-+ export GIT_AUTHOR_NAME="${GIT_AUTHOR_NAME:-" "}"
-+ export GIT_AUTHOR_EMAIL="`echo $author_str | sed -e 's/[^<]*//'`"
-+
-
- # check in the patch for a subject
- SUBJECT="$(sed -n '/^Subject/ s/Subject: //p' "$p")"
-@@ -615,6 +622,11 @@ commit()
- if [ ${#SUBJECT} -gt 60 ]; then
- SUBJECT=${SUBJECT: -60}
- fi
-+
-+ # remove the line from the tmp msg
-+ mv "$TMP_MSG" "$TMP_MSG.work"
-+ cat "$TMP_MSG.work" | grep -v -E ".*$SUBJECT.*" > "$TMP_MSG"
-+ rm "$TMP_MSG.work"
- fi
-
- if [ -z "$SUBJECT" ]; then
-@@ -629,7 +641,7 @@ commit()
-
- SUBJECT=`echo $SUBJECT | sed s'%^ *%%'`
-
-- if [ ! -z "$SUBJECT" ]; then
-+ if [ -n "$SUBJECT" ]; then
- echo "$SUBJECT" >> $TMP_MSG.subject
- echo "" >> $TMP_MSG.subject
- cat "$TMP_MSG" >> $TMP_MSG.subject
diff --git a/meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch b/meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
deleted file mode 100644
index c912397..0000000
--- a/meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
+++ /dev/null
@@ -1,48 +0,0 @@
-guilt: allow operation outside of git repos
-
-Sometimes guilt is sourced when there isn't a containing git repository.
-Some of the git commands that are always called will report errors
-unecesarility in this scenario. This adds a variable that will inhibit
-those problematic calls
-
-Upstream-Status: Inappropriate [oe-specific]
-
-Signed-off-by <bruce.ashfield@windriver.com>
-
----
-
- guilt | 9 ++++++---
- 1 file changed, 6 insertions(+), 3 deletions(-)
-
-
---- a/guilt
-+++ b/guilt
-@@ -23,7 +23,9 @@ esac
- # we change directories ourselves
- SUBDIRECTORY_OK=1
-
--. "$(git --exec-path)/git-sh-setup"
-+if [ -z "$DO_NOT_USE_GITREPO_COMMANDS" ]; then
-+ . "$(git --exec-path)/git-sh-setup"
-+fi
-
- #
- # Git version check
-@@ -921,14 +923,15 @@ diffstat=`git config --bool guilt.diffst
- # The following gets run every time this file is source'd
- #
-
--
- # GUILT_DIR="$GIT_DIR/patches"
- if [ -z "$GUILT_BASE" ]; then
- GUILT_BASE=wrs
- fi
- GUILT_DIR="$GUILT_BASE/patches"
-
--branch=`get_branch`
-+if [ -z "$DO_NOT_USE_GITREPO_COMMANDS" ]; then
-+ branch=`get_branch`
-+fi
-
- # most of the time we want to verify that the repo's branch has been
- # initialized, but every once in a blue moon (e.g., we want to run guilt-init),
diff --git a/meta/recipes-devtools/guilt/files/optional_head_check.patch b/meta/recipes-devtools/guilt/files/optional_head_check.patch
deleted file mode 100644
index 01e1d02..0000000
--- a/meta/recipes-devtools/guilt/files/optional_head_check.patch
+++ /dev/null
@@ -1,60 +0,0 @@
-guilt: allow guilt-push to opt out of head checking
-
-Depending on the method used to construct a tree, it is entirely
-possible that branches are not only made up of guilt created commits.
-This mixed mode is valid, and in particular is valid when applying
-patches to a tree.
-
-In the default mode of operation, you will see a warning such as
-this when working on a branch:
-
-Expected HEAD commit dbd5861f81a92b8b329561f94b8575c7ee6768b6
- got 3e8e6f6bd9f1772b91fc1fe9949f541d0560b487
-
-This looks severe, but is harmless during tree construction,
-since even if the HEAD commit was expected, you can still run into
-issues pushing a patch. This is particularly seen when templates are
-adding patches to a kernel.
-
-To make this look less ominous, we make the head check for patch
-pushing opt-in. Which means that by default, you'll no longer see
-this warning if you work with a mixed mode branch during tree
-construction.
-
-Other modes such as pop or refresh can run into problems when
-the HEAD commit isn't tracked or expected, so they should remained
-checked.
-
-Upstream-Status: Inappropriate [oe-specific]
-
-Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
-
----
- guilt | 3 +++
- guilt-push | 3 +++
- 2 files changed, 6 insertions(+)
-
---- a/guilt
-+++ b/guilt
-@@ -417,6 +417,9 @@ head_check()
- return 0 ;;
- esac
-
-+ # If do_head_check isn't set, bail, we are "opt-in"
-+ [ -z "$do_head_check" ] && return 0
-+
- if [ "`git rev-parse refs/heads/$branch`" != "`git rev-parse $1`" ]; then
- disp "Expected HEAD commit $1" >&2
- disp " got `git rev-parse refs/heads/$branch`" >&2
---- a/guilt-push
-+++ b/guilt-push
-@@ -23,6 +23,9 @@ while [ $# -gt 0 ]; do
- tag=$2
- shift
- ;;
-+ --head_check)
-+ do_head_check=t
-+ ;;
- *)
- break
- ;;
diff --git a/meta/recipes-devtools/guilt/files/uninstall_force.patch b/meta/recipes-devtools/guilt/files/uninstall_force.patch
deleted file mode 100644
index 8f7cea1..0000000
--- a/meta/recipes-devtools/guilt/files/uninstall_force.patch
+++ /dev/null
@@ -1,14 +0,0 @@
-guilt: force removal when uninstalling
-
-Upstream-Status: Inappropriate [oe-specific]
-
-Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
-
---- a/uninstall.orig
-+++ b/uninstall
-@@ -12,4 +12,4 @@
-
- shift
-
--(cd $PRE; rm "$@")
-+(cd $PRE; rm -f "$@")
diff --git a/meta/recipes-devtools/guilt/guilt-native_0.33.bb b/meta/recipes-devtools/guilt/guilt-native_git.bb
similarity index 45%
rename from meta/recipes-devtools/guilt/guilt-native_0.33.bb
rename to meta/recipes-devtools/guilt/guilt-native_git.bb
index d4dd616..9c75c3c 100644
--- a/meta/recipes-devtools/guilt/guilt-native_0.33.bb
+++ b/meta/recipes-devtools/guilt/guilt-native_git.bb
@@ -3,24 +3,15 @@ LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://COPYING;md5=b6f3400dc1a01cebafe8a52b3f344135"
-PV = "0.33"
-PR = "r4"
-
inherit native
-SRC_URI = "http://ftp.de.debian.org/debian/pool/main/g/guilt/guilt_${PV}.orig.tar.gz\
- file://guilt-push.patch \
- file://guilt-pop.patch \
- file://guilt.patch \
- file://guilt-init.patch \
- file://guilt-import-commit.patch \
- file://uninstall_force.patch \
- file://guilt-push-no-series.patch \
- file://make_git_commands_conditional.patch \
- file://improve_auto_header_gen.patch \
+SRC_URI = "git://repo.or.cz/guilt.git \
file://guilt-bash.patch \
- file://guilt-update-supported-git-versions-to-1.8.x.patch \
- file://optional_head_check.patch"
+ "
+
+SRCREV="c2a5bae511c6d5354aa4e1cb59069c31df2b8eeb"
+
+S="${WORKDIR}/git"
SRC_URI[md5sum] = "d800c5e0743d90543ef51d797a626e09"
SRC_URI[sha256sum] = "64dfe6af1e924030f71163f3aa12cd846c80901d6ff8ef267ea35bb0752b4ba9"
--
1.7.10.4
^ permalink raw reply related [flat|nested] 61+ messages in thread
* [PATCH 3/5] linux-libc-headers: update to v3.10
2013-08-23 18:08 [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
2013-08-23 18:08 ` [PATCH 1/5] kern-tools: usability, bug fixes and no guilt Bruce Ashfield
2013-08-23 18:08 ` [PATCH 2/5] guilt: update to latest git version Bruce Ashfield
@ 2013-08-23 18:08 ` Bruce Ashfield
2013-08-23 18:08 ` [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure Bruce Ashfield
` (3 subsequent siblings)
6 siblings, 0 replies; 61+ messages in thread
From: Bruce Ashfield @ 2013-08-23 18:08 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
Now that the 3.10 kernel has been released we can bump the libc-headers to
that version and remove the 3.8 variant. Userspace compatibility is
maintained through kernel versions, we also make the single 3.10 version the
toolchain default.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
meta/conf/distro/include/tcmode-default.inc | 2 +-
| 7 +++++++
| 8 --------
3 files changed, 8 insertions(+), 9 deletions(-)
create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
delete mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
diff --git a/meta/conf/distro/include/tcmode-default.inc b/meta/conf/distro/include/tcmode-default.inc
index aa0db25..fb41d5e 100644
--- a/meta/conf/distro/include/tcmode-default.inc
+++ b/meta/conf/distro/include/tcmode-default.inc
@@ -22,7 +22,7 @@ SDKGCCVERSION ?= "${GCCVERSION}"
BINUVERSION ?= "2.23.2"
EGLIBCVERSION ?= "2.18"
UCLIBCVERSION ?= "0.9.33+git%"
-LINUXLIBCVERSION ?= "3.8"
+LINUXLIBCVERSION ?= "3.10"
PREFERRED_VERSION_gcc ?= "${GCCVERSION}"
PREFERRED_VERSION_gcc-cross ?= "${GCCVERSION}"
--git a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
new file mode 100644
index 0000000..eb04367
--- /dev/null
+++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
@@ -0,0 +1,7 @@
+require linux-libc-headers.inc
+
+PR = "r0"
+
+SRC_URI[md5sum] = "72d0a9b3e60cd86fabcd3f24b1708944"
+SRC_URI[sha256sum] = "46c9e55e1fddf40813b8d697d5645037a8e2af5c1a8dff52b3fe82b5021582b8"
+
diff --git a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
deleted file mode 100644
index 5672bd4..0000000
--- a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
+++ /dev/null
@@ -1,8 +0,0 @@
-require linux-libc-headers.inc
-
-SRC_URI += "file://scripts-Makefile.headersinst-install-headers-from-sc.patch"
-
-PR = "r0"
-
-SRC_URI[md5sum] = "fcd1d2e60e1033c935a13ef81c89ea2d"
-SRC_URI[sha256sum] = "fce774b5313e73949cb35f128e91e7b2ccd7fa2438abc5cff69267e504395a45"
--
1.7.10.4
^ permalink raw reply related [flat|nested] 61+ messages in thread
* [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
2013-08-23 18:08 [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
` (2 preceding siblings ...)
2013-08-23 18:08 ` [PATCH 3/5] linux-libc-headers: update to v3.10 Bruce Ashfield
@ 2013-08-23 18:08 ` Bruce Ashfield
2013-08-23 18:08 ` [PATCH 5/5] linux-yocto: introduce v3.10 Bruce Ashfield
` (2 subsequent siblings)
6 siblings, 0 replies; 61+ messages in thread
From: Bruce Ashfield @ 2013-08-23 18:08 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
kernel commit 24b9f5017 [[media] V4L: Remove deprecated image centering controls]
removed the definitions of V4L2_CID_HCENTER and V4L2_CID_VCENTER after three
years of depreciation.
The ioctl values are still free, and the case statement which processess them
in v4l2 userspace falls through to the proper replacement. So in the short
term, we can explicitly define them using the old absolute values, and everything
will work.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 ++++++++++++++++++++
.../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
2 files changed, 46 insertions(+)
create mode 100644 meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
diff --git a/meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch b/meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
new file mode 100644
index 0000000..bd0de58
--- /dev/null
+++ b/meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
@@ -0,0 +1,45 @@
+From ccb01de8096a32d86d47b0d92ec3416c57ee4d25 Mon Sep 17 00:00:00 2001
+From: Bruce Ashfield <bruce.ashfield@windriver.com>
+Date: Thu, 22 Aug 2013 12:15:54 -0400
+Subject: [PATCH] v4l2_calls: define V4L2_CID_HCENTER and V4L2_CID_VCENTER
+
+kernel commit 24b9f5017 [[media] V4L: Remove deprecated image centering controls]
+removed the definitions of V4L2_CID_HCENTER and V4L2_CID_VCENTER after three
+years of depreciation.
+
+The ioctl values are still free, and the case statement which processess them
+in v4l2 userspace falls through to the proper replacement. So in the short
+term, we can explicitly define them using the old absolute values, and everything
+will work.
+
+Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
+---
+ sys/v4l2/v4l2_calls.c | 9 +++++++--
+ 1 file changed, 7 insertions(+), 2 deletions(-)
+
+diff --git a/sys/v4l2/v4l2_calls.c b/sys/v4l2/v4l2_calls.c
+index 309bfb6..3c64544 100644
+--- a/sys/v4l2/v4l2_calls.c
++++ b/sys/v4l2/v4l2_calls.c
+@@ -54,11 +54,16 @@
+ #include "gst/gst-i18n-plugin.h"
+
+ /* Those are ioctl calls */
++
++/* V4L2_CID_HCENTER has been removed from the mainline kernel, but
++ the ioctl space is still present. Since these values fall through
++ to their replacement, it is safe (in the short term) to re-use the
++ old values explictily */
+ #ifndef V4L2_CID_HCENTER
+-#define V4L2_CID_HCENTER V4L2_CID_HCENTER_DEPRECATED
++#define V4L2_CID_HCENTER V4L2_CID_BASE+22
+ #endif
+ #ifndef V4L2_CID_VCENTER
+-#define V4L2_CID_VCENTER V4L2_CID_VCENTER_DEPRECATED
++#define V4L2_CID_VCENTER V4L2_CID_BASE+23
+ #endif
+
+ GST_DEBUG_CATEGORY_EXTERN (v4l2_debug);
+--
+1.7.10.4
+
diff --git a/meta/recipes-multimedia/gstreamer/gst-plugins-good_0.10.31.bb b/meta/recipes-multimedia/gstreamer/gst-plugins-good_0.10.31.bb
index daffcf1..d18e155 100644
--- a/meta/recipes-multimedia/gstreamer/gst-plugins-good_0.10.31.bb
+++ b/meta/recipes-multimedia/gstreamer/gst-plugins-good_0.10.31.bb
@@ -23,6 +23,7 @@ DEPENDS += "gst-plugins-base gconf cairo libpng zlib libid3tag flac \
inherit gettext gconf
SRC_URI += "file://0001-v4l2-fix-build-with-recent-kernels-the-v4l2_buffer-i.patch"
+SRC_URI += "file://0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch"
EXTRA_OECONF += "--disable-aalib --disable-esd --disable-shout2 --disable-libcaca --disable-hal --without-check \
--disable-examples --disable-taglib"
--
1.7.10.4
^ permalink raw reply related [flat|nested] 61+ messages in thread
* [PATCH 5/5] linux-yocto: introduce v3.10
2013-08-23 18:08 [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
` (3 preceding siblings ...)
2013-08-23 18:08 ` [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure Bruce Ashfield
@ 2013-08-23 18:08 ` Bruce Ashfield
2013-08-24 0:57 ` Jonathan Liu
2013-08-23 21:30 ` [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
2013-08-24 6:33 ` Saul Wold
6 siblings, 1 reply; 61+ messages in thread
From: Bruce Ashfield @ 2013-08-23 18:08 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
Introduce the 3.10 kernel. This is based on the 3.10.9 upstream kernel
and replaces the 3.8 recipes, which will be removed once all reference
boards have been updated.
3.10 also the latest LTSI and will be updated with that content when it
becomes available.
Other features of the 3.10 kernel include:
- refreshed -rt support
- refreshed yaffs2, aufs3
- cryptodev
- bfs, edf, and OCF staged features
- scrubbed and updated meta data for v3.10
- improved tools support for meta data updates and queue maintenance
- patch carry forward from all previous linux-yocto kernels and
configuration.
This kernel has been built and boot tested on all qemu machines and architectures.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++++++++++++++++++++
meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++++++++++++++++
meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++++++++++++++++++++
3 files changed, 85 insertions(+)
create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb b/meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
new file mode 100644
index 0000000..4139be8
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
@@ -0,0 +1,30 @@
+require recipes-kernel/linux/linux-yocto.inc
+
+KBRANCH = "standard/preempt-rt/base"
+KBRANCH_qemuppc = "standard/preempt-rt/qemuppc"
+
+SRCREV_machine ?= "77c5842818867366c3d08ca1dec19dc43aee0e91"
+SRCREV_machine_qemuppc ?= "7be83bc1124d2a2c75f99df94baaf718659722ea"
+SRCREV_meta ?= "1b9b113837f353fd94148beb6bd00a3b7b35d01d"
+
+SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.10.git;protocol=git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta"
+
+LINUX_VERSION ?= "3.10.9"
+
+PV = "${LINUX_VERSION}+git${SRCPV}"
+
+KMETA = "meta"
+
+LINUX_KERNEL_TYPE = "preempt-rt"
+
+# Omit broken machines from COMPATIBLE_MACHINE
+# qemuppc hangs at boot
+# qemumips panics at boot
+COMPATIBLE_MACHINE = "(qemux86|qemux86-64|qemuarm)"
+
+# Functionality flags
+KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc features/taskstats/taskstats.scc"
+KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
+KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
+KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc"
+KERNEL_FEATURES_append = " ${@bb.utils.contains("TUNE_FEATURES", "mx32", " cfg/x32.scc", "" ,d)}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
new file mode 100644
index 0000000..1c2ad37
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
@@ -0,0 +1,25 @@
+require recipes-kernel/linux/linux-yocto.inc
+
+# We need lzma (as CONFIG_KERNEL_LZMA=y)
+DEPENDS += "xz-native"
+
+KBRANCH_DEFAULT = "standard/tiny/base"
+KBRANCH = "${KBRANCH_DEFAULT}"
+LINUX_KERNEL_TYPE = "tiny"
+KCONFIG_MODE = "--allnoconfig"
+
+LINUX_VERSION ?= "3.10.9"
+
+KMETA = "meta"
+
+SRCREV_machine ?= "6c1528b2b78d1ec7e75bb7a9880074ec35aa1aa0"
+SRCREV_meta ?= "1b9b113837f353fd94148beb6bd00a3b7b35d01d"
+
+PV = "${LINUX_VERSION}+git${SRCPV}"
+
+SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.10.git;protocol=git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta"
+
+COMPATIBLE_MACHINE = "(qemux86)"
+
+# Functionality flags
+KERNEL_FEATURES = ""
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.10.bb b/meta/recipes-kernel/linux/linux-yocto_3.10.bb
new file mode 100644
index 0000000..ea6ad2a
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto_3.10.bb
@@ -0,0 +1,30 @@
+require recipes-kernel/linux/linux-yocto.inc
+
+KBRANCH_DEFAULT = "standard/base"
+KBRANCH = "${KBRANCH_DEFAULT}"
+
+SRCREV_machine_qemuarm ?= "8675d3d0a3c17135f70ef474d5c362397c02e62a"
+SRCREV_machine_qemumips ?= "992b743b905edd21d3a4a27c92b5c6a9e44d7d73"
+SRCREV_machine_qemuppc ?= "09388c3572e26c78b34554e46e077f12be7b2401"
+SRCREV_machine_qemux86 ?= "6c1528b2b78d1ec7e75bb7a9880074ec35aa1aa0"
+SRCREV_machine_qemux86-64 ?= "6c1528b2b78d1ec7e75bb7a9880074ec35aa1aa0"
+SRCREV_machine_qemumips64 ?= "203679cb23c752fdcbc0180a55a81728d7462561"
+SRCREV_machine ?= "6c1528b2b78d1ec7e75bb7a9880074ec35aa1aa0"
+SRCREV_meta ?= "1b9b113837f353fd94148beb6bd00a3b7b35d01d"
+
+SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.10.git;protocol=git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
+
+LINUX_VERSION ?= "3.10.9"
+
+PV = "${LINUX_VERSION}+git${SRCPV}"
+
+KMETA = "meta"
+
+COMPATIBLE_MACHINE = "qemuarm|qemux86|qemuppc|qemumips|qemumips64|qemux86-64"
+
+# Functionality flags
+KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc"
+KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
+KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
+KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc"
+KERNEL_FEATURES_append = " ${@bb.utils.contains("TUNE_FEATURES", "mx32", " cfg/x32.scc", "" ,d)}"
--
1.7.10.4
^ permalink raw reply related [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2013-08-23 18:08 [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
` (4 preceding siblings ...)
2013-08-23 18:08 ` [PATCH 5/5] linux-yocto: introduce v3.10 Bruce Ashfield
@ 2013-08-23 21:30 ` Bruce Ashfield
2013-08-24 6:33 ` Saul Wold
6 siblings, 0 replies; 61+ messages in thread
From: Bruce Ashfield @ 2013-08-23 21:30 UTC (permalink / raw)
To: Richard Purdie; +Cc: Patches and discussions about the oe-core layer
On Fri, Aug 23, 2013 at 2:08 PM, Bruce Ashfield
<bruce.ashfield@windriver.com> wrote:
> Richard/Saul,
>
> Here's my consolidated set of changes that represent the biggest chunk
> of work for the Yocto 1.5 release. The obvious change is that the 3.10
> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
> mark on). I've built and booted core-image-sato for all the oe-core
> qemu machines.
>
> 3.10 also the latest LTSI and will be updated with that content when it
> becomes available.
>
> Other features of the 3.10 kernel include:
>
> - refreshed -rt support
> - refreshed yaffs2, aufs3
> - cryptodev
> - bfs, edf, and OCF staged features
> - scrubbed and updated meta data for v3.10
> - improved tools support for meta data updates and queue maintenance
> - patch carry forward from all previous linux-yocto kernels and
> configuration.
>
> I've also tested linux-yocto-rt and linux-yocto-tiny for the new, shiny tree.
>
> I've also bumped the linux-libc-headers to 3.10 and have fixed gst-plugins-good
> to adapt to a changed #define in the exported headers.
>
> Other parts of this update include an uprev of guilt, and in fact, a
> restoration of "normal" guil operations, since the kernel tree is now
> manipulated and maintained via a smaller, more contained script. This
> was necessary for both usability reasons and the fact that all of guilts
> protections were being removed for the kernel's use .. which makes you
> ask the quesetion "why use it". It was time for a change.
>
> The patches are pretty self explanitory and all contain detailed long
> logs .. but the summary is:
>
> [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
> [PATCH 2/5] guilt: update to latest git version
> [PATCH 3/5] linux-libc-headers: update to v3.10
> [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
> [PATCH 5/5] linux-yocto: introduce v3.10
>
> ** There is one pending activity. As part of thsi update to 3.10, we want
> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
> routerstationpro BSP is still using it as its preferred version. I'm
> a one man show on this update, and I wasn't able to get the 100+ patches
> ported to 3.10 AND get this update out before the M4 cutoff.
Good news on this front. The routerstation pro (and it's replacement after
1.5) are working on 3.10 with the patches rebased. I'll follow up later with
the update of the rsp and the removal of the 3.8 recipe.
The beagleboard and fsl board will follow after that as well, pending some
boot testing.
Cheers,
Bruce
>
> ** I'm still attempting to udpate all the reference boards, and
> once done, I'll send a follow up patch.
>
> ** Please test, I've done my best, but things can slip through. We'll
> work issues in the stabilization period.
>
> Cheers,
>
> Bruce
>
>
> The following changes since commit 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>
> bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40 +0100)
>
> are available in the git repository at:
>
> git://git.pokylinux.org/poky-contrib zedd/kernel
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Bruce Ashfield (5):
> kern-tools: usability, bug fixes and no guilt
> guilt: update to latest git version
> linux-libc-headers: update to v3.10
> gst-plugins-good: fix 3.10 libc-headers build failure
> linux-yocto: introduce v3.10
>
> meta/classes/kernel-yocto.bbclass | 2 +
> meta/conf/distro/include/tcmode-default.inc | 2 +-
> .../guilt/files/guilt-import-commit.patch | 96 ------
> meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
> meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
> .../guilt/files/guilt-push-no-series.patch | 29 --
> meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
> .../guilt/files/guilt-set-git_exec_path.patch | 29 --
> ...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
> meta/recipes-devtools/guilt/files/guilt.patch | 319 --------------------
> .../guilt/files/improve_auto_header_gen.patch | 71 -----
> .../files/make_git_commands_conditional.patch | 48 ---
> .../guilt/files/optional_head_check.patch | 60 ----
> .../guilt/files/uninstall_force.patch | 14 -
> .../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
> .../kern-tools/kern-tools-native_git.bb | 6 +-
> .../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
> .../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
> ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
> .../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
> 23 files changed, 150 insertions(+), 861 deletions(-)
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-import-commit.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-init.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/optional_head_check.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/uninstall_force.patch
> rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb => guilt-native_git.bb} (45%)
> create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
> delete mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
> create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
> create mode 100644 meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>
> --
> 1.7.10.4
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 5/5] linux-yocto: introduce v3.10
2013-08-23 18:08 ` [PATCH 5/5] linux-yocto: introduce v3.10 Bruce Ashfield
@ 2013-08-24 0:57 ` Jonathan Liu
2013-08-24 13:36 ` Bruce Ashfield
0 siblings, 1 reply; 61+ messages in thread
From: Jonathan Liu @ 2013-08-24 0:57 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On 24/08/2013 4:08 AM, Bruce Ashfield wrote:
> Introduce the 3.10 kernel. This is based on the 3.10.9 upstream kernel
> and replaces the 3.8 recipes, which will be removed once all reference
> boards have been updated.
>
> 3.10 also the latest LTSI and will be updated with that content when it
> becomes available.
>
> Other features of the 3.10 kernel include:
>
> - refreshed -rt support
> - refreshed yaffs2, aufs3
> - cryptodev
> - bfs, edf, and OCF staged features
> - scrubbed and updated meta data for v3.10
> - improved tools support for meta data updates and queue maintenance
> - patch carry forward from all previous linux-yocto kernels and
> configuration.
>
> This kernel has been built and boot tested on all qemu machines and architectures.
>
> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
> ---
> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++++++++++++++++++++
> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++++++++++++++++
> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++++++++++++++++++++
> 3 files changed, 85 insertions(+)
> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
> create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>
> diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb b/meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
> new file mode 100644
> index 0000000..4139be8
> --- /dev/null
> +++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
> @@ -0,0 +1,30 @@
> +require recipes-kernel/linux/linux-yocto.inc
> +
> +KBRANCH = "standard/preempt-rt/base"
> +KBRANCH_qemuppc = "standard/preempt-rt/qemuppc"
> +
> +SRCREV_machine ?= "77c5842818867366c3d08ca1dec19dc43aee0e91"
> +SRCREV_machine_qemuppc ?= "7be83bc1124d2a2c75f99df94baaf718659722ea"
> +SRCREV_meta ?= "1b9b113837f353fd94148beb6bd00a3b7b35d01d"
> +
> +SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.10.git;protocol=git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta"
> +
> +LINUX_VERSION ?= "3.10.9"
> +
> +PV = "${LINUX_VERSION}+git${SRCPV}"
> +
> +KMETA = "meta"
> +
> +LINUX_KERNEL_TYPE = "preempt-rt"
> +
> +# Omit broken machines from COMPATIBLE_MACHINE
> +# qemuppc hangs at boot
> +# qemumips panics at boot
> +COMPATIBLE_MACHINE = "(qemux86|qemux86-64|qemuarm)"
I see COMPATIBLE_MACHINE has been carried over from the 3.4 and 3.8
linux-rt recipes. Is linux-rt still broken on qemuppc and qemumips?
> +
> +# Functionality flags
> +KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc features/taskstats/taskstats.scc"
> +KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
> +KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
> +KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc"
> +KERNEL_FEATURES_append = " ${@bb.utils.contains("TUNE_FEATURES", "mx32", " cfg/x32.scc", "" ,d)}"
> diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
> new file mode 100644
> index 0000000..1c2ad37
> --- /dev/null
> +++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
> @@ -0,0 +1,25 @@
> +require recipes-kernel/linux/linux-yocto.inc
> +
> +# We need lzma (as CONFIG_KERNEL_LZMA=y)
> +DEPENDS += "xz-native"
> +
> +KBRANCH_DEFAULT = "standard/tiny/base"
> +KBRANCH = "${KBRANCH_DEFAULT}"
> +LINUX_KERNEL_TYPE = "tiny"
> +KCONFIG_MODE = "--allnoconfig"
> +
> +LINUX_VERSION ?= "3.10.9"
> +
> +KMETA = "meta"
> +
> +SRCREV_machine ?= "6c1528b2b78d1ec7e75bb7a9880074ec35aa1aa0"
> +SRCREV_meta ?= "1b9b113837f353fd94148beb6bd00a3b7b35d01d"
> +
> +PV = "${LINUX_VERSION}+git${SRCPV}"
> +
> +SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.10.git;protocol=git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta"
> +
> +COMPATIBLE_MACHINE = "(qemux86)"
> +
> +# Functionality flags
> +KERNEL_FEATURES = ""
> diff --git a/meta/recipes-kernel/linux/linux-yocto_3.10.bb b/meta/recipes-kernel/linux/linux-yocto_3.10.bb
> new file mode 100644
> index 0000000..ea6ad2a
> --- /dev/null
> +++ b/meta/recipes-kernel/linux/linux-yocto_3.10.bb
> @@ -0,0 +1,30 @@
> +require recipes-kernel/linux/linux-yocto.inc
> +
> +KBRANCH_DEFAULT = "standard/base"
> +KBRANCH = "${KBRANCH_DEFAULT}"
> +
> +SRCREV_machine_qemuarm ?= "8675d3d0a3c17135f70ef474d5c362397c02e62a"
> +SRCREV_machine_qemumips ?= "992b743b905edd21d3a4a27c92b5c6a9e44d7d73"
> +SRCREV_machine_qemuppc ?= "09388c3572e26c78b34554e46e077f12be7b2401"
> +SRCREV_machine_qemux86 ?= "6c1528b2b78d1ec7e75bb7a9880074ec35aa1aa0"
> +SRCREV_machine_qemux86-64 ?= "6c1528b2b78d1ec7e75bb7a9880074ec35aa1aa0"
> +SRCREV_machine_qemumips64 ?= "203679cb23c752fdcbc0180a55a81728d7462561"
> +SRCREV_machine ?= "6c1528b2b78d1ec7e75bb7a9880074ec35aa1aa0"
> +SRCREV_meta ?= "1b9b113837f353fd94148beb6bd00a3b7b35d01d"
> +
> +SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.10.git;protocol=git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
> +
> +LINUX_VERSION ?= "3.10.9"
> +
> +PV = "${LINUX_VERSION}+git${SRCPV}"
> +
> +KMETA = "meta"
> +
> +COMPATIBLE_MACHINE = "qemuarm|qemux86|qemuppc|qemumips|qemumips64|qemux86-64"
> +
> +# Functionality flags
> +KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc"
> +KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
> +KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
> +KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc"
> +KERNEL_FEATURES_append = " ${@bb.utils.contains("TUNE_FEATURES", "mx32", " cfg/x32.scc", "" ,d)}"
Regards,
Jonathan
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2013-08-23 18:08 [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
` (5 preceding siblings ...)
2013-08-23 21:30 ` [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
@ 2013-08-24 6:33 ` Saul Wold
2013-08-24 13:34 ` Bruce Ashfield
6 siblings, 1 reply; 61+ messages in thread
From: Saul Wold @ 2013-08-24 6:33 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
> Richard/Saul,
>
> Here's my consolidated set of changes that represent the biggest chunk
> of work for the Yocto 1.5 release. The obvious change is that the 3.10
> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
> mark on). I've built and booted core-image-sato for all the oe-core
> qemu machines.
>
> 3.10 also the latest LTSI and will be updated with that content when it
> becomes available.
>
> Other features of the 3.10 kernel include:
>
> - refreshed -rt support
> - refreshed yaffs2, aufs3
> - cryptodev
> - bfs, edf, and OCF staged features
> - scrubbed and updated meta data for v3.10
> - improved tools support for meta data updates and queue maintenance
> - patch carry forward from all previous linux-yocto kernels and
> configuration.
>
> I've also tested linux-yocto-rt and linux-yocto-tiny for the new, shiny tree.
>
> I've also bumped the linux-libc-headers to 3.10 and have fixed gst-plugins-good
> to adapt to a changed #define in the exported headers.
>
> Other parts of this update include an uprev of guilt, and in fact, a
> restoration of "normal" guil operations, since the kernel tree is now
> manipulated and maintained via a smaller, more contained script. This
> was necessary for both usability reasons and the fact that all of guilts
> protections were being removed for the kernel's use .. which makes you
> ask the quesetion "why use it". It was time for a change.
>
> The patches are pretty self explanitory and all contain detailed long
> logs .. but the summary is:
>
> [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
> [PATCH 2/5] guilt: update to latest git version
> [PATCH 3/5] linux-libc-headers: update to v3.10
One of the changes in 3.10 seems to have introduced a conflicting
definition of ptrace_peeksiginfo_args in linux/ptrace.h
> In file included from ptrace.h:22:0,
> | from ptrace05.c:38:
> | /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8: error: redefinition of 'struct ptrace_peeksiginfo_args'
> | struct ptrace_peeksiginfo_args {
> | ^
> | In file included from ptrace.h:9:0,
> | from ptrace05.c:38:
> | /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8: note: originally defined here
> | struct ptrace_peeksiginfo_args
> | ^
This affects ltp, valgrind and strace.
Please check the autobuilder as I am building with this change set and
expect these failures.
Sau!
Sau!
> [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
> [PATCH 5/5] linux-yocto: introduce v3.10
>
> ** There is one pending activity. As part of thsi update to 3.10, we want
> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
> routerstationpro BSP is still using it as its preferred version. I'm
> a one man show on this update, and I wasn't able to get the 100+ patches
> ported to 3.10 AND get this update out before the M4 cutoff.
>
> ** I'm still attempting to udpate all the reference boards, and
> once done, I'll send a follow up patch.
>
> ** Please test, I've done my best, but things can slip through. We'll
> work issues in the stabilization period.
>
> Cheers,
>
> Bruce
>
>
> The following changes since commit 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>
> bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40 +0100)
>
> are available in the git repository at:
>
> git://git.pokylinux.org/poky-contrib zedd/kernel
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Bruce Ashfield (5):
> kern-tools: usability, bug fixes and no guilt
> guilt: update to latest git version
> linux-libc-headers: update to v3.10
> gst-plugins-good: fix 3.10 libc-headers build failure
> linux-yocto: introduce v3.10
>
> meta/classes/kernel-yocto.bbclass | 2 +
> meta/conf/distro/include/tcmode-default.inc | 2 +-
> .../guilt/files/guilt-import-commit.patch | 96 ------
> meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
> meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
> .../guilt/files/guilt-push-no-series.patch | 29 --
> meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
> .../guilt/files/guilt-set-git_exec_path.patch | 29 --
> ...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
> meta/recipes-devtools/guilt/files/guilt.patch | 319 --------------------
> .../guilt/files/improve_auto_header_gen.patch | 71 -----
> .../files/make_git_commands_conditional.patch | 48 ---
> .../guilt/files/optional_head_check.patch | 60 ----
> .../guilt/files/uninstall_force.patch | 14 -
> .../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
> .../kern-tools/kern-tools-native_git.bb | 6 +-
> .../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
> .../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
> ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
> .../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
> 23 files changed, 150 insertions(+), 861 deletions(-)
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-import-commit.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-init.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/optional_head_check.patch
> delete mode 100644 meta/recipes-devtools/guilt/files/uninstall_force.patch
> rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb => guilt-native_git.bb} (45%)
> create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
> delete mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
> create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
> create mode 100644 meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2013-08-24 6:33 ` Saul Wold
@ 2013-08-24 13:34 ` Bruce Ashfield
2013-08-24 13:45 ` Bruce Ashfield
0 siblings, 1 reply; 61+ messages in thread
From: Bruce Ashfield @ 2013-08-24 13:34 UTC (permalink / raw)
To: Saul Wold; +Cc: openembedded-core
On 13-08-24 2:33 AM, Saul Wold wrote:
> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>> Richard/Saul,
>>
>> Here's my consolidated set of changes that represent the biggest chunk
>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>> mark on). I've built and booted core-image-sato for all the oe-core
>> qemu machines.
>>
>> 3.10 also the latest LTSI and will be updated with that content when it
>> becomes available.
>>
>> Other features of the 3.10 kernel include:
>>
>> - refreshed -rt support
>> - refreshed yaffs2, aufs3
>> - cryptodev
>> - bfs, edf, and OCF staged features
>> - scrubbed and updated meta data for v3.10
>> - improved tools support for meta data updates and queue maintenance
>> - patch carry forward from all previous linux-yocto kernels and
>> configuration.
>>
>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>> shiny tree.
>>
>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>> gst-plugins-good
>> to adapt to a changed #define in the exported headers.
>>
>> Other parts of this update include an uprev of guilt, and in fact, a
>> restoration of "normal" guil operations, since the kernel tree is now
>> manipulated and maintained via a smaller, more contained script. This
>> was necessary for both usability reasons and the fact that all of guilts
>> protections were being removed for the kernel's use .. which makes you
>> ask the quesetion "why use it". It was time for a change.
>>
>> The patches are pretty self explanitory and all contain detailed long
>> logs .. but the summary is:
>>
>> [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>> [PATCH 2/5] guilt: update to latest git version
>> [PATCH 3/5] linux-libc-headers: update to v3.10
> One of the changes in 3.10 seems to have introduced a conflicting
> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>
>> In file included from ptrace.h:22:0,
>> | from ptrace05.c:38:
>> |
>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>> | struct ptrace_peeksiginfo_args {
>> | ^
>> | In file included from ptrace.h:9:0,
>> | from ptrace05.c:38:
>> |
>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>> note: originally defined here
>> | struct ptrace_peeksiginfo_args
>> | ^
>
> This affects ltp, valgrind and strace.
>
> Please check the autobuilder as I am building with this change set and
> expect these failures.
I'm unfortunately off for the weekend and won't have cycles to look into
any failures until Monday.
So if you want to leave the old headers in place, that's an option.
I fixed the one issue that I saw with Sato .. but I am after all one
person and can't possibly build and boot all the qemu boards with
all image combinations! This is after all, where I'd expect other
people to help out and fix build issues.
Cheers,
Bruce
>
> Sau!
>
> Sau!
>
>> [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>> [PATCH 5/5] linux-yocto: introduce v3.10
>>
>> ** There is one pending activity. As part of thsi update to 3.10, we want
>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>> routerstationpro BSP is still using it as its preferred version. I'm
>> a one man show on this update, and I wasn't able to get the 100+ patches
>> ported to 3.10 AND get this update out before the M4 cutoff.
>>
>> ** I'm still attempting to udpate all the reference boards, and
>> once done, I'll send a follow up patch.
>>
>> ** Please test, I've done my best, but things can slip through. We'll
>> work issues in the stabilization period.
>>
>> Cheers,
>>
>> Bruce
>>
>>
>> The following changes since commit
>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>
>> bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40 +0100)
>>
>> are available in the git repository at:
>>
>> git://git.pokylinux.org/poky-contrib zedd/kernel
>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>>
>> Bruce Ashfield (5):
>> kern-tools: usability, bug fixes and no guilt
>> guilt: update to latest git version
>> linux-libc-headers: update to v3.10
>> gst-plugins-good: fix 3.10 libc-headers build failure
>> linux-yocto: introduce v3.10
>>
>> meta/classes/kernel-yocto.bbclass | 2 +
>> meta/conf/distro/include/tcmode-default.inc | 2 +-
>> .../guilt/files/guilt-import-commit.patch | 96 ------
>> meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
>> meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
>> .../guilt/files/guilt-push-no-series.patch | 29 --
>> meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
>> .../guilt/files/guilt-set-git_exec_path.patch | 29 --
>> ...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
>> meta/recipes-devtools/guilt/files/guilt.patch | 319
>> --------------------
>> .../guilt/files/improve_auto_header_gen.patch | 71 -----
>> .../files/make_git_commands_conditional.patch | 48 ---
>> .../guilt/files/optional_head_check.patch | 60 ----
>> .../guilt/files/uninstall_force.patch | 14 -
>> .../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
>> .../kern-tools/kern-tools-native_git.bb | 6 +-
>> .../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
>> .../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
>> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
>> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
>> ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
>> .../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
>> 23 files changed, 150 insertions(+), 861 deletions(-)
>> delete mode 100644
>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-init.patch
>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>> delete mode 100644
>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push.patch
>> delete mode 100644
>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>> delete mode 100644
>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>
>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>> delete mode 100644
>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>> delete mode 100644
>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>> delete mode 100644
>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>> delete mode 100644
>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>> rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>> guilt-native_git.bb} (45%)
>> create mode 100644
>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>> delete mode 100644
>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>> create mode 100644
>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>
>>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 5/5] linux-yocto: introduce v3.10
2013-08-24 0:57 ` Jonathan Liu
@ 2013-08-24 13:36 ` Bruce Ashfield
0 siblings, 0 replies; 61+ messages in thread
From: Bruce Ashfield @ 2013-08-24 13:36 UTC (permalink / raw)
To: Jonathan Liu; +Cc: openembedded-core
On 13-08-23 8:57 PM, Jonathan Liu wrote:
> On 24/08/2013 4:08 AM, Bruce Ashfield wrote:
>> Introduce the 3.10 kernel. This is based on the 3.10.9 upstream kernel
>> and replaces the 3.8 recipes, which will be removed once all reference
>> boards have been updated.
>>
>> 3.10 also the latest LTSI and will be updated with that content when it
>> becomes available.
>>
>> Other features of the 3.10 kernel include:
>>
>> - refreshed -rt support
>> - refreshed yaffs2, aufs3
>> - cryptodev
>> - bfs, edf, and OCF staged features
>> - scrubbed and updated meta data for v3.10
>> - improved tools support for meta data updates and queue maintenance
>> - patch carry forward from all previous linux-yocto kernels and
>> configuration.
>>
>> This kernel has been built and boot tested on all qemu machines and
>> architectures.
>>
>> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
>> ---
>> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30
>> ++++++++++++++++++++
>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25
>> ++++++++++++++++
>> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30
>> ++++++++++++++++++++
>> 3 files changed, 85 insertions(+)
>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>>
>> diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>> b/meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>> new file mode 100644
>> index 0000000..4139be8
>> --- /dev/null
>> +++ b/meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>> @@ -0,0 +1,30 @@
>> +require recipes-kernel/linux/linux-yocto.inc
>> +
>> +KBRANCH = "standard/preempt-rt/base"
>> +KBRANCH_qemuppc = "standard/preempt-rt/qemuppc"
>> +
>> +SRCREV_machine ?= "77c5842818867366c3d08ca1dec19dc43aee0e91"
>> +SRCREV_machine_qemuppc ?= "7be83bc1124d2a2c75f99df94baaf718659722ea"
>> +SRCREV_meta ?= "1b9b113837f353fd94148beb6bd00a3b7b35d01d"
>> +
>> +SRC_URI =
>> "git://git.yoctoproject.org/linux-yocto-3.10.git;protocol=git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta"
>>
>> +
>> +LINUX_VERSION ?= "3.10.9"
>> +
>> +PV = "${LINUX_VERSION}+git${SRCPV}"
>> +
>> +KMETA = "meta"
>> +
>> +LINUX_KERNEL_TYPE = "preempt-rt"
>> +
>> +# Omit broken machines from COMPATIBLE_MACHINE
>> +# qemuppc hangs at boot
>> +# qemumips panics at boot
>> +COMPATIBLE_MACHINE = "(qemux86|qemux86-64|qemuarm)"
> I see COMPATIBLE_MACHINE has been carried over from the 3.4 and 3.8
> linux-rt recipes. Is linux-rt still broken on qemuppc and qemumips?
It is still the case, for the most part. -rt works fine on both ppc and
mips, just not in qemu.
The first port of any new kernel, I carry support over exactly as it is.
Only changing the kernel + headers, stabilize the existing support and
then look at adding new functionality and boards. That's the only way to
reasonably control the changes.
Cheers,
Bruce
>
>> +
>> +# Functionality flags
>> +KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc
>> features/taskstats/taskstats.scc"
>> +KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
>> +KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
>> +KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc"
>> +KERNEL_FEATURES_append = " ${@bb.utils.contains("TUNE_FEATURES",
>> "mx32", " cfg/x32.scc", "" ,d)}"
>> diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>> b/meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>> new file mode 100644
>> index 0000000..1c2ad37
>> --- /dev/null
>> +++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>> @@ -0,0 +1,25 @@
>> +require recipes-kernel/linux/linux-yocto.inc
>> +
>> +# We need lzma (as CONFIG_KERNEL_LZMA=y)
>> +DEPENDS += "xz-native"
>> +
>> +KBRANCH_DEFAULT = "standard/tiny/base"
>> +KBRANCH = "${KBRANCH_DEFAULT}"
>> +LINUX_KERNEL_TYPE = "tiny"
>> +KCONFIG_MODE = "--allnoconfig"
>> +
>> +LINUX_VERSION ?= "3.10.9"
>> +
>> +KMETA = "meta"
>> +
>> +SRCREV_machine ?= "6c1528b2b78d1ec7e75bb7a9880074ec35aa1aa0"
>> +SRCREV_meta ?= "1b9b113837f353fd94148beb6bd00a3b7b35d01d"
>> +
>> +PV = "${LINUX_VERSION}+git${SRCPV}"
>> +
>> +SRC_URI =
>> "git://git.yoctoproject.org/linux-yocto-3.10.git;protocol=git;bareclone=1;branch=${KBRANCH},meta;name=machine,meta"
>>
>> +
>> +COMPATIBLE_MACHINE = "(qemux86)"
>> +
>> +# Functionality flags
>> +KERNEL_FEATURES = ""
>> diff --git a/meta/recipes-kernel/linux/linux-yocto_3.10.bb
>> b/meta/recipes-kernel/linux/linux-yocto_3.10.bb
>> new file mode 100644
>> index 0000000..ea6ad2a
>> --- /dev/null
>> +++ b/meta/recipes-kernel/linux/linux-yocto_3.10.bb
>> @@ -0,0 +1,30 @@
>> +require recipes-kernel/linux/linux-yocto.inc
>> +
>> +KBRANCH_DEFAULT = "standard/base"
>> +KBRANCH = "${KBRANCH_DEFAULT}"
>> +
>> +SRCREV_machine_qemuarm ?= "8675d3d0a3c17135f70ef474d5c362397c02e62a"
>> +SRCREV_machine_qemumips ?= "992b743b905edd21d3a4a27c92b5c6a9e44d7d73"
>> +SRCREV_machine_qemuppc ?= "09388c3572e26c78b34554e46e077f12be7b2401"
>> +SRCREV_machine_qemux86 ?= "6c1528b2b78d1ec7e75bb7a9880074ec35aa1aa0"
>> +SRCREV_machine_qemux86-64 ?= "6c1528b2b78d1ec7e75bb7a9880074ec35aa1aa0"
>> +SRCREV_machine_qemumips64 ?= "203679cb23c752fdcbc0180a55a81728d7462561"
>> +SRCREV_machine ?= "6c1528b2b78d1ec7e75bb7a9880074ec35aa1aa0"
>> +SRCREV_meta ?= "1b9b113837f353fd94148beb6bd00a3b7b35d01d"
>> +
>> +SRC_URI =
>> "git://git.yoctoproject.org/linux-yocto-3.10.git;protocol=git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
>>
>> +
>> +LINUX_VERSION ?= "3.10.9"
>> +
>> +PV = "${LINUX_VERSION}+git${SRCPV}"
>> +
>> +KMETA = "meta"
>> +
>> +COMPATIBLE_MACHINE =
>> "qemuarm|qemux86|qemuppc|qemumips|qemumips64|qemux86-64"
>> +
>> +# Functionality flags
>> +KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc"
>> +KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
>> +KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
>> +KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc"
>> +KERNEL_FEATURES_append = " ${@bb.utils.contains("TUNE_FEATURES",
>> "mx32", " cfg/x32.scc", "" ,d)}"
> Regards,
> Jonathan
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2013-08-24 13:34 ` Bruce Ashfield
@ 2013-08-24 13:45 ` Bruce Ashfield
2013-08-24 13:50 ` Saul Wold
0 siblings, 1 reply; 61+ messages in thread
From: Bruce Ashfield @ 2013-08-24 13:45 UTC (permalink / raw)
To: Saul Wold; +Cc: openembedded-core
On 13-08-24 9:34 AM, Bruce Ashfield wrote:
> On 13-08-24 2:33 AM, Saul Wold wrote:
>> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>>> Richard/Saul,
>>>
>>> Here's my consolidated set of changes that represent the biggest chunk
>>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>>> mark on). I've built and booted core-image-sato for all the oe-core
>>> qemu machines.
>>>
>>> 3.10 also the latest LTSI and will be updated with that content when it
>>> becomes available.
>>>
>>> Other features of the 3.10 kernel include:
>>>
>>> - refreshed -rt support
>>> - refreshed yaffs2, aufs3
>>> - cryptodev
>>> - bfs, edf, and OCF staged features
>>> - scrubbed and updated meta data for v3.10
>>> - improved tools support for meta data updates and queue maintenance
>>> - patch carry forward from all previous linux-yocto kernels and
>>> configuration.
>>>
>>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>>> shiny tree.
>>>
>>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>>> gst-plugins-good
>>> to adapt to a changed #define in the exported headers.
>>>
>>> Other parts of this update include an uprev of guilt, and in fact, a
>>> restoration of "normal" guil operations, since the kernel tree is now
>>> manipulated and maintained via a smaller, more contained script. This
>>> was necessary for both usability reasons and the fact that all of guilts
>>> protections were being removed for the kernel's use .. which makes you
>>> ask the quesetion "why use it". It was time for a change.
>>>
>>> The patches are pretty self explanitory and all contain detailed long
>>> logs .. but the summary is:
>>>
>>> [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>>> [PATCH 2/5] guilt: update to latest git version
>>> [PATCH 3/5] linux-libc-headers: update to v3.10
>> One of the changes in 3.10 seems to have introduced a conflicting
>> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>>
>>> In file included from ptrace.h:22:0,
>>> | from ptrace05.c:38:
>>> |
>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>>>
>>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>>> | struct ptrace_peeksiginfo_args {
>>> | ^
>>> | In file included from ptrace.h:9:0,
>>> | from ptrace05.c:38:
>>> |
>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>>>
>>> note: originally defined here
>>> | struct ptrace_peeksiginfo_args
>>> | ^
>>
>> This affects ltp, valgrind and strace.
>>
>> Please check the autobuilder as I am building with this change set and
>> expect these failures.
>
> I'm unfortunately off for the weekend and won't have cycles to look into
> any failures until Monday.
As it turns out, I may have some time to work on this tonight, since I
have to delete the 3.8 yocto recipe and get that patch out.
So I've launched a LSB build in the background and will check on it
later.
If anyone else does get a fix for this, make sure to cc' me on any
changes, so I won't spend time trying to fix it a second time! :)
Bruce
>
> So if you want to leave the old headers in place, that's an option.
>
> I fixed the one issue that I saw with Sato .. but I am after all one
> person and can't possibly build and boot all the qemu boards with
> all image combinations! This is after all, where I'd expect other
> people to help out and fix build issues.
>
> Cheers,
>
> Bruce
>
>>
>> Sau!
>>
>> Sau!
>>
>>> [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>>> [PATCH 5/5] linux-yocto: introduce v3.10
>>>
>>> ** There is one pending activity. As part of thsi update to 3.10, we
>>> want
>>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>>> routerstationpro BSP is still using it as its preferred version. I'm
>>> a one man show on this update, and I wasn't able to get the 100+ patches
>>> ported to 3.10 AND get this update out before the M4 cutoff.
>>>
>>> ** I'm still attempting to udpate all the reference boards, and
>>> once done, I'll send a follow up patch.
>>>
>>> ** Please test, I've done my best, but things can slip through. We'll
>>> work issues in the stabilization period.
>>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>
>>> The following changes since commit
>>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>>
>>> bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40
>>> +0100)
>>>
>>> are available in the git repository at:
>>>
>>> git://git.pokylinux.org/poky-contrib zedd/kernel
>>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>>>
>>> Bruce Ashfield (5):
>>> kern-tools: usability, bug fixes and no guilt
>>> guilt: update to latest git version
>>> linux-libc-headers: update to v3.10
>>> gst-plugins-good: fix 3.10 libc-headers build failure
>>> linux-yocto: introduce v3.10
>>>
>>> meta/classes/kernel-yocto.bbclass | 2 +
>>> meta/conf/distro/include/tcmode-default.inc | 2 +-
>>> .../guilt/files/guilt-import-commit.patch | 96 ------
>>> meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
>>> meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
>>> .../guilt/files/guilt-push-no-series.patch | 29 --
>>> meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
>>> .../guilt/files/guilt-set-git_exec_path.patch | 29 --
>>> ...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
>>> meta/recipes-devtools/guilt/files/guilt.patch | 319
>>> --------------------
>>> .../guilt/files/improve_auto_header_gen.patch | 71 -----
>>> .../files/make_git_commands_conditional.patch | 48 ---
>>> .../guilt/files/optional_head_check.patch | 60 ----
>>> .../guilt/files/uninstall_force.patch | 14 -
>>> .../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
>>> .../kern-tools/kern-tools-native_git.bb | 6 +-
>>> .../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
>>> .../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
>>> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
>>> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
>>> ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
>>> .../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
>>> 23 files changed, 150 insertions(+), 861 deletions(-)
>>> delete mode 100644
>>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-init.patch
>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>>> delete mode 100644
>>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push.patch
>>> delete mode 100644
>>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>>> delete mode 100644
>>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>>
>>>
>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>>> delete mode 100644
>>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>>> delete mode 100644
>>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>>> delete mode 100644
>>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>>> delete mode 100644
>>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>>> rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>>> guilt-native_git.bb} (45%)
>>> create mode 100644
>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>>> delete mode 100644
>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>>> create mode 100644
>>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>>
>>>
>>>
>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2013-08-24 13:45 ` Bruce Ashfield
@ 2013-08-24 13:50 ` Saul Wold
2013-08-24 13:53 ` Bruce Ashfield
` (3 more replies)
0 siblings, 4 replies; 61+ messages in thread
From: Saul Wold @ 2013-08-24 13:50 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On 08/24/2013 06:45 AM, Bruce Ashfield wrote:
> On 13-08-24 9:34 AM, Bruce Ashfield wrote:
>> On 13-08-24 2:33 AM, Saul Wold wrote:
>>> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>>>> Richard/Saul,
>>>>
>>>> Here's my consolidated set of changes that represent the biggest chunk
>>>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>>>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>>>> mark on). I've built and booted core-image-sato for all the oe-core
>>>> qemu machines.
>>>>
>>>> 3.10 also the latest LTSI and will be updated with that content when it
>>>> becomes available.
>>>>
>>>> Other features of the 3.10 kernel include:
>>>>
>>>> - refreshed -rt support
>>>> - refreshed yaffs2, aufs3
>>>> - cryptodev
>>>> - bfs, edf, and OCF staged features
>>>> - scrubbed and updated meta data for v3.10
>>>> - improved tools support for meta data updates and queue maintenance
>>>> - patch carry forward from all previous linux-yocto kernels and
>>>> configuration.
>>>>
>>>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>>>> shiny tree.
>>>>
>>>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>>>> gst-plugins-good
>>>> to adapt to a changed #define in the exported headers.
>>>>
>>>> Other parts of this update include an uprev of guilt, and in fact, a
>>>> restoration of "normal" guil operations, since the kernel tree is now
>>>> manipulated and maintained via a smaller, more contained script. This
>>>> was necessary for both usability reasons and the fact that all of
>>>> guilts
>>>> protections were being removed for the kernel's use .. which makes you
>>>> ask the quesetion "why use it". It was time for a change.
>>>>
>>>> The patches are pretty self explanitory and all contain detailed long
>>>> logs .. but the summary is:
>>>>
>>>> [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>>>> [PATCH 2/5] guilt: update to latest git version
>>>> [PATCH 3/5] linux-libc-headers: update to v3.10
>>> One of the changes in 3.10 seems to have introduced a conflicting
>>> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>>>
>>>> In file included from ptrace.h:22:0,
>>>> | from ptrace05.c:38:
>>>> |
>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>>>>
>>>>
>>>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>>>> | struct ptrace_peeksiginfo_args {
>>>> | ^
>>>> | In file included from ptrace.h:9:0,
>>>> | from ptrace05.c:38:
>>>> |
>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>>>>
>>>>
>>>> note: originally defined here
>>>> | struct ptrace_peeksiginfo_args
>>>> | ^
>>>
>>> This affects ltp, valgrind and strace.
>>>
>>> Please check the autobuilder as I am building with this change set and
>>> expect these failures.
>>
>> I'm unfortunately off for the weekend and won't have cycles to look into
>> any failures until Monday.
>
> As it turns out, I may have some time to work on this tonight, since I
> have to delete the 3.8 yocto recipe and get that patch out.
>
> So I've launched a LSB build in the background and will check on it
> later.
>
Just FYI, it might not show up in an LSB build, since those tools
valgrind, ltp and strace are more Dev tools, so a world build would be
better.
Also, not sure why but ARM failed to patch 3.8 kernel overnight on the
AB. (lots of red).
I just restarted AB with out the 3.10 headers.
Sau!
> If anyone else does get a fix for this, make sure to cc' me on any
> changes, so I won't spend time trying to fix it a second time! :)
>
> Bruce
>
>>
>> So if you want to leave the old headers in place, that's an option.
>>
>> I fixed the one issue that I saw with Sato .. but I am after all one
>> person and can't possibly build and boot all the qemu boards with
>> all image combinations! This is after all, where I'd expect other
>> people to help out and fix build issues.
>>
>> Cheers,
>>
>> Bruce
>>
>>>
>>> Sau!
>>>
>>> Sau!
>>>
>>>> [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>>>> [PATCH 5/5] linux-yocto: introduce v3.10
>>>>
>>>> ** There is one pending activity. As part of thsi update to 3.10, we
>>>> want
>>>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>>>> routerstationpro BSP is still using it as its preferred version. I'm
>>>> a one man show on this update, and I wasn't able to get the 100+
>>>> patches
>>>> ported to 3.10 AND get this update out before the M4 cutoff.
>>>>
>>>> ** I'm still attempting to udpate all the reference boards, and
>>>> once done, I'll send a follow up patch.
>>>>
>>>> ** Please test, I've done my best, but things can slip through. We'll
>>>> work issues in the stabilization period.
>>>>
>>>> Cheers,
>>>>
>>>> Bruce
>>>>
>>>>
>>>> The following changes since commit
>>>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>>>
>>>> bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40
>>>> +0100)
>>>>
>>>> are available in the git repository at:
>>>>
>>>> git://git.pokylinux.org/poky-contrib zedd/kernel
>>>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>>>>
>>>> Bruce Ashfield (5):
>>>> kern-tools: usability, bug fixes and no guilt
>>>> guilt: update to latest git version
>>>> linux-libc-headers: update to v3.10
>>>> gst-plugins-good: fix 3.10 libc-headers build failure
>>>> linux-yocto: introduce v3.10
>>>>
>>>> meta/classes/kernel-yocto.bbclass | 2 +
>>>> meta/conf/distro/include/tcmode-default.inc | 2 +-
>>>> .../guilt/files/guilt-import-commit.patch | 96 ------
>>>> meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
>>>> meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
>>>> .../guilt/files/guilt-push-no-series.patch | 29 --
>>>> meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
>>>> .../guilt/files/guilt-set-git_exec_path.patch | 29 --
>>>> ...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
>>>> meta/recipes-devtools/guilt/files/guilt.patch | 319
>>>> --------------------
>>>> .../guilt/files/improve_auto_header_gen.patch | 71 -----
>>>> .../files/make_git_commands_conditional.patch | 48 ---
>>>> .../guilt/files/optional_head_check.patch | 60 ----
>>>> .../guilt/files/uninstall_force.patch | 14 -
>>>> .../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
>>>> .../kern-tools/kern-tools-native_git.bb | 6 +-
>>>> .../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
>>>> .../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
>>>> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
>>>> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
>>>> ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
>>>> .../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
>>>> 23 files changed, 150 insertions(+), 861 deletions(-)
>>>> delete mode 100644
>>>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-init.patch
>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>>>> delete mode 100644
>>>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-push.patch
>>>> delete mode 100644
>>>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>>>> delete mode 100644
>>>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>>>
>>>>
>>>>
>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>>>> delete mode 100644
>>>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>>>> delete mode 100644
>>>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>>>> delete mode 100644
>>>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>>>> delete mode 100644
>>>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>>>> rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>>>> guilt-native_git.bb} (45%)
>>>> create mode 100644
>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>>>> delete mode 100644
>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>>>> create mode 100644
>>>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>>>
>>>>
>>>>
>>>>
>>
>
>
>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2013-08-24 13:50 ` Saul Wold
@ 2013-08-24 13:53 ` Bruce Ashfield
2013-08-24 14:47 ` Bruce Ashfield
` (2 subsequent siblings)
3 siblings, 0 replies; 61+ messages in thread
From: Bruce Ashfield @ 2013-08-24 13:53 UTC (permalink / raw)
To: Saul Wold; +Cc: openembedded-core
On 13-08-24 9:50 AM, Saul Wold wrote:
> On 08/24/2013 06:45 AM, Bruce Ashfield wrote:
>> On 13-08-24 9:34 AM, Bruce Ashfield wrote:
>>> On 13-08-24 2:33 AM, Saul Wold wrote:
>>>> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>>>>> Richard/Saul,
>>>>>
>>>>> Here's my consolidated set of changes that represent the biggest chunk
>>>>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>>>>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>>>>> mark on). I've built and booted core-image-sato for all the oe-core
>>>>> qemu machines.
>>>>>
>>>>> 3.10 also the latest LTSI and will be updated with that content
>>>>> when it
>>>>> becomes available.
>>>>>
>>>>> Other features of the 3.10 kernel include:
>>>>>
>>>>> - refreshed -rt support
>>>>> - refreshed yaffs2, aufs3
>>>>> - cryptodev
>>>>> - bfs, edf, and OCF staged features
>>>>> - scrubbed and updated meta data for v3.10
>>>>> - improved tools support for meta data updates and queue
>>>>> maintenance
>>>>> - patch carry forward from all previous linux-yocto kernels and
>>>>> configuration.
>>>>>
>>>>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>>>>> shiny tree.
>>>>>
>>>>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>>>>> gst-plugins-good
>>>>> to adapt to a changed #define in the exported headers.
>>>>>
>>>>> Other parts of this update include an uprev of guilt, and in fact, a
>>>>> restoration of "normal" guil operations, since the kernel tree is now
>>>>> manipulated and maintained via a smaller, more contained script. This
>>>>> was necessary for both usability reasons and the fact that all of
>>>>> guilts
>>>>> protections were being removed for the kernel's use .. which makes you
>>>>> ask the quesetion "why use it". It was time for a change.
>>>>>
>>>>> The patches are pretty self explanitory and all contain detailed long
>>>>> logs .. but the summary is:
>>>>>
>>>>> [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>>>>> [PATCH 2/5] guilt: update to latest git version
>>>>> [PATCH 3/5] linux-libc-headers: update to v3.10
>>>> One of the changes in 3.10 seems to have introduced a conflicting
>>>> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>>>>
>>>>> In file included from ptrace.h:22:0,
>>>>> | from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>>>>>
>>>>>
>>>>>
>>>>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>>>>> | struct ptrace_peeksiginfo_args {
>>>>> | ^
>>>>> | In file included from ptrace.h:9:0,
>>>>> | from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>>>>>
>>>>>
>>>>>
>>>>> note: originally defined here
>>>>> | struct ptrace_peeksiginfo_args
>>>>> | ^
>>>>
>>>> This affects ltp, valgrind and strace.
>>>>
>>>> Please check the autobuilder as I am building with this change set and
>>>> expect these failures.
>>>
>>> I'm unfortunately off for the weekend and won't have cycles to look into
>>> any failures until Monday.
>>
>> As it turns out, I may have some time to work on this tonight, since I
>> have to delete the 3.8 yocto recipe and get that patch out.
>>
>> So I've launched a LSB build in the background and will check on it
>> later.
>>
> Just FYI, it might not show up in an LSB build, since those tools
> valgrind, ltp and strace are more Dev tools, so a world build would be
> better.
Ah ok. I'll explicitly add dependencies on them here and restart
my sato build.
I'm a bit surprised that it failed, since user apis are a huge no-no
to change.
>
> Also, not sure why but ARM failed to patch 3.8 kernel overnight on the
> AB. (lots of red).
probably because I didn't look at 3.8 ... since my plan was to delete
it!
I'll follow up with a fix for that tonight, if I can see the failure
here. Always fun!! :)
Leave that one with me. Do you have a link to the failure ?
Bruce
>
> I just restarted AB with out the 3.10 headers.
>
> Sau!
>
>> If anyone else does get a fix for this, make sure to cc' me on any
>> changes, so I won't spend time trying to fix it a second time! :)
>>
>> Bruce
>>
>>>
>>> So if you want to leave the old headers in place, that's an option.
>>>
>>> I fixed the one issue that I saw with Sato .. but I am after all one
>>> person and can't possibly build and boot all the qemu boards with
>>> all image combinations! This is after all, where I'd expect other
>>> people to help out and fix build issues.
>>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>>
>>>> Sau!
>>>>
>>>> Sau!
>>>>
>>>>> [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>>>>> [PATCH 5/5] linux-yocto: introduce v3.10
>>>>>
>>>>> ** There is one pending activity. As part of thsi update to 3.10, we
>>>>> want
>>>>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>>>>> routerstationpro BSP is still using it as its preferred version. I'm
>>>>> a one man show on this update, and I wasn't able to get the 100+
>>>>> patches
>>>>> ported to 3.10 AND get this update out before the M4 cutoff.
>>>>>
>>>>> ** I'm still attempting to udpate all the reference boards, and
>>>>> once done, I'll send a follow up patch.
>>>>>
>>>>> ** Please test, I've done my best, but things can slip through. We'll
>>>>> work issues in the stabilization period.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Bruce
>>>>>
>>>>>
>>>>> The following changes since commit
>>>>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>>>>
>>>>> bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40
>>>>> +0100)
>>>>>
>>>>> are available in the git repository at:
>>>>>
>>>>> git://git.pokylinux.org/poky-contrib zedd/kernel
>>>>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>>>>>
>>>>> Bruce Ashfield (5):
>>>>> kern-tools: usability, bug fixes and no guilt
>>>>> guilt: update to latest git version
>>>>> linux-libc-headers: update to v3.10
>>>>> gst-plugins-good: fix 3.10 libc-headers build failure
>>>>> linux-yocto: introduce v3.10
>>>>>
>>>>> meta/classes/kernel-yocto.bbclass | 2 +
>>>>> meta/conf/distro/include/tcmode-default.inc | 2 +-
>>>>> .../guilt/files/guilt-import-commit.patch | 96 ------
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
>>>>> meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
>>>>> .../guilt/files/guilt-push-no-series.patch | 29 --
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
>>>>> .../guilt/files/guilt-set-git_exec_path.patch | 29 --
>>>>> ...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
>>>>> meta/recipes-devtools/guilt/files/guilt.patch | 319
>>>>> --------------------
>>>>> .../guilt/files/improve_auto_header_gen.patch | 71 -----
>>>>> .../files/make_git_commands_conditional.patch | 48 ---
>>>>> .../guilt/files/optional_head_check.patch | 60 ----
>>>>> .../guilt/files/uninstall_force.patch | 14 -
>>>>> .../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
>>>>> .../kern-tools/kern-tools-native_git.bb | 6 +-
>>>>> .../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
>>>>> .../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
>>>>> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
>>>>> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
>>>>> ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
>>>>> .../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
>>>>> 23 files changed, 150 insertions(+), 861 deletions(-)
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch
>>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>>>>> rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>>>>> guilt-native_git.bb} (45%)
>>>>> create mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>>>>> delete mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>>>>> create mode 100644
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>>>>> create mode 100644
>>>>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>
>>
>>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2013-08-24 13:50 ` Saul Wold
2013-08-24 13:53 ` Bruce Ashfield
@ 2013-08-24 14:47 ` Bruce Ashfield
2013-08-24 14:59 ` Bruce Ashfield
2013-08-24 16:05 ` Bruce Ashfield
3 siblings, 0 replies; 61+ messages in thread
From: Bruce Ashfield @ 2013-08-24 14:47 UTC (permalink / raw)
To: Saul Wold; +Cc: openembedded-core
On 13-08-24 9:50 AM, Saul Wold wrote:
> On 08/24/2013 06:45 AM, Bruce Ashfield wrote:
>> On 13-08-24 9:34 AM, Bruce Ashfield wrote:
>>> On 13-08-24 2:33 AM, Saul Wold wrote:
>>>> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>>>>> Richard/Saul,
>>>>>
>>>>> Here's my consolidated set of changes that represent the biggest chunk
>>>>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>>>>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>>>>> mark on). I've built and booted core-image-sato for all the oe-core
>>>>> qemu machines.
>>>>>
>>>>> 3.10 also the latest LTSI and will be updated with that content
>>>>> when it
>>>>> becomes available.
>>>>>
>>>>> Other features of the 3.10 kernel include:
>>>>>
>>>>> - refreshed -rt support
>>>>> - refreshed yaffs2, aufs3
>>>>> - cryptodev
>>>>> - bfs, edf, and OCF staged features
>>>>> - scrubbed and updated meta data for v3.10
>>>>> - improved tools support for meta data updates and queue
>>>>> maintenance
>>>>> - patch carry forward from all previous linux-yocto kernels and
>>>>> configuration.
>>>>>
>>>>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>>>>> shiny tree.
>>>>>
>>>>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>>>>> gst-plugins-good
>>>>> to adapt to a changed #define in the exported headers.
>>>>>
>>>>> Other parts of this update include an uprev of guilt, and in fact, a
>>>>> restoration of "normal" guil operations, since the kernel tree is now
>>>>> manipulated and maintained via a smaller, more contained script. This
>>>>> was necessary for both usability reasons and the fact that all of
>>>>> guilts
>>>>> protections were being removed for the kernel's use .. which makes you
>>>>> ask the quesetion "why use it". It was time for a change.
>>>>>
>>>>> The patches are pretty self explanitory and all contain detailed long
>>>>> logs .. but the summary is:
>>>>>
>>>>> [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>>>>> [PATCH 2/5] guilt: update to latest git version
>>>>> [PATCH 3/5] linux-libc-headers: update to v3.10
>>>> One of the changes in 3.10 seems to have introduced a conflicting
>>>> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>>>>
>>>>> In file included from ptrace.h:22:0,
>>>>> | from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>>>>>
>>>>>
>>>>>
>>>>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>>>>> | struct ptrace_peeksiginfo_args {
>>>>> | ^
>>>>> | In file included from ptrace.h:9:0,
>>>>> | from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>>>>>
>>>>>
>>>>>
>>>>> note: originally defined here
>>>>> | struct ptrace_peeksiginfo_args
>>>>> | ^
>>>>
>>>> This affects ltp, valgrind and strace.
>>>>
>>>> Please check the autobuilder as I am building with this change set and
>>>> expect these failures.
>>>
>>> I'm unfortunately off for the weekend and won't have cycles to look into
>>> any failures until Monday.
>>
>> As it turns out, I may have some time to work on this tonight, since I
>> have to delete the 3.8 yocto recipe and get that patch out.
>>
>> So I've launched a LSB build in the background and will check on it
>> later.
>>
> Just FYI, it might not show up in an LSB build, since those tools
> valgrind, ltp and strace are more Dev tools, so a world build would be
> better.
I reproduced the failure here via adding ptrace to my image install.
The kernel change happened in april, and the good news is that the
structure is still exactly the same size, with the same fields. So the
userspace ABI is unchanged.
I'll hunt down the conflict and adjust the packages, since that kernel
header change will be there to stay.
Has anyone checked to see if the upstream version of those packages have
already adapted to the change ? I'll do that tonight when I'm back, if
no one else has.
Cheers,
Bruce
>
> Also, not sure why but ARM failed to patch 3.8 kernel overnight on the
> AB. (lots of red).
>
> I just restarted AB with out the 3.10 headers.
>
> Sau!
>
>> If anyone else does get a fix for this, make sure to cc' me on any
>> changes, so I won't spend time trying to fix it a second time! :)
>>
>> Bruce
>>
>>>
>>> So if you want to leave the old headers in place, that's an option.
>>>
>>> I fixed the one issue that I saw with Sato .. but I am after all one
>>> person and can't possibly build and boot all the qemu boards with
>>> all image combinations! This is after all, where I'd expect other
>>> people to help out and fix build issues.
>>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>>
>>>> Sau!
>>>>
>>>> Sau!
>>>>
>>>>> [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>>>>> [PATCH 5/5] linux-yocto: introduce v3.10
>>>>>
>>>>> ** There is one pending activity. As part of thsi update to 3.10, we
>>>>> want
>>>>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>>>>> routerstationpro BSP is still using it as its preferred version. I'm
>>>>> a one man show on this update, and I wasn't able to get the 100+
>>>>> patches
>>>>> ported to 3.10 AND get this update out before the M4 cutoff.
>>>>>
>>>>> ** I'm still attempting to udpate all the reference boards, and
>>>>> once done, I'll send a follow up patch.
>>>>>
>>>>> ** Please test, I've done my best, but things can slip through. We'll
>>>>> work issues in the stabilization period.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Bruce
>>>>>
>>>>>
>>>>> The following changes since commit
>>>>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>>>>
>>>>> bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40
>>>>> +0100)
>>>>>
>>>>> are available in the git repository at:
>>>>>
>>>>> git://git.pokylinux.org/poky-contrib zedd/kernel
>>>>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>>>>>
>>>>> Bruce Ashfield (5):
>>>>> kern-tools: usability, bug fixes and no guilt
>>>>> guilt: update to latest git version
>>>>> linux-libc-headers: update to v3.10
>>>>> gst-plugins-good: fix 3.10 libc-headers build failure
>>>>> linux-yocto: introduce v3.10
>>>>>
>>>>> meta/classes/kernel-yocto.bbclass | 2 +
>>>>> meta/conf/distro/include/tcmode-default.inc | 2 +-
>>>>> .../guilt/files/guilt-import-commit.patch | 96 ------
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
>>>>> meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
>>>>> .../guilt/files/guilt-push-no-series.patch | 29 --
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
>>>>> .../guilt/files/guilt-set-git_exec_path.patch | 29 --
>>>>> ...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
>>>>> meta/recipes-devtools/guilt/files/guilt.patch | 319
>>>>> --------------------
>>>>> .../guilt/files/improve_auto_header_gen.patch | 71 -----
>>>>> .../files/make_git_commands_conditional.patch | 48 ---
>>>>> .../guilt/files/optional_head_check.patch | 60 ----
>>>>> .../guilt/files/uninstall_force.patch | 14 -
>>>>> .../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
>>>>> .../kern-tools/kern-tools-native_git.bb | 6 +-
>>>>> .../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
>>>>> .../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
>>>>> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
>>>>> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
>>>>> ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
>>>>> .../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
>>>>> 23 files changed, 150 insertions(+), 861 deletions(-)
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch
>>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>>>>> rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>>>>> guilt-native_git.bb} (45%)
>>>>> create mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>>>>> delete mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>>>>> create mode 100644
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>>>>> create mode 100644
>>>>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>
>>
>>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2013-08-24 13:50 ` Saul Wold
2013-08-24 13:53 ` Bruce Ashfield
2013-08-24 14:47 ` Bruce Ashfield
@ 2013-08-24 14:59 ` Bruce Ashfield
2013-08-24 16:05 ` Bruce Ashfield
3 siblings, 0 replies; 61+ messages in thread
From: Bruce Ashfield @ 2013-08-24 14:59 UTC (permalink / raw)
To: Saul Wold; +Cc: openembedded-core
On 13-08-24 9:50 AM, Saul Wold wrote:
> On 08/24/2013 06:45 AM, Bruce Ashfield wrote:
>> On 13-08-24 9:34 AM, Bruce Ashfield wrote:
>>> On 13-08-24 2:33 AM, Saul Wold wrote:
>>>> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>>>>> Richard/Saul,
>>>>>
>>>>> Here's my consolidated set of changes that represent the biggest chunk
>>>>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>>>>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>>>>> mark on). I've built and booted core-image-sato for all the oe-core
>>>>> qemu machines.
>>>>>
>>>>> 3.10 also the latest LTSI and will be updated with that content
>>>>> when it
>>>>> becomes available.
>>>>>
>>>>> Other features of the 3.10 kernel include:
>>>>>
>>>>> - refreshed -rt support
>>>>> - refreshed yaffs2, aufs3
>>>>> - cryptodev
>>>>> - bfs, edf, and OCF staged features
>>>>> - scrubbed and updated meta data for v3.10
>>>>> - improved tools support for meta data updates and queue
>>>>> maintenance
>>>>> - patch carry forward from all previous linux-yocto kernels and
>>>>> configuration.
>>>>>
>>>>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>>>>> shiny tree.
>>>>>
>>>>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>>>>> gst-plugins-good
>>>>> to adapt to a changed #define in the exported headers.
>>>>>
>>>>> Other parts of this update include an uprev of guilt, and in fact, a
>>>>> restoration of "normal" guil operations, since the kernel tree is now
>>>>> manipulated and maintained via a smaller, more contained script. This
>>>>> was necessary for both usability reasons and the fact that all of
>>>>> guilts
>>>>> protections were being removed for the kernel's use .. which makes you
>>>>> ask the quesetion "why use it". It was time for a change.
>>>>>
>>>>> The patches are pretty self explanitory and all contain detailed long
>>>>> logs .. but the summary is:
>>>>>
>>>>> [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>>>>> [PATCH 2/5] guilt: update to latest git version
>>>>> [PATCH 3/5] linux-libc-headers: update to v3.10
>>>> One of the changes in 3.10 seems to have introduced a conflicting
>>>> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>>>>
>>>>> In file included from ptrace.h:22:0,
>>>>> | from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>>>>>
>>>>>
>>>>>
>>>>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>>>>> | struct ptrace_peeksiginfo_args {
>>>>> | ^
>>>>> | In file included from ptrace.h:9:0,
>>>>> | from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>>>>>
>>>>>
>>>>>
>>>>> note: originally defined here
>>>>> | struct ptrace_peeksiginfo_args
>>>>> | ^
>>>>
>>>> This affects ltp, valgrind and strace.
>>>>
>>>> Please check the autobuilder as I am building with this change set and
>>>> expect these failures.
>>>
>>> I'm unfortunately off for the weekend and won't have cycles to look into
>>> any failures until Monday.
>>
>> As it turns out, I may have some time to work on this tonight, since I
>> have to delete the 3.8 yocto recipe and get that patch out.
>>
>> So I've launched a LSB build in the background and will check on it
>> later.
>>
> Just FYI, it might not show up in an LSB build, since those tools
> valgrind, ltp and strace are more Dev tools, so a world build would be
> better.
>
> Also, not sure why but ARM failed to patch 3.8 kernel overnight on the
> AB. (lots of red).
>
> I just restarted AB with out the 3.10 headers.
ok .. this time I'm REALLY going to step away for a few hours.
The mismatch is between the eglibc 2.18 sys/ptrace.h and the kernel's
definition of the structure. I wouldn't really call it a mismatch,
since they are both the same size and field types .. both simply
define it now.
I'm adding Khem: What's the right thing to do here?
I can obviously hack the kernel to remove the definition, but that make
the linux-yocto 3.10 the only kernel that will work against yocto 1.5's
eglibc for building any applications that use ptrace.h.
Falling back to the 3.8 headers will work, but again, we are avoiding
the problem and any end user that does bump to a newer set of libc-headers
will see the problem.
I'll wait for consensus on the approach and add a change if required
into my linux-yocto 3.8 removal patch tonight.
Bruce
>
> Sau!
>
>> If anyone else does get a fix for this, make sure to cc' me on any
>> changes, so I won't spend time trying to fix it a second time! :)
>>
>> Bruce
>>
>>>
>>> So if you want to leave the old headers in place, that's an option.
>>>
>>> I fixed the one issue that I saw with Sato .. but I am after all one
>>> person and can't possibly build and boot all the qemu boards with
>>> all image combinations! This is after all, where I'd expect other
>>> people to help out and fix build issues.
>>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>>
>>>> Sau!
>>>>
>>>> Sau!
>>>>
>>>>> [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>>>>> [PATCH 5/5] linux-yocto: introduce v3.10
>>>>>
>>>>> ** There is one pending activity. As part of thsi update to 3.10, we
>>>>> want
>>>>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>>>>> routerstationpro BSP is still using it as its preferred version. I'm
>>>>> a one man show on this update, and I wasn't able to get the 100+
>>>>> patches
>>>>> ported to 3.10 AND get this update out before the M4 cutoff.
>>>>>
>>>>> ** I'm still attempting to udpate all the reference boards, and
>>>>> once done, I'll send a follow up patch.
>>>>>
>>>>> ** Please test, I've done my best, but things can slip through. We'll
>>>>> work issues in the stabilization period.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Bruce
>>>>>
>>>>>
>>>>> The following changes since commit
>>>>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>>>>
>>>>> bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40
>>>>> +0100)
>>>>>
>>>>> are available in the git repository at:
>>>>>
>>>>> git://git.pokylinux.org/poky-contrib zedd/kernel
>>>>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>>>>>
>>>>> Bruce Ashfield (5):
>>>>> kern-tools: usability, bug fixes and no guilt
>>>>> guilt: update to latest git version
>>>>> linux-libc-headers: update to v3.10
>>>>> gst-plugins-good: fix 3.10 libc-headers build failure
>>>>> linux-yocto: introduce v3.10
>>>>>
>>>>> meta/classes/kernel-yocto.bbclass | 2 +
>>>>> meta/conf/distro/include/tcmode-default.inc | 2 +-
>>>>> .../guilt/files/guilt-import-commit.patch | 96 ------
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
>>>>> meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
>>>>> .../guilt/files/guilt-push-no-series.patch | 29 --
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
>>>>> .../guilt/files/guilt-set-git_exec_path.patch | 29 --
>>>>> ...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
>>>>> meta/recipes-devtools/guilt/files/guilt.patch | 319
>>>>> --------------------
>>>>> .../guilt/files/improve_auto_header_gen.patch | 71 -----
>>>>> .../files/make_git_commands_conditional.patch | 48 ---
>>>>> .../guilt/files/optional_head_check.patch | 60 ----
>>>>> .../guilt/files/uninstall_force.patch | 14 -
>>>>> .../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
>>>>> .../kern-tools/kern-tools-native_git.bb | 6 +-
>>>>> .../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
>>>>> .../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
>>>>> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
>>>>> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
>>>>> ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
>>>>> .../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
>>>>> 23 files changed, 150 insertions(+), 861 deletions(-)
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch
>>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>>>>> rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>>>>> guilt-native_git.bb} (45%)
>>>>> create mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>>>>> delete mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>>>>> create mode 100644
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>>>>> create mode 100644
>>>>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>
>>
>>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2013-08-24 13:50 ` Saul Wold
` (2 preceding siblings ...)
2013-08-24 14:59 ` Bruce Ashfield
@ 2013-08-24 16:05 ` Bruce Ashfield
3 siblings, 0 replies; 61+ messages in thread
From: Bruce Ashfield @ 2013-08-24 16:05 UTC (permalink / raw)
To: Saul Wold; +Cc: openembedded-core
On 13-08-24 9:50 AM, Saul Wold wrote:
> On 08/24/2013 06:45 AM, Bruce Ashfield wrote:
>> On 13-08-24 9:34 AM, Bruce Ashfield wrote:
>>> On 13-08-24 2:33 AM, Saul Wold wrote:
>>>> On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
>>>>> Richard/Saul,
>>>>>
>>>>> Here's my consolidated set of changes that represent the biggest chunk
>>>>> of work for the Yocto 1.5 release. The obvious change is that the 3.10
>>>>> kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
>>>>> mark on). I've built and booted core-image-sato for all the oe-core
>>>>> qemu machines.
>>>>>
>>>>> 3.10 also the latest LTSI and will be updated with that content
>>>>> when it
>>>>> becomes available.
>>>>>
>>>>> Other features of the 3.10 kernel include:
>>>>>
>>>>> - refreshed -rt support
>>>>> - refreshed yaffs2, aufs3
>>>>> - cryptodev
>>>>> - bfs, edf, and OCF staged features
>>>>> - scrubbed and updated meta data for v3.10
>>>>> - improved tools support for meta data updates and queue
>>>>> maintenance
>>>>> - patch carry forward from all previous linux-yocto kernels and
>>>>> configuration.
>>>>>
>>>>> I've also tested linux-yocto-rt and linux-yocto-tiny for the new,
>>>>> shiny tree.
>>>>>
>>>>> I've also bumped the linux-libc-headers to 3.10 and have fixed
>>>>> gst-plugins-good
>>>>> to adapt to a changed #define in the exported headers.
>>>>>
>>>>> Other parts of this update include an uprev of guilt, and in fact, a
>>>>> restoration of "normal" guil operations, since the kernel tree is now
>>>>> manipulated and maintained via a smaller, more contained script. This
>>>>> was necessary for both usability reasons and the fact that all of
>>>>> guilts
>>>>> protections were being removed for the kernel's use .. which makes you
>>>>> ask the quesetion "why use it". It was time for a change.
>>>>>
>>>>> The patches are pretty self explanitory and all contain detailed long
>>>>> logs .. but the summary is:
>>>>>
>>>>> [PATCH 1/5] kern-tools: usability, bug fixes and no guilt
>>>>> [PATCH 2/5] guilt: update to latest git version
>>>>> [PATCH 3/5] linux-libc-headers: update to v3.10
>>>> One of the changes in 3.10 seems to have introduced a conflicting
>>>> definition of ptrace_peeksiginfo_args in linux/ptrace.h
>>>>
>>>>> In file included from ptrace.h:22:0,
>>>>> | from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/linux/ptrace.h:58:8:
>>>>>
>>>>>
>>>>>
>>>>> error: redefinition of 'struct ptrace_peeksiginfo_args'
>>>>> | struct ptrace_peeksiginfo_args {
>>>>> | ^
>>>>> | In file included from ptrace.h:9:0,
>>>>> | from ptrace05.c:38:
>>>>> |
>>>>> /srv/ssd/sgw/builds/world/tmp/sysroots/qemux86-64/usr/include/sys/ptrace.h:191:8:
>>>>>
>>>>>
>>>>>
>>>>> note: originally defined here
>>>>> | struct ptrace_peeksiginfo_args
>>>>> | ^
>>>>
>>>> This affects ltp, valgrind and strace.
>>>>
>>>> Please check the autobuilder as I am building with this change set and
>>>> expect these failures.
>>>
>>> I'm unfortunately off for the weekend and won't have cycles to look into
>>> any failures until Monday.
>>
>> As it turns out, I may have some time to work on this tonight, since I
>> have to delete the 3.8 yocto recipe and get that patch out.
>>
>> So I've launched a LSB build in the background and will check on it
>> later.
>>
> Just FYI, it might not show up in an LSB build, since those tools
> valgrind, ltp and strace are more Dev tools, so a world build would be
> better.
>
> Also, not sure why but ARM failed to patch 3.8 kernel overnight on the
> AB. (lots of red).
FYI: I've fixed the ARM 3.8 build issue here, it'll be in my series
tonight .. regardless if I'm removing 3.8, it was worth fixing.
Cheers,
Bruce
>
> I just restarted AB with out the 3.10 headers.
>
> Sau!
>
>> If anyone else does get a fix for this, make sure to cc' me on any
>> changes, so I won't spend time trying to fix it a second time! :)
>>
>> Bruce
>>
>>>
>>> So if you want to leave the old headers in place, that's an option.
>>>
>>> I fixed the one issue that I saw with Sato .. but I am after all one
>>> person and can't possibly build and boot all the qemu boards with
>>> all image combinations! This is after all, where I'd expect other
>>> people to help out and fix build issues.
>>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>>
>>>> Sau!
>>>>
>>>> Sau!
>>>>
>>>>> [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure
>>>>> [PATCH 5/5] linux-yocto: introduce v3.10
>>>>>
>>>>> ** There is one pending activity. As part of thsi update to 3.10, we
>>>>> want
>>>>> to move to the 3.4 and 3.10 kernel, dropping 3.8 support. But the
>>>>> routerstationpro BSP is still using it as its preferred version. I'm
>>>>> a one man show on this update, and I wasn't able to get the 100+
>>>>> patches
>>>>> ported to 3.10 AND get this update out before the M4 cutoff.
>>>>>
>>>>> ** I'm still attempting to udpate all the reference boards, and
>>>>> once done, I'll send a follow up patch.
>>>>>
>>>>> ** Please test, I've done my best, but things can slip through. We'll
>>>>> work issues in the stabilization period.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Bruce
>>>>>
>>>>>
>>>>> The following changes since commit
>>>>> 501e1a321d15abd712e3a6ee6ccdb8e21c3d4ea4:
>>>>>
>>>>> bitbake: prserv/serv: Fix pid file removal (2013-08-23 17:43:40
>>>>> +0100)
>>>>>
>>>>> are available in the git repository at:
>>>>>
>>>>> git://git.pokylinux.org/poky-contrib zedd/kernel
>>>>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>>>>>
>>>>> Bruce Ashfield (5):
>>>>> kern-tools: usability, bug fixes and no guilt
>>>>> guilt: update to latest git version
>>>>> linux-libc-headers: update to v3.10
>>>>> gst-plugins-good: fix 3.10 libc-headers build failure
>>>>> linux-yocto: introduce v3.10
>>>>>
>>>>> meta/classes/kernel-yocto.bbclass | 2 +
>>>>> meta/conf/distro/include/tcmode-default.inc | 2 +-
>>>>> .../guilt/files/guilt-import-commit.patch | 96 ------
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch | 25 --
>>>>> meta/recipes-devtools/guilt/files/guilt-pop.patch | 73 -----
>>>>> .../guilt/files/guilt-push-no-series.patch | 29 --
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch | 42 ---
>>>>> .../guilt/files/guilt-set-git_exec_path.patch | 29 --
>>>>> ...lt-update-supported-git-versions-to-1.8.x.patch | 28 --
>>>>> meta/recipes-devtools/guilt/files/guilt.patch | 319
>>>>> --------------------
>>>>> .../guilt/files/improve_auto_header_gen.patch | 71 -----
>>>>> .../files/make_git_commands_conditional.patch | 48 ---
>>>>> .../guilt/files/optional_head_check.patch | 60 ----
>>>>> .../guilt/files/uninstall_force.patch | 14 -
>>>>> .../{guilt-native_0.33.bb => guilt-native_git.bb} | 21 +-
>>>>> .../kern-tools/kern-tools-native_git.bb | 6 +-
>>>>> .../linux-libc-headers/linux-libc-headers_3.10.bb | 7 +
>>>>> .../linux-libc-headers/linux-libc-headers_3.8.bb | 8 -
>>>>> meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb | 30 ++
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb | 25 ++
>>>>> meta/recipes-kernel/linux/linux-yocto_3.10.bb | 30 ++
>>>>> ...define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch | 45 +++
>>>>> .../gstreamer/gst-plugins-good_0.10.31.bb | 1 +
>>>>> 23 files changed, 150 insertions(+), 861 deletions(-)
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-import-commit.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-init.patch
>>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt-pop.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push-no-series.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-push.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-set-git_exec_path.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/guilt-update-supported-git-versions-to-1.8.x.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> delete mode 100644 meta/recipes-devtools/guilt/files/guilt.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/improve_auto_header_gen.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/make_git_commands_conditional.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/optional_head_check.patch
>>>>> delete mode 100644
>>>>> meta/recipes-devtools/guilt/files/uninstall_force.patch
>>>>> rename meta/recipes-devtools/guilt/{guilt-native_0.33.bb =>
>>>>> guilt-native_git.bb} (45%)
>>>>> create mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb
>>>>> delete mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.8.bb
>>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_3.10.bb
>>>>> create mode 100644
>>>>> meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
>>>>> create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.10.bb
>>>>> create mode 100644
>>>>> meta/recipes-multimedia/gstreamer/gst-plugins-good-0.10.31/0001-v4l2_calls-define-V4L2_CID_HCENTER-and-V4L2_CID_VCEN.patch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>
>>
>>
^ permalink raw reply [flat|nested] 61+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2023-02-01 16:28 bruce.ashfield
0 siblings, 0 replies; 61+ messages in thread
From: bruce.ashfield @ 2023-02-01 16:28 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Richard,
Here's the latest round of configuration and -stable udpates that
I've collected.
Nothing major, but hopefully the virtio patches will help some of
the AB issues.
Bruce
The following changes since commit da95831d91b1265ecaee5bbfaeb1caaa2c290838:
scons: Pass MAXLINELENGTH to scons invocation (2023-01-31 17:11:07 +0000)
are available in the Git repository at:
https://git.yoctoproject.org/poky-contrib zedd/kernel
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto/6.1: update to v6.1.7
linux-yocto/5.15: update to v5.15.89
linux-yocto/6.1: cfg: remove depreciated configs
linux-yocto/6.1: update to v6.1.9
linux-yocto/5.15: update to v5.15.91
.../linux/linux-yocto-rt_5.15.bb | 6 ++---
.../linux/linux-yocto-rt_6.1.bb | 6 ++---
.../linux/linux-yocto-tiny_5.15.bb | 6 ++---
.../linux/linux-yocto-tiny_6.1.bb | 6 ++---
meta/recipes-kernel/linux/linux-yocto_5.15.bb | 26 +++++++++----------
meta/recipes-kernel/linux/linux-yocto_6.1.bb | 26 +++++++++----------
6 files changed, 38 insertions(+), 38 deletions(-)
--
2.34.1
^ permalink raw reply [flat|nested] 61+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2020-11-19 19:17 Bruce Ashfield
0 siblings, 0 replies; 61+ messages in thread
From: Bruce Ashfield @ 2020-11-19 19:17 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Richard,
Here's my next set of collected changes for linux-yocto. I built and booted the
5.4 -stable bump .. and obviously it looks good.
I've also grabbed a pending devsrc change, that looks good to me.
Finally, I have a fix Khem sent for perf builds. I kept 5.4 and 5.8 separate
for that fix, so Steve can pick them up for Dunfell as appropriate.
Bruce
The following changes since commit d8f47a68a92802fc47f297de05a0f2817963a7ee:
kernel: relocate copy of module.lds to module compilation task (2020-11-18 13:59:27 +0000)
are available in the Git repository at:
git://git.yoctoproject.org/poky-contrib zedd/kernel
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (4):
linux-yocto/5.4: perf: Alias SYS_futex with SYS_futex_time64 on 32-bit
arches with 64bit time_t
linux-yocto/5.8: perf: Alias SYS_futex with SYS_futex_time64 on 32-bit
arches with 64bit time_t
linux-yocto/5.8: ext4/tipc warning fixups
linux-yocto/5.4: update to v5.4.78
INC@Cisco) (1):
kernel-devsrc: improve reproducibility for arm64
meta/recipes-kernel/linux/kernel-devsrc.bb | 4 ++++
.../linux/linux-yocto-rt_5.4.bb | 6 ++---
.../linux/linux-yocto-rt_5.8.bb | 2 +-
.../linux/linux-yocto-tiny_5.4.bb | 8 +++----
.../linux/linux-yocto-tiny_5.8.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22 +++++++++----------
meta/recipes-kernel/linux/linux-yocto_5.8.bb | 18 +++++++--------
7 files changed, 34 insertions(+), 30 deletions(-)
--
2.19.1
^ permalink raw reply [flat|nested] 61+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2020-05-29 1:29 Bruce Ashfield
0 siblings, 0 replies; 61+ messages in thread
From: Bruce Ashfield @ 2020-05-29 1:29 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Hi Richard,
As discussed earlier, this is the pull request which contains a temporary
revert of the CONFIG_IKHEADERS config change that was causing the
periodic issues.
I added a kernel feature that can be used to enable the configuration from
a recipe, that way I won't leave anyone broken while I continue to debug,
since this still is a problem for anyone that is doing reproducible builds
and wants ikheaders.
This went through AB quick and came back green.
Bruce
The following changes since commit 392ba004f42be2fd9dcf121d3dfa5b414ff83f93:
ref-manual: add PACKAGE_ADD_METADATA documentation (2020-05-27 11:05:04 +0100)
are available in the Git repository at:
git://git.yoctoproject.org/poky-contrib zedd/kernel
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto/5.4: update to v5.4.42
linux-yocto-rt/5.4: update to rt24
linux-yocto/5.4: temporarily revert IKHEADERS in standard kernels
linux-yocto: gather reproducibility configs into a fragment
linux-yocto/5.4: update to v5.4.43
.../linux/linux-yocto-rt_5.4.bb | 6 ++---
.../linux/linux-yocto-tiny_5.4.bb | 8 +++----
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22 +++++++++----------
3 files changed, 18 insertions(+), 18 deletions(-)
--
2.19.1
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2020-05-04 8:30 ` Richard Purdie
@ 2020-05-04 12:56 ` Bruce Ashfield
0 siblings, 0 replies; 61+ messages in thread
From: Bruce Ashfield @ 2020-05-04 12:56 UTC (permalink / raw)
To: Richard Purdie; +Cc: Patches and discussions about the oe-core layer, steve
On Mon, May 4, 2020 at 4:31 AM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> Hi Bruce,
>
> On Sun, 2020-05-03 at 11:44 -0400, bruce.ashfield@gmail.com wrote:
> > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> >
> > Hi all,
> >
> > Here are the -stable updates I've collected since m3 of dunfell. I
> > ran things through the autobuilder, and no new kernel issues were
> > picked up.
> >
> > The -dev bump is good for master, while all of the 5.4-stable bumps
> > are good for both master and dunfell.
>
> I pulled these into master-next and saw reproducibility issues. I
> wondered why your test build didn't show it, turns out it also did:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/1024
>
> 2020-05-04 05:18:46,863 - oe-selftest - INFO - ======================================================================
> 2020-05-04 05:18:46,863 - oe-selftest - INFO - FAIL: reproducible.ReproducibleTests.test_reproducible_builds (subunit.RemotedTestCase)
> 2020-05-04 05:18:46,863 - oe-selftest - INFO - ----------------------------------------------------------------------
> 2020-05-04 05:18:46,864 - oe-selftest - INFO - testtools.testresult.real._StringException:
>
> AssertionError: The following deb packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/deb/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_amd64.deb
> The following ipk packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/ipk/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_qemux86_64.ipk
>
I don't see any changes in the kernels that would have triggered it,
but they never are obvious.
I unfortunately have no idea how to run reproducibility tests on the
kernels locally and my build server at home is brutally underpowered
for more than one core-image build per arch a day (hence the
autobuilder runs).
Is there a cut and paste se of instructions about the tests that I
could follow ?
Bruce
> master-next was:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/900
>
> and friends.
>
> Cheers,
>
> Richard
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2020-05-03 15:44 Bruce Ashfield
@ 2020-05-04 8:30 ` Richard Purdie
2020-05-04 12:56 ` Bruce Ashfield
0 siblings, 1 reply; 61+ messages in thread
From: Richard Purdie @ 2020-05-04 8:30 UTC (permalink / raw)
To: bruce.ashfield; +Cc: openembedded-core, steve
Hi Bruce,
On Sun, 2020-05-03 at 11:44 -0400, bruce.ashfield@gmail.com wrote:
> From: Bruce Ashfield <bruce.ashfield@gmail.com>
>
> Hi all,
>
> Here are the -stable updates I've collected since m3 of dunfell. I
> ran things through the autobuilder, and no new kernel issues were
> picked up.
>
> The -dev bump is good for master, while all of the 5.4-stable bumps
> are good for both master and dunfell.
I pulled these into master-next and saw reproducibility issues. I
wondered why your test build didn't show it, turns out it also did:
https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/1024
2020-05-04 05:18:46,863 - oe-selftest - INFO - ======================================================================
2020-05-04 05:18:46,863 - oe-selftest - INFO - FAIL: reproducible.ReproducibleTests.test_reproducible_builds (subunit.RemotedTestCase)
2020-05-04 05:18:46,863 - oe-selftest - INFO - ----------------------------------------------------------------------
2020-05-04 05:18:46,864 - oe-selftest - INFO - testtools.testresult.real._StringException:
AssertionError: The following deb packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/deb/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_amd64.deb
The following ipk packages are missing or different: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/ipk/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_qemux86_64.ipk
master-next was:
https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/900
and friends.
Cheers,
Richard
^ permalink raw reply [flat|nested] 61+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2020-05-03 15:44 Bruce Ashfield
2020-05-04 8:30 ` Richard Purdie
0 siblings, 1 reply; 61+ messages in thread
From: Bruce Ashfield @ 2020-05-03 15:44 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core, steve
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Hi all,
Here are the -stable updates I've collected since m3 of dunfell. I ran
things through the autobuilder, and no new kernel issues were picked up.
The -dev bump is good for master, while all of the 5.4-stable bumps are
good for both master and dunfell.
Cheers,
Bruce
The following changes since commit 2e11d97b6c95e89aa1f9d3603a966c94c442469e:
oeqa/qemurunner: Clean up failure handling (2020-04-26 14:00:51 +0100)
are available in the Git repository at:
git://git.yoctoproject.org/poky-contrib zedd/kernel
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto/5.4: update to v5.4.28
linux-yocto/5.4: update to v5.4.32
linux-yocto/5.4: update to v5.4.34
linux-yocto/5.4: update to v5.4.38
linux-yocto-dev: bump to v5.7-rc
meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +-
.../linux/linux-yocto-rt_5.4.bb | 6 ++---
.../linux/linux-yocto-tiny_5.4.bb | 8 +++----
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22 +++++++++----------
4 files changed, 19 insertions(+), 19 deletions(-)
--
2.19.1
^ permalink raw reply [flat|nested] 61+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2020-03-24 23:04 Bruce Ashfield
0 siblings, 0 replies; 61+ messages in thread
From: Bruce Ashfield @ 2020-03-24 23:04 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Hi all,
Here's the queued bug fixes for linux-yocto. It has khem's identified fixes
for the kernel selftest issues with the latest -stable udpates, as well as
some BSP fixes and config changes.
I ran this through the AB and everything came back green.
I've done this in multiple commits, so we'll have granularity to look
into individual fixes if we have trouble.
Cheers,
Bruce
The following changes since commit d5db9d12642e03a1d5cca5f1520dad5fcc9524c3:
archiver.py: fix typo of "ARCHIVER_MIRROR_EXCLUDE" in comment (2020-03-24 16:39:40 +0000)
are available in the Git repository at:
git://git.yoctoproject.org/poky-contrib zedd/kernel
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto/5.4: Revert "platform/x86: wmi: Destroy on cleanup rather
than unregister"
linux-yocto/5.4: fix kernel selftests
linux-yocto/5.4: KVM: LAPIC: Mark hrtimer for period or oneshot mode
to expire in hard interrupt context
linux-yocto/5.4: ARM: 8918/2: only build return_address() if needed
linux-yocto/5.4: configuration tweaks
.../linux/linux-yocto-rt_5.4.bb | 4 ++--
.../linux/linux-yocto-tiny_5.4.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 20 +++++++++----------
3 files changed, 15 insertions(+), 15 deletions(-)
--
2.19.1
^ permalink raw reply [flat|nested] 61+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2016-07-27 16:57 Bruce Ashfield
0 siblings, 0 replies; 61+ messages in thread
From: Bruce Ashfield @ 2016-07-27 16:57 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
Hi all,
Here's the latest batch of linux-yocto (4.1 and 4.4) changes. They are
-stable updates, a memory leak fix and configuration tweaks (in particular
the removal of debug kernel from the printk fragment).
This is a slight overlap with another series that I sent before, since I
noticed some mistakes in the 4.1 and 4.4-stable update commits .. so I
rephrased them.
Cheers,
Bruce
The following changes since commit 039f47ad197a9a53109c9f3deadd9c35e62c056d:
uclibc: remove meta-yocto-bsp append (2016-07-26 08:56:32 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto/4.4: bump to v4.4.15
linux-yocto/4.1: bump to v4.1.28
linux-yocto/4.1: bug fixes and configuration changes
linux-yocto/4.4: lx-dialog and mei bug fixes
linux-yocto/4.4: mousedev and printk configuation streamlining
meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto_4.1.bb | 20 ++++++++++----------
meta/recipes-kernel/linux/linux-yocto_4.4.bb | 20 ++++++++++----------
6 files changed, 31 insertions(+), 31 deletions(-)
--
2.5.0
^ permalink raw reply [flat|nested] 61+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2016-06-21 15:20 Bruce Ashfield
0 siblings, 0 replies; 61+ messages in thread
From: Bruce Ashfield @ 2016-06-21 15:20 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
Hi all,
Here's the latest set of changes to the 4.1 and 4.4 linux-yocto
kernel's. Nothing particularly exciting, mainline backports and
minor fixups.
Cheers,
Bruce
The following changes since commit 84cce1d49ddb75025ec454d758fbc8d369920122:
e2fsprogs: remove the extra dot from the recipe filename (2016-06-21 13:00:17 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto/4.1: tpm2, pinctrl, powercap and watchdog backports
linux-yocto/4.1: SPI, MFD, alsa and perf backports
linux-yocto/4.1: driver, mmc and power backports
linux-yocto/4.1: pstate backports
linux-yocto/4.4: sensor driver backports
meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_4.1.bb | 16 ++++++++--------
meta/recipes-kernel/linux/linux-yocto_4.4.bb | 16 ++++++++--------
5 files changed, 19 insertions(+), 19 deletions(-)
--
2.5.0
^ permalink raw reply [flat|nested] 61+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2016-04-13 16:12 Bruce Ashfield
0 siblings, 0 replies; 61+ messages in thread
From: Bruce Ashfield @ 2016-04-13 16:12 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
Hi all,
This series contains some changes that I've been gathering over the past
week. Nothing serious, just BSP mainline backports, configuration tweaks
to tiny (for usability) and a change to make aufs4 opt-in (versus always
on).
I've built and booted this for qemu* (standard and -rt).
Cheers,
Bruce
The following changes since commit e912c468875ffea7e8070cb7813bca262d1cbb0b:
kbd: remove uclibc-stdarg.patch (2016-04-13 10:12:53 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto/4.4: gpio-pca953x: fix the "drive" property cannot
read/write
linux-yocto/4.1: mainline SPI backports
linux-yocto/4.4: BXT enablement
linux-yocto: tiny and pin ctrl config updates
linux-yocto: make aufs4 optional
meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto_4.1.bb | 18 +++++++++---------
meta/recipes-kernel/linux/linux-yocto_4.4.bb | 18 +++++++++---------
6 files changed, 26 insertions(+), 26 deletions(-)
--
2.5.0
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-06 22:49 ` Martin Jansa
@ 2015-05-07 15:33 ` Bruce Ashfield
0 siblings, 0 replies; 61+ messages in thread
From: Bruce Ashfield @ 2015-05-07 15:33 UTC (permalink / raw)
To: Martin Jansa, Richard Purdie
Cc: Patches and discussions about the oe-core layer
On 2015-05-06 06:49 PM, Martin Jansa wrote:
> I use tmpfs in most of my builds, so in most cases when I see the error
> from the build, tmpfs is already gone (purged by next build executed on
> the same sever).
ross just found something like this in one of his local builds .. I'm
pretty sure I see the race.
Fix coming shortly, and then the bigger changes I was mentioning before
as well.
Cheers,
Bruce
>
> On Wed, May 6, 2015 at 11:32 PM, Richard Purdie
> <richard.purdie@linuxfoundation.org
> <mailto:richard.purdie@linuxfoundation.org>> wrote:
>
> On Wed, 2015-05-06 at 13:46 -0400, Bruce Ashfield wrote:
> > On 2015-05-06 12:07 PM, Martin Jansa wrote:
> > > I've used master-next week or two ago (mostly to test bluez4 and python3
> > > changes) and soon after that dropped all linux-yocto related changes
> > > from it assuming that it's indeed cause for the issues I'm seeing, but
> > > it's not and it's still failing with master as well (and my
> > > jenkins/world builds are just small portion of my builds executed
> > > elsewhere where I see similar issues).
> >
> > Richard: How can we sort out the differences between the build
> > environment that Martin uses versus what the autobuilder is showing?
> >
> > There's nothing particularly complex happening during that build,
> > it's a checkout and generation of a config.
> >
> > I'm unable to reproduce any of the failures, and neither is the
> > autobuilder.
>
> This is a tough one and I'm struggling a little. We could try looking at
> the tmp/stamps/qemux86-poky-linux/linux-yocto/* files (sigdata in
> particular) as well as
> tmp/work/qemux86-poky-linux/linux-yocto/*/temp/log.task_order
>
> Martin, would you be able to share the above somewhere? I'm hoping this
> would give us a clue as to what the difference is between the builds and
> allow us to reproduce the problem.
>
> Cheers,
>
> Richard
>
>
>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-06 15:33 ` Martin Jansa
2015-05-06 15:44 ` Richard Purdie
@ 2015-05-07 6:33 ` Khem Raj
1 sibling, 0 replies; 61+ messages in thread
From: Khem Raj @ 2015-05-07 6:33 UTC (permalink / raw)
To: Martin Jansa; +Cc: openembedded-core
[-- Attachment #1: Type: text/plain, Size: 448 bytes --]
> On May 6, 2015, at 8:33 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
>
> I'm considering providing simple old-style recipes for vanilla kernels
> and using them in my jenkins builds instead linux-yocto, because kernel
> shouldn't block testing other recipes from meta-oe and other layers as
> often as linux-yocto does.
just for build sake to avoid full kernel builds, having a dummy kernel recipe should be another alternative
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-06 21:32 ` Richard Purdie
@ 2015-05-06 22:49 ` Martin Jansa
2015-05-07 15:33 ` Bruce Ashfield
0 siblings, 1 reply; 61+ messages in thread
From: Martin Jansa @ 2015-05-06 22:49 UTC (permalink / raw)
To: Richard Purdie; +Cc: Patches and discussions about the oe-core layer
[-- Attachment #1: Type: text/plain, Size: 1627 bytes --]
I use tmpfs in most of my builds, so in most cases when I see the error
from the build, tmpfs is already gone (purged by next build executed on the
same sever).
On Wed, May 6, 2015 at 11:32 PM, Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:
> On Wed, 2015-05-06 at 13:46 -0400, Bruce Ashfield wrote:
> > On 2015-05-06 12:07 PM, Martin Jansa wrote:
> > > I've used master-next week or two ago (mostly to test bluez4 and
> python3
> > > changes) and soon after that dropped all linux-yocto related changes
> > > from it assuming that it's indeed cause for the issues I'm seeing, but
> > > it's not and it's still failing with master as well (and my
> > > jenkins/world builds are just small portion of my builds executed
> > > elsewhere where I see similar issues).
> >
> > Richard: How can we sort out the differences between the build
> > environment that Martin uses versus what the autobuilder is showing?
> >
> > There's nothing particularly complex happening during that build,
> > it's a checkout and generation of a config.
> >
> > I'm unable to reproduce any of the failures, and neither is the
> > autobuilder.
>
> This is a tough one and I'm struggling a little. We could try looking at
> the tmp/stamps/qemux86-poky-linux/linux-yocto/* files (sigdata in
> particular) as well as
> tmp/work/qemux86-poky-linux/linux-yocto/*/temp/log.task_order
>
> Martin, would you be able to share the above somewhere? I'm hoping this
> would give us a clue as to what the difference is between the builds and
> allow us to reproduce the problem.
>
> Cheers,
>
> Richard
>
>
>
[-- Attachment #2: Type: text/html, Size: 2142 bytes --]
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-06 17:46 ` Bruce Ashfield
@ 2015-05-06 21:32 ` Richard Purdie
2015-05-06 22:49 ` Martin Jansa
0 siblings, 1 reply; 61+ messages in thread
From: Richard Purdie @ 2015-05-06 21:32 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On Wed, 2015-05-06 at 13:46 -0400, Bruce Ashfield wrote:
> On 2015-05-06 12:07 PM, Martin Jansa wrote:
> > I've used master-next week or two ago (mostly to test bluez4 and python3
> > changes) and soon after that dropped all linux-yocto related changes
> > from it assuming that it's indeed cause for the issues I'm seeing, but
> > it's not and it's still failing with master as well (and my
> > jenkins/world builds are just small portion of my builds executed
> > elsewhere where I see similar issues).
>
> Richard: How can we sort out the differences between the build
> environment that Martin uses versus what the autobuilder is showing?
>
> There's nothing particularly complex happening during that build,
> it's a checkout and generation of a config.
>
> I'm unable to reproduce any of the failures, and neither is the
> autobuilder.
This is a tough one and I'm struggling a little. We could try looking at
the tmp/stamps/qemux86-poky-linux/linux-yocto/* files (sigdata in
particular) as well as
tmp/work/qemux86-poky-linux/linux-yocto/*/temp/log.task_order
Martin, would you be able to share the above somewhere? I'm hoping this
would give us a clue as to what the difference is between the builds and
allow us to reproduce the problem.
Cheers,
Richard
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-06 16:07 ` Martin Jansa
@ 2015-05-06 17:46 ` Bruce Ashfield
2015-05-06 21:32 ` Richard Purdie
0 siblings, 1 reply; 61+ messages in thread
From: Bruce Ashfield @ 2015-05-06 17:46 UTC (permalink / raw)
To: Martin Jansa, Richard Purdie; +Cc: openembedded-core
On 2015-05-06 12:07 PM, Martin Jansa wrote:
> On Wed, May 06, 2015 at 04:44:46PM +0100, Richard Purdie wrote:
>> On Wed, 2015-05-06 at 17:33 +0200, Martin Jansa wrote:
>>> On Wed, May 06, 2015 at 10:58:36AM -0400, Bruce Ashfield wrote:
>>>> On 2015-05-06 10:42 AM, Martin Jansa wrote:
>>>> At this point, all I can say is file a bug. My builds of the same
>>>> board work, and the autobuilder show up green.
>>>>
>>>> That screams race condition, so I'll look into it from that angle.
>>>
>>> I'm considering providing simple old-style recipes for vanilla kernels
>>> and using them in my jenkins builds instead linux-yocto, because kernel
>>> shouldn't block testing other recipes from meta-oe and other layers as
>>> often as linux-yocto does.
>>
>> I wasn't aware of linux-yocto breaking that often?
>
> Someone can query http://errors.yoctoproject.org/ database to see how
> often (or if it's just me and my builds), unfortunately the full-text
> search for "linux-yocto" doesn't provide good overview of issues,
> because it shows 350 errors and not all are from linux-yocto recipe.
>
> http://www.openembedded.org/wiki/Bitbake_World_Status* pages and status
> on e-mail also aren't very accurate because I submit only reports from
> relatively success full builds (so I usually skip the builds with failed
> kernel, unless it's failing like that for long time).
>
>> I am aware that:
>>
>> * we have a race issue with shared_work which we're trying to resolve
>> and its proving tricky to find a patch which doesn't break builds
>>
>> * we have the newly reported issue in this thread. FWIW the builders
>> I've seen are all green
>>
>> * there are some warnings in the build which need addressing
>>
>> but on the most part I thought we'd caught the serious kernel failures
>> in advance of changes hitting master. Are you using master-next or
>> master?
>
> I've used master-next week or two ago (mostly to test bluez4 and python3
> changes) and soon after that dropped all linux-yocto related changes
> from it assuming that it's indeed cause for the issues I'm seeing, but
> it's not and it's still failing with master as well (and my
> jenkins/world builds are just small portion of my builds executed
> elsewhere where I see similar issues).
Richard: How can we sort out the differences between the build
environment that Martin uses versus what the autobuilder is showing?
There's nothing particularly complex happening during that build,
it's a checkout and generation of a config.
I'm unable to reproduce any of the failures, and neither is the
autobuilder.
I've stared at the code and can't see what could cause any of this.
That being said, I think I have a solution to what Martin is reporting
here, where I've changed the way the meta data is maintained and
build.
It will be ready in a week or so, so I'd be interested in us holding
on anything drastic until we can try that out.
Bruce
>
>> Its its -next, I can understand the problems more as that has been
>> unstable recently but then by its nature, it can be. We are rooting out
>> problems before master afaict though?
>>
>> Cheers,
>>
>> Richard
>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-06 15:44 ` Richard Purdie
@ 2015-05-06 16:07 ` Martin Jansa
2015-05-06 17:46 ` Bruce Ashfield
0 siblings, 1 reply; 61+ messages in thread
From: Martin Jansa @ 2015-05-06 16:07 UTC (permalink / raw)
To: Richard Purdie; +Cc: openembedded-core
On Wed, May 06, 2015 at 04:44:46PM +0100, Richard Purdie wrote:
> On Wed, 2015-05-06 at 17:33 +0200, Martin Jansa wrote:
> > On Wed, May 06, 2015 at 10:58:36AM -0400, Bruce Ashfield wrote:
> > > On 2015-05-06 10:42 AM, Martin Jansa wrote:
> > > At this point, all I can say is file a bug. My builds of the same
> > > board work, and the autobuilder show up green.
> > >
> > > That screams race condition, so I'll look into it from that angle.
> >
> > I'm considering providing simple old-style recipes for vanilla kernels
> > and using them in my jenkins builds instead linux-yocto, because kernel
> > shouldn't block testing other recipes from meta-oe and other layers as
> > often as linux-yocto does.
>
> I wasn't aware of linux-yocto breaking that often?
Someone can query http://errors.yoctoproject.org/ database to see how
often (or if it's just me and my builds), unfortunately the full-text
search for "linux-yocto" doesn't provide good overview of issues,
because it shows 350 errors and not all are from linux-yocto recipe.
http://www.openembedded.org/wiki/Bitbake_World_Status* pages and status
on e-mail also aren't very accurate because I submit only reports from
relatively success full builds (so I usually skip the builds with failed
kernel, unless it's failing like that for long time).
> I am aware that:
>
> * we have a race issue with shared_work which we're trying to resolve
> and its proving tricky to find a patch which doesn't break builds
>
> * we have the newly reported issue in this thread. FWIW the builders
> I've seen are all green
>
> * there are some warnings in the build which need addressing
>
> but on the most part I thought we'd caught the serious kernel failures
> in advance of changes hitting master. Are you using master-next or
> master?
I've used master-next week or two ago (mostly to test bluez4 and python3
changes) and soon after that dropped all linux-yocto related changes
from it assuming that it's indeed cause for the issues I'm seeing, but
it's not and it's still failing with master as well (and my
jenkins/world builds are just small portion of my builds executed
elsewhere where I see similar issues).
> Its its -next, I can understand the problems more as that has been
> unstable recently but then by its nature, it can be. We are rooting out
> problems before master afaict though?
>
> Cheers,
>
> Richard
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-06 15:33 ` Martin Jansa
@ 2015-05-06 15:44 ` Richard Purdie
2015-05-06 16:07 ` Martin Jansa
2015-05-07 6:33 ` Khem Raj
1 sibling, 1 reply; 61+ messages in thread
From: Richard Purdie @ 2015-05-06 15:44 UTC (permalink / raw)
To: Martin Jansa; +Cc: openembedded-core
On Wed, 2015-05-06 at 17:33 +0200, Martin Jansa wrote:
> On Wed, May 06, 2015 at 10:58:36AM -0400, Bruce Ashfield wrote:
> > On 2015-05-06 10:42 AM, Martin Jansa wrote:
> > At this point, all I can say is file a bug. My builds of the same
> > board work, and the autobuilder show up green.
> >
> > That screams race condition, so I'll look into it from that angle.
>
> I'm considering providing simple old-style recipes for vanilla kernels
> and using them in my jenkins builds instead linux-yocto, because kernel
> shouldn't block testing other recipes from meta-oe and other layers as
> often as linux-yocto does.
I wasn't aware of linux-yocto breaking that often?
I am aware that:
* we have a race issue with shared_work which we're trying to resolve
and its proving tricky to find a patch which doesn't break builds
* we have the newly reported issue in this thread. FWIW the builders
I've seen are all green
* there are some warnings in the build which need addressing
but on the most part I thought we'd caught the serious kernel failures
in advance of changes hitting master. Are you using master-next or
master?
Its its -next, I can understand the problems more as that has been
unstable recently but then by its nature, it can be. We are rooting out
problems before master afaict though?
Cheers,
Richard
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-06 14:58 ` Bruce Ashfield
@ 2015-05-06 15:33 ` Martin Jansa
2015-05-06 15:44 ` Richard Purdie
2015-05-07 6:33 ` Khem Raj
0 siblings, 2 replies; 61+ messages in thread
From: Martin Jansa @ 2015-05-06 15:33 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On Wed, May 06, 2015 at 10:58:36AM -0400, Bruce Ashfield wrote:
> On 2015-05-06 10:42 AM, Martin Jansa wrote:
> > On Sat, May 02, 2015 at 10:50:53PM -0400, Bruce Ashfield wrote:
> >> On 2015-05-02 4:13 AM, Martin Jansa wrote:
> >>> On Fri, May 01, 2015 at 07:30:24PM -0400, Bruce Ashfield wrote:
> >>>> On 2015-05-01 6:59 PM, Richard Purdie wrote:
> >>>>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> >>>>>> Here is the latest consolidated pull request for the supported linux-yocto
> >>>>>> kernels.
> >>>>>>
> >>>>>> - We have a refresh of the 3.14-rt support
> >>>>>> - bluetooh configuration changes for common-pc/qemux86
> >>>>>> - braswell BSP features and fixes
> >>>>>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
> >>>>>> I've built and booted these on my local machines and qemu, and
> >>>>>> everything was sane.
> >>>
> >>> Does it fix the issue I've reported few days ago?
> >>> http://lists.openembedded.org/pipermail/openembedded-core/2015-April/104344.html
> >>
> >> Nope. But one config warning is far down on the list when I'm
> >> trying to introduce new -stable's and an entire -dev kernel.
> >>
> >> I didn't forget about it, it'll just get done in priority order.
> >
> > OK, now it fails completely in default qemux86 builds:
> >
>
> At this point, all I can say is file a bug. My builds of the same
> board work, and the autobuilder show up green.
>
> That screams race condition, so I'll look into it from that angle.
I'm considering providing simple old-style recipes for vanilla kernels
and using them in my jenkins builds instead linux-yocto, because kernel
shouldn't block testing other recipes from meta-oe and other layers as
often as linux-yocto does.
> > ERROR: Function failed: do_kernel_configme (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159)
> > ERROR: Logfile of failure stored in: /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159
> > Log data follows:
> > | DEBUG: Executing shell function do_kernel_configme
> > | NOTE: kernel configme
> > | [INFO] Configuring target/machine combo: "standard/qemux86"
> > | [INFO] collecting configs in .meta/meta-series
> > | [ERROR] frag /home/jenkins/oe/world/shr-core/tmp-glibc/work-shared/qemux86/kernel-source/.meta/cfg/kernel-cache/bsp/common-pc/common-pc-drivers-32.cfg does not exist
> > | Error running the meta series for collecting config data
> > | config of "standard/qemux86" failed
> > | WARNING: exit code 1 from a shell command.
> > | ERROR: Function failed: do_kernel_configme (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159)
> > NOTE: recipe linux-yocto-3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0: task do_kernel_configme: Failed
> > ERROR: Task 30162 (/home/jenkins/oe/world/shr-core/openembedded-core/meta/recipes-kernel/linux/linux-yocto_3.19.bb, do_kernel_configme) failed with exit code '1'
> >
> > http://errors.yoctoproject.org/Errors/Details/10481/
> >
> >>>>>> The -dev kernel obviously isn't something for deployment yet, but
> >>>>>> it builds, and forms the base for follow up config changes, features
> >>>>>> and development work. I built and booted core-image-kernel dev with
> >>>>>> the 4.1 changes in place.
> >>>>>
> >>>>> The autobuilder showed up this for an x32 build :/.
> >>>>
> >>>> Can one of the intel folks have a look at this ? I won't be able to get
> >>>> to it until Tuesday at the earliest.
> >>>>
> >>>> Bruce
> >>>>
> >>>>>
> >>>>> https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio
> >>>>>
> >>>>> Cheers,
> >>>>>
> >>>>> Richard
> >>>>>
> >>>>
> >>>> --
> >>>> _______________________________________________
> >>>> Openembedded-core mailing list
> >>>> Openembedded-core@lists.openembedded.org
> >>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
> >>>
> >>
> >
>
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-06 14:42 ` Martin Jansa
@ 2015-05-06 14:58 ` Bruce Ashfield
2015-05-06 15:33 ` Martin Jansa
0 siblings, 1 reply; 61+ messages in thread
From: Bruce Ashfield @ 2015-05-06 14:58 UTC (permalink / raw)
To: Martin Jansa; +Cc: openembedded-core
On 2015-05-06 10:42 AM, Martin Jansa wrote:
> On Sat, May 02, 2015 at 10:50:53PM -0400, Bruce Ashfield wrote:
>> On 2015-05-02 4:13 AM, Martin Jansa wrote:
>>> On Fri, May 01, 2015 at 07:30:24PM -0400, Bruce Ashfield wrote:
>>>> On 2015-05-01 6:59 PM, Richard Purdie wrote:
>>>>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>>>>>> Here is the latest consolidated pull request for the supported linux-yocto
>>>>>> kernels.
>>>>>>
>>>>>> - We have a refresh of the 3.14-rt support
>>>>>> - bluetooh configuration changes for common-pc/qemux86
>>>>>> - braswell BSP features and fixes
>>>>>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>>>>> I've built and booted these on my local machines and qemu, and
>>>>>> everything was sane.
>>>
>>> Does it fix the issue I've reported few days ago?
>>> http://lists.openembedded.org/pipermail/openembedded-core/2015-April/104344.html
>>
>> Nope. But one config warning is far down on the list when I'm
>> trying to introduce new -stable's and an entire -dev kernel.
>>
>> I didn't forget about it, it'll just get done in priority order.
>
> OK, now it fails completely in default qemux86 builds:
>
At this point, all I can say is file a bug. My builds of the same
board work, and the autobuilder show up green.
That screams race condition, so I'll look into it from that angle.
Bruce
> ERROR: Function failed: do_kernel_configme (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159)
> ERROR: Logfile of failure stored in: /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159
> Log data follows:
> | DEBUG: Executing shell function do_kernel_configme
> | NOTE: kernel configme
> | [INFO] Configuring target/machine combo: "standard/qemux86"
> | [INFO] collecting configs in .meta/meta-series
> | [ERROR] frag /home/jenkins/oe/world/shr-core/tmp-glibc/work-shared/qemux86/kernel-source/.meta/cfg/kernel-cache/bsp/common-pc/common-pc-drivers-32.cfg does not exist
> | Error running the meta series for collecting config data
> | config of "standard/qemux86" failed
> | WARNING: exit code 1 from a shell command.
> | ERROR: Function failed: do_kernel_configme (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159)
> NOTE: recipe linux-yocto-3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0: task do_kernel_configme: Failed
> ERROR: Task 30162 (/home/jenkins/oe/world/shr-core/openembedded-core/meta/recipes-kernel/linux/linux-yocto_3.19.bb, do_kernel_configme) failed with exit code '1'
>
> http://errors.yoctoproject.org/Errors/Details/10481/
>
>>>>>> The -dev kernel obviously isn't something for deployment yet, but
>>>>>> it builds, and forms the base for follow up config changes, features
>>>>>> and development work. I built and booted core-image-kernel dev with
>>>>>> the 4.1 changes in place.
>>>>>
>>>>> The autobuilder showed up this for an x32 build :/.
>>>>
>>>> Can one of the intel folks have a look at this ? I won't be able to get
>>>> to it until Tuesday at the earliest.
>>>>
>>>> Bruce
>>>>
>>>>>
>>>>> https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Richard
>>>>>
>>>>
>>>> --
>>>> _______________________________________________
>>>> Openembedded-core mailing list
>>>> Openembedded-core@lists.openembedded.org
>>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>>
>>
>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-03 2:50 ` Bruce Ashfield
@ 2015-05-06 14:42 ` Martin Jansa
2015-05-06 14:58 ` Bruce Ashfield
0 siblings, 1 reply; 61+ messages in thread
From: Martin Jansa @ 2015-05-06 14:42 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On Sat, May 02, 2015 at 10:50:53PM -0400, Bruce Ashfield wrote:
> On 2015-05-02 4:13 AM, Martin Jansa wrote:
> > On Fri, May 01, 2015 at 07:30:24PM -0400, Bruce Ashfield wrote:
> >> On 2015-05-01 6:59 PM, Richard Purdie wrote:
> >>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> >>>> Here is the latest consolidated pull request for the supported linux-yocto
> >>>> kernels.
> >>>>
> >>>> - We have a refresh of the 3.14-rt support
> >>>> - bluetooh configuration changes for common-pc/qemux86
> >>>> - braswell BSP features and fixes
> >>>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
> >>>> I've built and booted these on my local machines and qemu, and
> >>>> everything was sane.
> >
> > Does it fix the issue I've reported few days ago?
> > http://lists.openembedded.org/pipermail/openembedded-core/2015-April/104344.html
>
> Nope. But one config warning is far down on the list when I'm
> trying to introduce new -stable's and an entire -dev kernel.
>
> I didn't forget about it, it'll just get done in priority order.
OK, now it fails completely in default qemux86 builds:
ERROR: Function failed: do_kernel_configme (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159)
ERROR: Logfile of failure stored in: /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159
Log data follows:
| DEBUG: Executing shell function do_kernel_configme
| NOTE: kernel configme
| [INFO] Configuring target/machine combo: "standard/qemux86"
| [INFO] collecting configs in .meta/meta-series
| [ERROR] frag /home/jenkins/oe/world/shr-core/tmp-glibc/work-shared/qemux86/kernel-source/.meta/cfg/kernel-cache/bsp/common-pc/common-pc-drivers-32.cfg does not exist
| Error running the meta series for collecting config data
| config of "standard/qemux86" failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_kernel_configme (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0/temp/log.do_kernel_configme.1159)
NOTE: recipe linux-yocto-3.19.5+gitAUTOINC+7215fe4313_d5d30ba4d2-r0: task do_kernel_configme: Failed
ERROR: Task 30162 (/home/jenkins/oe/world/shr-core/openembedded-core/meta/recipes-kernel/linux/linux-yocto_3.19.bb, do_kernel_configme) failed with exit code '1'
http://errors.yoctoproject.org/Errors/Details/10481/
> >>>> The -dev kernel obviously isn't something for deployment yet, but
> >>>> it builds, and forms the base for follow up config changes, features
> >>>> and development work. I built and booted core-image-kernel dev with
> >>>> the 4.1 changes in place.
> >>>
> >>> The autobuilder showed up this for an x32 build :/.
> >>
> >> Can one of the intel folks have a look at this ? I won't be able to get
> >> to it until Tuesday at the earliest.
> >>
> >> Bruce
> >>
> >>>
> >>> https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio
> >>>
> >>> Cheers,
> >>>
> >>> Richard
> >>>
> >>
> >> --
> >> _______________________________________________
> >> Openembedded-core mailing list
> >> Openembedded-core@lists.openembedded.org
> >> http://lists.openembedded.org/mailman/listinfo/openembedded-core
> >
>
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-03 21:30 ` Richard Purdie
2015-05-04 4:36 ` Bruce Ashfield
@ 2015-05-04 15:01 ` Bruce Ashfield
1 sibling, 0 replies; 61+ messages in thread
From: Bruce Ashfield @ 2015-05-04 15:01 UTC (permalink / raw)
To: Richard Purdie; +Cc: openembedded-core
On 2015-05-03 05:30 PM, Richard Purdie wrote:
> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>> Here is the latest consolidated pull request for the supported linux-yocto
>> kernels.
>>
>> - We have a refresh of the 3.14-rt support
>> - bluetooh configuration changes for common-pc/qemux86
>> - braswell BSP features and fixes
>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>
>> I've built and booted these on my local machines and qemu, and
>> everything was sane.
>>
>> The -dev kernel obviously isn't something for deployment yet, but
>> it builds, and forms the base for follow up config changes, features
>> and development work. I built and booted core-image-kernel dev with
>> the 4.1 changes in place.
>
> There was also a problem with poky-lsb. The idea (as far as I remember)
> is that it should be using LTSI rather than the default main kernel so
> we could split the testing. Unfortunately it was pointing at 3.10 which
> doesn't exist any longer so was using 3.17. I think LTSI is 3.14 so I
> updated the PREFERRED_VERSION to that.
>
> This resulted in this failure on the autobuilder:
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-mips-lsb/builds/281/steps/BuildImages/logs/stdio
>
> Basically with qemumips and 3.14. Hopefully not a hard one to fix. If
> I've mixed the versions up, let me know which one poky-lsb should be
FYI: I've fixed the mips build. Looking at x86 now. SRCREV updates
to follow ASAP.
Bruce
> using.
>
> Cheers,
>
> Richard
>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-03 21:30 ` Richard Purdie
@ 2015-05-04 4:36 ` Bruce Ashfield
2015-05-04 15:01 ` Bruce Ashfield
1 sibling, 0 replies; 61+ messages in thread
From: Bruce Ashfield @ 2015-05-04 4:36 UTC (permalink / raw)
To: Richard Purdie; +Cc: openembedded-core
On 2015-05-03 5:30 PM, Richard Purdie wrote:
> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>> Here is the latest consolidated pull request for the supported linux-yocto
>> kernels.
>>
>> - We have a refresh of the 3.14-rt support
>> - bluetooh configuration changes for common-pc/qemux86
>> - braswell BSP features and fixes
>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>
>> I've built and booted these on my local machines and qemu, and
>> everything was sane.
>>
>> The -dev kernel obviously isn't something for deployment yet, but
>> it builds, and forms the base for follow up config changes, features
>> and development work. I built and booted core-image-kernel dev with
>> the 4.1 changes in place.
>
> There was also a problem with poky-lsb. The idea (as far as I remember)
> is that it should be using LTSI rather than the default main kernel so
> we could split the testing. Unfortunately it was pointing at 3.10 which
> doesn't exist any longer so was using 3.17. I think LTSI is 3.14 so I
> updated the PREFERRED_VERSION to that.
Correct on all counts. We did want it to use LTSI, and that is 3.14
at the moment.
>
> This resulted in this failure on the autobuilder:
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-mips-lsb/builds/281/steps/BuildImages/logs/stdio
>
> Basically with qemumips and 3.14. Hopefully not a hard one to fix. If
Doesn't look to bad. I'll address this one along with the x32 build
failure on Monday (assuming I get it fixed in the day).
Bruce
> I've mixed the versions up, let me know which one poky-lsb should be
> using.
>
> Cheers,
>
> Richard
>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-01 1:34 Bruce Ashfield
2015-05-01 22:59 ` Richard Purdie
@ 2015-05-03 21:30 ` Richard Purdie
2015-05-04 4:36 ` Bruce Ashfield
2015-05-04 15:01 ` Bruce Ashfield
1 sibling, 2 replies; 61+ messages in thread
From: Richard Purdie @ 2015-05-03 21:30 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> Here is the latest consolidated pull request for the supported linux-yocto
> kernels.
>
> - We have a refresh of the 3.14-rt support
> - bluetooh configuration changes for common-pc/qemux86
> - braswell BSP features and fixes
> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>
> I've built and booted these on my local machines and qemu, and
> everything was sane.
>
> The -dev kernel obviously isn't something for deployment yet, but
> it builds, and forms the base for follow up config changes, features
> and development work. I built and booted core-image-kernel dev with
> the 4.1 changes in place.
There was also a problem with poky-lsb. The idea (as far as I remember)
is that it should be using LTSI rather than the default main kernel so
we could split the testing. Unfortunately it was pointing at 3.10 which
doesn't exist any longer so was using 3.17. I think LTSI is 3.14 so I
updated the PREFERRED_VERSION to that.
This resulted in this failure on the autobuilder:
https://autobuilder.yoctoproject.org/main/builders/nightly-mips-lsb/builds/281/steps/BuildImages/logs/stdio
Basically with qemumips and 3.14. Hopefully not a hard one to fix. If
I've mixed the versions up, let me know which one poky-lsb should be
using.
Cheers,
Richard
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-03 3:52 ` Bruce Ashfield
@ 2015-05-03 10:48 ` Richard Purdie
0 siblings, 0 replies; 61+ messages in thread
From: Richard Purdie @ 2015-05-03 10:48 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On Sat, 2015-05-02 at 23:52 -0400, Bruce Ashfield wrote:
> On 2015-05-02 5:00 AM, Richard Purdie wrote:
> > On Fri, 2015-05-01 at 19:30 -0400, Bruce Ashfield wrote:
> >> On 2015-05-01 6:59 PM, Richard Purdie wrote:
> >>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> >>>> Here is the latest consolidated pull request for the supported linux-yocto
> >>>> kernels.
> >>>>
> >>>> - We have a refresh of the 3.14-rt support
> >>>> - bluetooh configuration changes for common-pc/qemux86
> >>>> - braswell BSP features and fixes
> >>>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
> >>>>
> >>>> I've built and booted these on my local machines and qemu, and
> >>>> everything was sane.
> >>>>
> >>>> The -dev kernel obviously isn't something for deployment yet, but
> >>>> it builds, and forms the base for follow up config changes, features
> >>>> and development work. I built and booted core-image-kernel dev with
> >>>> the 4.1 changes in place.
> >>>
> >>> The autobuilder showed up this for an x32 build :/.
> >>
> >> Can one of the intel folks have a look at this ? I won't be able to get
> >> to it until Tuesday at the earliest.
> >
> > I had a look into this. The issue is that this has been applied:
> >
> > http://git.yoctoproject.org/cgit.cgi/linux-yocto-3.19/commit/?h=standard/base&id=423e98721e048f6c7b925a75448f6c4ecb2b5b69
> >
> > but it needs:
> >
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ce793486e23e0162a732c605189c8028e0910e86
> >
> > and the ioapic driver also appears to need:
> >
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=ecf5636dcd59cd5508641f995cc4c2bafedbb995
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=62d1141ff34e35de496ba06491c8e854b23b3f3e
> >
> >
> > which meant I also had to add:
> >
> > struct resource_win {
> > struct resource res; /* In master (CPU) address space */
> > resource_size_t offset; /* Translation offset for bridge */
> > };
> >
> > to drivers/acpi/ioapic.c to make it compile which appears to be related to:
> >
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a49170b552423a3e85fc4f0d778c707402ee4863
> >
> > which depends on a number of patches from around that time which change acpi/resource.c:
> >
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/acpi/resource.c
> >
> > (from 2015/2/3)
> >
> > At this point I'm out my depth on how you want to fix this but it does
> > appear related to the Braswell changes.
> >
> > To be clear qemux86 and qemux86-64 don't build at all with this series.
> > I'll see if I can just drop the Braswell parts.
>
> I did reproduce the issue here as well, so with any luck, I can sneak
> enough time to have this fixed for Monday after all.
From my perspective there isn't a rush at this point. I've merged the
config changes which unblocked the bluez patches and things are
therefore "flowing" from my perspective, the stable update can wait
until later in the week.
Cheers,
Richard
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-02 9:00 ` Richard Purdie
2015-05-03 2:53 ` Bruce Ashfield
@ 2015-05-03 3:52 ` Bruce Ashfield
2015-05-03 10:48 ` Richard Purdie
1 sibling, 1 reply; 61+ messages in thread
From: Bruce Ashfield @ 2015-05-03 3:52 UTC (permalink / raw)
To: Richard Purdie; +Cc: openembedded-core
On 2015-05-02 5:00 AM, Richard Purdie wrote:
> On Fri, 2015-05-01 at 19:30 -0400, Bruce Ashfield wrote:
>> On 2015-05-01 6:59 PM, Richard Purdie wrote:
>>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>>>> Here is the latest consolidated pull request for the supported linux-yocto
>>>> kernels.
>>>>
>>>> - We have a refresh of the 3.14-rt support
>>>> - bluetooh configuration changes for common-pc/qemux86
>>>> - braswell BSP features and fixes
>>>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>>>
>>>> I've built and booted these on my local machines and qemu, and
>>>> everything was sane.
>>>>
>>>> The -dev kernel obviously isn't something for deployment yet, but
>>>> it builds, and forms the base for follow up config changes, features
>>>> and development work. I built and booted core-image-kernel dev with
>>>> the 4.1 changes in place.
>>>
>>> The autobuilder showed up this for an x32 build :/.
>>
>> Can one of the intel folks have a look at this ? I won't be able to get
>> to it until Tuesday at the earliest.
>
> I had a look into this. The issue is that this has been applied:
>
> http://git.yoctoproject.org/cgit.cgi/linux-yocto-3.19/commit/?h=standard/base&id=423e98721e048f6c7b925a75448f6c4ecb2b5b69
>
> but it needs:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ce793486e23e0162a732c605189c8028e0910e86
>
> and the ioapic driver also appears to need:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=ecf5636dcd59cd5508641f995cc4c2bafedbb995
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=62d1141ff34e35de496ba06491c8e854b23b3f3e
>
>
> which meant I also had to add:
>
> struct resource_win {
> struct resource res; /* In master (CPU) address space */
> resource_size_t offset; /* Translation offset for bridge */
> };
>
> to drivers/acpi/ioapic.c to make it compile which appears to be related to:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a49170b552423a3e85fc4f0d778c707402ee4863
>
> which depends on a number of patches from around that time which change acpi/resource.c:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/acpi/resource.c
>
> (from 2015/2/3)
>
> At this point I'm out my depth on how you want to fix this but it does
> appear related to the Braswell changes.
>
> To be clear qemux86 and qemux86-64 don't build at all with this series.
> I'll see if I can just drop the Braswell parts.
I did reproduce the issue here as well, so with any luck, I can sneak
enough time to have this fixed for Monday after all.
Bruce
>
> Cheers,
>
> Richard
>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-02 9:00 ` Richard Purdie
@ 2015-05-03 2:53 ` Bruce Ashfield
2015-05-03 3:52 ` Bruce Ashfield
1 sibling, 0 replies; 61+ messages in thread
From: Bruce Ashfield @ 2015-05-03 2:53 UTC (permalink / raw)
To: Richard Purdie; +Cc: openembedded-core
On 2015-05-02 5:00 AM, Richard Purdie wrote:
> On Fri, 2015-05-01 at 19:30 -0400, Bruce Ashfield wrote:
>> On 2015-05-01 6:59 PM, Richard Purdie wrote:
>>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>>>> Here is the latest consolidated pull request for the supported linux-yocto
>>>> kernels.
>>>>
>>>> - We have a refresh of the 3.14-rt support
>>>> - bluetooh configuration changes for common-pc/qemux86
>>>> - braswell BSP features and fixes
>>>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>>>
>>>> I've built and booted these on my local machines and qemu, and
>>>> everything was sane.
>>>>
>>>> The -dev kernel obviously isn't something for deployment yet, but
>>>> it builds, and forms the base for follow up config changes, features
>>>> and development work. I built and booted core-image-kernel dev with
>>>> the 4.1 changes in place.
>>>
>>> The autobuilder showed up this for an x32 build :/.
>>
>> Can one of the intel folks have a look at this ? I won't be able to get
>> to it until Tuesday at the earliest.
>
> I had a look into this. The issue is that this has been applied:
>
> http://git.yoctoproject.org/cgit.cgi/linux-yocto-3.19/commit/?h=standard/base&id=423e98721e048f6c7b925a75448f6c4ecb2b5b69
>
> but it needs:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ce793486e23e0162a732c605189c8028e0910e86
>
> and the ioapic driver also appears to need:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=ecf5636dcd59cd5508641f995cc4c2bafedbb995
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=62d1141ff34e35de496ba06491c8e854b23b3f3e
>
>
> which meant I also had to add:
>
> struct resource_win {
> struct resource res; /* In master (CPU) address space */
> resource_size_t offset; /* Translation offset for bridge */
> };
>
> to drivers/acpi/ioapic.c to make it compile which appears to be related to:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a49170b552423a3e85fc4f0d778c707402ee4863
>
> which depends on a number of patches from around that time which change acpi/resource.c:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/acpi/resource.c
>
> (from 2015/2/3)
>
> At this point I'm out my depth on how you want to fix this but it does
> appear related to the Braswell changes.
>
> To be clear qemux86 and qemux86-64 don't build at all with this series.
> I'll see if I can just drop the Braswell parts.
Gah. It figures. That's of course the issue with any set of BSP ports ..
they get tangled up with Greg's series from time to time.
The changes are all additive, so we can't really drop the braswell parts
unless I revert the whole block of changes.
Drop those -stable updates for now, and I'll see if I can carve out some
time tomorrow to get that config building.
Bruce
>
> Cheers,
>
> Richard
>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-02 8:13 ` Martin Jansa
@ 2015-05-03 2:50 ` Bruce Ashfield
2015-05-06 14:42 ` Martin Jansa
0 siblings, 1 reply; 61+ messages in thread
From: Bruce Ashfield @ 2015-05-03 2:50 UTC (permalink / raw)
To: Martin Jansa; +Cc: openembedded-core
On 2015-05-02 4:13 AM, Martin Jansa wrote:
> On Fri, May 01, 2015 at 07:30:24PM -0400, Bruce Ashfield wrote:
>> On 2015-05-01 6:59 PM, Richard Purdie wrote:
>>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>>>> Here is the latest consolidated pull request for the supported linux-yocto
>>>> kernels.
>>>>
>>>> - We have a refresh of the 3.14-rt support
>>>> - bluetooh configuration changes for common-pc/qemux86
>>>> - braswell BSP features and fixes
>>>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>>> I've built and booted these on my local machines and qemu, and
>>>> everything was sane.
>
> Does it fix the issue I've reported few days ago?
> http://lists.openembedded.org/pipermail/openembedded-core/2015-April/104344.html
Nope. But one config warning is far down on the list when I'm
trying to introduce new -stable's and an entire -dev kernel.
I didn't forget about it, it'll just get done in priority order.
Bruce
>
>>>> The -dev kernel obviously isn't something for deployment yet, but
>>>> it builds, and forms the base for follow up config changes, features
>>>> and development work. I built and booted core-image-kernel dev with
>>>> the 4.1 changes in place.
>>>
>>> The autobuilder showed up this for an x32 build :/.
>>
>> Can one of the intel folks have a look at this ? I won't be able to get
>> to it until Tuesday at the earliest.
>>
>> Bruce
>>
>>>
>>> https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio
>>>
>>> Cheers,
>>>
>>> Richard
>>>
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-01 23:30 ` Bruce Ashfield
2015-05-02 8:13 ` Martin Jansa
@ 2015-05-02 9:00 ` Richard Purdie
2015-05-03 2:53 ` Bruce Ashfield
2015-05-03 3:52 ` Bruce Ashfield
1 sibling, 2 replies; 61+ messages in thread
From: Richard Purdie @ 2015-05-02 9:00 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On Fri, 2015-05-01 at 19:30 -0400, Bruce Ashfield wrote:
> On 2015-05-01 6:59 PM, Richard Purdie wrote:
> > On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> >> Here is the latest consolidated pull request for the supported linux-yocto
> >> kernels.
> >>
> >> - We have a refresh of the 3.14-rt support
> >> - bluetooh configuration changes for common-pc/qemux86
> >> - braswell BSP features and fixes
> >> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
> >>
> >> I've built and booted these on my local machines and qemu, and
> >> everything was sane.
> >>
> >> The -dev kernel obviously isn't something for deployment yet, but
> >> it builds, and forms the base for follow up config changes, features
> >> and development work. I built and booted core-image-kernel dev with
> >> the 4.1 changes in place.
> >
> > The autobuilder showed up this for an x32 build :/.
>
> Can one of the intel folks have a look at this ? I won't be able to get
> to it until Tuesday at the earliest.
I had a look into this. The issue is that this has been applied:
http://git.yoctoproject.org/cgit.cgi/linux-yocto-3.19/commit/?h=standard/base&id=423e98721e048f6c7b925a75448f6c4ecb2b5b69
but it needs:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ce793486e23e0162a732c605189c8028e0910e86
and the ioapic driver also appears to need:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=ecf5636dcd59cd5508641f995cc4c2bafedbb995
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=62d1141ff34e35de496ba06491c8e854b23b3f3e
which meant I also had to add:
struct resource_win {
struct resource res; /* In master (CPU) address space */
resource_size_t offset; /* Translation offset for bridge */
};
to drivers/acpi/ioapic.c to make it compile which appears to be related to:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a49170b552423a3e85fc4f0d778c707402ee4863
which depends on a number of patches from around that time which change acpi/resource.c:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/acpi/resource.c
(from 2015/2/3)
At this point I'm out my depth on how you want to fix this but it does
appear related to the Braswell changes.
To be clear qemux86 and qemux86-64 don't build at all with this series.
I'll see if I can just drop the Braswell parts.
Cheers,
Richard
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-01 23:30 ` Bruce Ashfield
@ 2015-05-02 8:13 ` Martin Jansa
2015-05-03 2:50 ` Bruce Ashfield
2015-05-02 9:00 ` Richard Purdie
1 sibling, 1 reply; 61+ messages in thread
From: Martin Jansa @ 2015-05-02 8:13 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On Fri, May 01, 2015 at 07:30:24PM -0400, Bruce Ashfield wrote:
> On 2015-05-01 6:59 PM, Richard Purdie wrote:
> > On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> >> Here is the latest consolidated pull request for the supported linux-yocto
> >> kernels.
> >>
> >> - We have a refresh of the 3.14-rt support
> >> - bluetooh configuration changes for common-pc/qemux86
> >> - braswell BSP features and fixes
> >> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
> >> I've built and booted these on my local machines and qemu, and
> >> everything was sane.
Does it fix the issue I've reported few days ago?
http://lists.openembedded.org/pipermail/openembedded-core/2015-April/104344.html
> >> The -dev kernel obviously isn't something for deployment yet, but
> >> it builds, and forms the base for follow up config changes, features
> >> and development work. I built and booted core-image-kernel dev with
> >> the 4.1 changes in place.
> >
> > The autobuilder showed up this for an x32 build :/.
>
> Can one of the intel folks have a look at this ? I won't be able to get
> to it until Tuesday at the earliest.
>
> Bruce
>
> >
> > https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio
> >
> > Cheers,
> >
> > Richard
> >
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-01 22:59 ` Richard Purdie
@ 2015-05-01 23:30 ` Bruce Ashfield
2015-05-02 8:13 ` Martin Jansa
2015-05-02 9:00 ` Richard Purdie
0 siblings, 2 replies; 61+ messages in thread
From: Bruce Ashfield @ 2015-05-01 23:30 UTC (permalink / raw)
To: Richard Purdie; +Cc: openembedded-core
On 2015-05-01 6:59 PM, Richard Purdie wrote:
> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>> Here is the latest consolidated pull request for the supported linux-yocto
>> kernels.
>>
>> - We have a refresh of the 3.14-rt support
>> - bluetooh configuration changes for common-pc/qemux86
>> - braswell BSP features and fixes
>> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>
>> I've built and booted these on my local machines and qemu, and
>> everything was sane.
>>
>> The -dev kernel obviously isn't something for deployment yet, but
>> it builds, and forms the base for follow up config changes, features
>> and development work. I built and booted core-image-kernel dev with
>> the 4.1 changes in place.
>
> The autobuilder showed up this for an x32 build :/.
Can one of the intel folks have a look at this ? I won't be able to get
to it until Tuesday at the earliest.
Bruce
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio
>
> Cheers,
>
> Richard
>
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-05-01 1:34 Bruce Ashfield
@ 2015-05-01 22:59 ` Richard Purdie
2015-05-01 23:30 ` Bruce Ashfield
2015-05-03 21:30 ` Richard Purdie
1 sibling, 1 reply; 61+ messages in thread
From: Richard Purdie @ 2015-05-01 22:59 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
> Here is the latest consolidated pull request for the supported linux-yocto
> kernels.
>
> - We have a refresh of the 3.14-rt support
> - bluetooh configuration changes for common-pc/qemux86
> - braswell BSP features and fixes
> - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>
> I've built and booted these on my local machines and qemu, and
> everything was sane.
>
> The -dev kernel obviously isn't something for deployment yet, but
> it builds, and forms the base for follow up config changes, features
> and development work. I built and booted core-image-kernel dev with
> the 4.1 changes in place.
The autobuilder showed up this for an x32 build :/.
https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/282/steps/BuildImages/logs/stdio
Cheers,
Richard
^ permalink raw reply [flat|nested] 61+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2015-05-01 1:34 Bruce Ashfield
2015-05-01 22:59 ` Richard Purdie
2015-05-03 21:30 ` Richard Purdie
0 siblings, 2 replies; 61+ messages in thread
From: Bruce Ashfield @ 2015-05-01 1:34 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
Here is the latest consolidated pull request for the supported linux-yocto
kernels.
- We have a refresh of the 3.14-rt support
- bluetooh configuration changes for common-pc/qemux86
- braswell BSP features and fixes
- Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
I've built and booted these on my local machines and qemu, and
everything was sane.
The -dev kernel obviously isn't something for deployment yet, but
it builds, and forms the base for follow up config changes, features
and development work. I built and booted core-image-kernel dev with
the 4.1 changes in place.
Cheers,
Bruce
The following changes since commit db409697db2ea0931cdcd2015d089b6b0ea39bbb:
bitbake: bitbake: reset build mtime cache before the build (2015-04-29 10:59:54 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto/3.14: refresh -rt support
linux-yocto: add core bluetooth support to qemux86* and common-pc*
linux-yocto/3.19: Braswell support and bug fixes
perf: fix build (and feature tests) for 4.1-rcX
linux-yocto-dev: introduce 4.1-rc development kernel
meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto_3.14.bb | 18 +++++++++---------
meta/recipes-kernel/linux/linux-yocto_3.19.bb | 18 +++++++++---------
meta/recipes-kernel/perf/perf.bb | 3 +++
7 files changed, 29 insertions(+), 26 deletions(-)
--
2.1.0
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-03-25 13:26 ` Bruce Ashfield
@ 2015-03-25 13:52 ` Richard Purdie
0 siblings, 0 replies; 61+ messages in thread
From: Richard Purdie @ 2015-03-25 13:52 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: Patches and discussions about the oe-core layer
On Wed, 2015-03-25 at 09:26 -0400, Bruce Ashfield wrote:
> On Wed, Mar 25, 2015 at 8:13 AM, Bruce Ashfield
> <bruce.ashfield@gmail.com> wrote:
> > On Wed, Mar 25, 2015 at 5:26 AM, Richard Purdie
> > <richard.purdie@linuxfoundation.org> wrote:
> >> On Tue, 2015-03-24 at 14:57 -0400, Bruce Ashfield wrote:
> >>> Hi all,
> >>>
> >>> Here is the latest linux-yocto consolidated pull request. It is a mix of
> >>> kernel version -stable imports (CVEs and fixes), kernel configuration
> >>> changes, a documentation update and kernel configuration enhancement.
> >>>
> >>> The -stable updates are routine, and I build/boot tested them here
> >>> (with my fixup commits being evidence). These are ready for a round of
> >>> autobuilder/soak testing.
> >>
> >> Something in here broke lttng-modules causing cascades of failures on
> >> the autobuilder so I've updated it to the latest code on the 2.6 stable
> >> branch and am retesting.
> >
> > Gah. I built and booted here, but can't think of any reason why that didn't
> > trigger and fail here.
> >
> > I've started my own build as well, with a completely clean starting point.
>
> and sure enough, it blows up on my clean build.
>
> If your update doesn't resolve this, ping me and I'll take care of the fix.
It seemed to work, we've merged everything to master and branched for
the release. Release build now in progress so we'll see... :)
Cheers,
Richard
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-03-25 12:13 ` Bruce Ashfield
@ 2015-03-25 13:26 ` Bruce Ashfield
2015-03-25 13:52 ` Richard Purdie
0 siblings, 1 reply; 61+ messages in thread
From: Bruce Ashfield @ 2015-03-25 13:26 UTC (permalink / raw)
To: Richard Purdie; +Cc: Patches and discussions about the oe-core layer
On Wed, Mar 25, 2015 at 8:13 AM, Bruce Ashfield
<bruce.ashfield@gmail.com> wrote:
> On Wed, Mar 25, 2015 at 5:26 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>> On Tue, 2015-03-24 at 14:57 -0400, Bruce Ashfield wrote:
>>> Hi all,
>>>
>>> Here is the latest linux-yocto consolidated pull request. It is a mix of
>>> kernel version -stable imports (CVEs and fixes), kernel configuration
>>> changes, a documentation update and kernel configuration enhancement.
>>>
>>> The -stable updates are routine, and I build/boot tested them here
>>> (with my fixup commits being evidence). These are ready for a round of
>>> autobuilder/soak testing.
>>
>> Something in here broke lttng-modules causing cascades of failures on
>> the autobuilder so I've updated it to the latest code on the 2.6 stable
>> branch and am retesting.
>
> Gah. I built and booted here, but can't think of any reason why that didn't
> trigger and fail here.
>
> I've started my own build as well, with a completely clean starting point.
and sure enough, it blows up on my clean build.
If your update doesn't resolve this, ping me and I'll take care of the fix.
Bruce
>
> Bruce
>
>>
>> Cheers,
>>
>> Richard
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end"
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-03-25 9:26 ` Richard Purdie
@ 2015-03-25 12:13 ` Bruce Ashfield
2015-03-25 13:26 ` Bruce Ashfield
0 siblings, 1 reply; 61+ messages in thread
From: Bruce Ashfield @ 2015-03-25 12:13 UTC (permalink / raw)
To: Richard Purdie; +Cc: Patches and discussions about the oe-core layer
On Wed, Mar 25, 2015 at 5:26 AM, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> On Tue, 2015-03-24 at 14:57 -0400, Bruce Ashfield wrote:
>> Hi all,
>>
>> Here is the latest linux-yocto consolidated pull request. It is a mix of
>> kernel version -stable imports (CVEs and fixes), kernel configuration
>> changes, a documentation update and kernel configuration enhancement.
>>
>> The -stable updates are routine, and I build/boot tested them here
>> (with my fixup commits being evidence). These are ready for a round of
>> autobuilder/soak testing.
>
> Something in here broke lttng-modules causing cascades of failures on
> the autobuilder so I've updated it to the latest code on the 2.6 stable
> branch and am retesting.
Gah. I built and booted here, but can't think of any reason why that didn't
trigger and fail here.
I've started my own build as well, with a completely clean starting point.
Bruce
>
> Cheers,
>
> Richard
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2015-03-24 18:57 Bruce Ashfield
@ 2015-03-25 9:26 ` Richard Purdie
2015-03-25 12:13 ` Bruce Ashfield
0 siblings, 1 reply; 61+ messages in thread
From: Richard Purdie @ 2015-03-25 9:26 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: openembedded-core
On Tue, 2015-03-24 at 14:57 -0400, Bruce Ashfield wrote:
> Hi all,
>
> Here is the latest linux-yocto consolidated pull request. It is a mix of
> kernel version -stable imports (CVEs and fixes), kernel configuration
> changes, a documentation update and kernel configuration enhancement.
>
> The -stable updates are routine, and I build/boot tested them here
> (with my fixup commits being evidence). These are ready for a round of
> autobuilder/soak testing.
Something in here broke lttng-modules causing cascades of failures on
the autobuilder so I've updated it to the latest code on the 2.6 stable
branch and am retesting.
Cheers,
Richard
^ permalink raw reply [flat|nested] 61+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2015-03-24 18:57 Bruce Ashfield
2015-03-25 9:26 ` Richard Purdie
0 siblings, 1 reply; 61+ messages in thread
From: Bruce Ashfield @ 2015-03-24 18:57 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core
Hi all,
Here is the latest linux-yocto consolidated pull request. It is a mix of
kernel version -stable imports (CVEs and fixes), kernel configuration
changes, a documentation update and kernel configuration enhancement.
The -stable updates are routine, and I build/boot tested them here
(with my fixup commits being evidence). These are ready for a round of
autobuilder/soak testing.
The only other change is the addition of the ability to use a defconfig
that is maintained within a kernel tree. This enhacement request came
from the raspberrypi2 maintainers. We went through a few revisions and
test cycles on this (see YOCTO: 7474 for the details).
The final result has no impact on existing configuration workflows, but
does allow an in-tree config to be copied out into WORKDIR and then
incorporated with other fragments as part of kconfig processing. A new
variable is introduced for specifying the defconfig KBUILD_DEFCONFIG,
and I'll work with Scott to make sure this is documented in the
appropriate locations.
Cheers,
Bruce
The following changes since commit 369932178fe9e7aa4a6d0e2ef1e2e539be701d02:
yocto-bsp: Update templates to 3.19 kernel (2015-03-24 10:06:03 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
kernel-yocto: allow in-tree defconfigs
linux-yocto/3.19: configuration updates and stable import
linux-yocto/3.14: integrate korg stable and meta data changes
linux-yocto/3.19: fixes for Intel core warnings
skeleton: clarify linux-yocto-custom workflow
.../recipes-kernel/linux/linux-yocto-custom.bb | 6 ++--
meta/classes/kernel-yocto.bbclass | 39 ++++++++++++++++++++--
meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb | 8 ++---
meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 6 ++--
meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb | 6 ++--
meta/recipes-kernel/linux/linux-yocto_3.14.bb | 20 +++++------
meta/recipes-kernel/linux/linux-yocto_3.19.bb | 20 +++++------
7 files changed, 69 insertions(+), 36 deletions(-)
--
2.1.0
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2012-02-05 6:31 Bruce Ashfield
@ 2012-02-08 4:09 ` Saul Wold
0 siblings, 0 replies; 61+ messages in thread
From: Saul Wold @ 2012-02-08 4:09 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer; +Cc: dvhart
On 02/04/2012 10:31 PM, Bruce Ashfield wrote:
> Richard/Saul,
>
> This is a follow on to the 3.2 tree and src_patches changes that I sent
> last week.
>
> The ability to specify out of tree BSPs via single .scc files is not
> possible, as well as any automatic BSPs following the naming conventions
> of the 3.2 tree.
>
> The meta branch changes are routine, with the exception being that I got
> a report that 3.0 -rt wasn't patching. That report turned out to be true,
> and I've fixed it here.
>
> Cheers,
>
> Bruce
>
> The following changes since commit cb89d43473a91ff4cb2447d642fcd9308d7366e3:
>
> libzypp: add missing runtime dependences on gzip and gnupg (2012-02-03 17:23:34 +0000)
>
> are available in the git repository at:
> git://git.pokylinux.org/poky-contrib zedd/kernel
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Bruce Ashfield (5):
> linux-yocto: locate and use out of tree features specified on the
> SRC_URI
> linux-yocto: meta updates for sys940x and cleanup
> linux-yocto: rt compiliation fix
> kern-tools: remove explicit 'yocto' references from auto-bsp handling
> linux-yocto: fri2: use emgd-1.10
>
> meta/classes/kernel-yocto.bbclass | 21 ++++++++++++++++++++
> .../kern-tools/kern-tools-native_git.bb | 2 +-
> meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb | 2 +-
> meta/recipes-kernel/linux/linux-yocto_3.0.bb | 2 +-
> meta/recipes-kernel/linux/linux-yocto_3.2.bb | 2 +-
> 5 files changed, 25 insertions(+), 4 deletions(-)
>
Merged into OE-core with updated patch set
Thanks
Sau!
^ permalink raw reply [flat|nested] 61+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2012-02-05 6:31 Bruce Ashfield
2012-02-08 4:09 ` Saul Wold
0 siblings, 1 reply; 61+ messages in thread
From: Bruce Ashfield @ 2012-02-05 6:31 UTC (permalink / raw)
To: richard.purdie; +Cc: dvhart, openembedded-core, saul.wold
Richard/Saul,
This is a follow on to the 3.2 tree and src_patches changes that I sent
last week.
The ability to specify out of tree BSPs via single .scc files is not
possible, as well as any automatic BSPs following the naming conventions
of the 3.2 tree.
The meta branch changes are routine, with the exception being that I got
a report that 3.0 -rt wasn't patching. That report turned out to be true,
and I've fixed it here.
Cheers,
Bruce
The following changes since commit cb89d43473a91ff4cb2447d642fcd9308d7366e3:
libzypp: add missing runtime dependences on gzip and gnupg (2012-02-03 17:23:34 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto: locate and use out of tree features specified on the
SRC_URI
linux-yocto: meta updates for sys940x and cleanup
linux-yocto: rt compiliation fix
kern-tools: remove explicit 'yocto' references from auto-bsp handling
linux-yocto: fri2: use emgd-1.10
meta/classes/kernel-yocto.bbclass | 21 ++++++++++++++++++++
.../kern-tools/kern-tools-native_git.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_3.0.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_3.2.bb | 2 +-
5 files changed, 25 insertions(+), 4 deletions(-)
--
1.7.4.1
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2012-01-11 18:52 Bruce Ashfield
@ 2012-01-17 19:28 ` Saul Wold
0 siblings, 0 replies; 61+ messages in thread
From: Saul Wold @ 2012-01-17 19:28 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
On 01/11/2012 10:52 AM, Bruce Ashfield wrote:
> Richard/Saul,
>
> Since this is a stabilization week, this probably can't be merged
> immediately, but I've been working with this enough to call it
> good enough, and me sitting on them longer doesn't help.
>
> The first change in this series is the switch of qemuppc from prep to
> mac99. With this, we'll close a whole set of issues (slow bootup) and
> close a feature gap that has existed for a while.
>
> I'm seeing a bit of strangeness with the mouse in my sato testing,
> but that's about it. Liming hasn't seen the same issues, so getting
> this into the tree will allow us to incrementally improve and debug
> this.
>
> The second change is a SRCREV update pulls in the forward looking
> fix from Khem and a fix from Zumeng that fixes a failed ltp/mm test
> that was found on the routerstationpro.
>
> Cheers,
>
> Bruce
>
> cc: Khem Raj<raj.khem@gmail.com>
> cc: Zumeng Chen<zumeng.chen@windriver.com>
> cc: Liming Wang<liming.wang@windriver.com>
>
> The following changes since commit 18c88fcec85f96d2495457928be913807971aea7:
>
> package.bbclass: per recipe PRSERV_HOST support (2012-01-11 10:37:43 +0000)
>
> are available in the git repository at:
> git://git.pokylinux.org/poky-contrib zedd/kernel
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Bruce Ashfield (1):
> linux-yocto: consolidated fix SRCREV updates
>
> Liming Wang (4):
> qemuppc: replace emulation of qemuppc from prep to mac99
> qemuppc: add pointercal file
> qemuppc: add machconfig
> tslib: enable big endian support for qemuppc
>
> meta/conf/machine/qemuppc.conf | 2 +-
> .../formfactor/files/qemuppc/machconfig | 10 ++++++++++
> .../pointercal/files/qemuppc/pointercal | Bin 0 -> 36 bytes
> meta/recipes-graphics/tslib/tslib_1.0.bb | 1 +
> meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb | 6 +++---
> meta/recipes-kernel/linux/linux-yocto_3.0.bb | 15 ++++++++-------
> scripts/runqemu | 7 +------
> scripts/runqemu-internal | 16 ++++++++--------
> 8 files changed, 32 insertions(+), 25 deletions(-)
> create mode 100755 meta/recipes-bsp/formfactor/files/qemuppc/machconfig
> create mode 100644 meta/recipes-bsp/pointercal/files/qemuppc/pointercal
>
Merged into OE-Core
Thanks
Sau!
^ permalink raw reply [flat|nested] 61+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2012-01-11 18:52 Bruce Ashfield
2012-01-17 19:28 ` Saul Wold
0 siblings, 1 reply; 61+ messages in thread
From: Bruce Ashfield @ 2012-01-11 18:52 UTC (permalink / raw)
To: richard.purdie; +Cc: openembedded-core, saul.wold
Richard/Saul,
Since this is a stabilization week, this probably can't be merged
immediately, but I've been working with this enough to call it
good enough, and me sitting on them longer doesn't help.
The first change in this series is the switch of qemuppc from prep to
mac99. With this, we'll close a whole set of issues (slow bootup) and
close a feature gap that has existed for a while.
I'm seeing a bit of strangeness with the mouse in my sato testing,
but that's about it. Liming hasn't seen the same issues, so getting
this into the tree will allow us to incrementally improve and debug
this.
The second change is a SRCREV update pulls in the forward looking
fix from Khem and a fix from Zumeng that fixes a failed ltp/mm test
that was found on the routerstationpro.
Cheers,
Bruce
cc: Khem Raj <raj.khem@gmail.com>
cc: Zumeng Chen <zumeng.chen@windriver.com>
cc: Liming Wang <liming.wang@windriver.com>
The following changes since commit 18c88fcec85f96d2495457928be913807971aea7:
package.bbclass: per recipe PRSERV_HOST support (2012-01-11 10:37:43 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (1):
linux-yocto: consolidated fix SRCREV updates
Liming Wang (4):
qemuppc: replace emulation of qemuppc from prep to mac99
qemuppc: add pointercal file
qemuppc: add machconfig
tslib: enable big endian support for qemuppc
meta/conf/machine/qemuppc.conf | 2 +-
.../formfactor/files/qemuppc/machconfig | 10 ++++++++++
.../pointercal/files/qemuppc/pointercal | Bin 0 -> 36 bytes
meta/recipes-graphics/tslib/tslib_1.0.bb | 1 +
meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto_3.0.bb | 15 ++++++++-------
scripts/runqemu | 7 +------
scripts/runqemu-internal | 16 ++++++++--------
8 files changed, 32 insertions(+), 25 deletions(-)
create mode 100755 meta/recipes-bsp/formfactor/files/qemuppc/machconfig
create mode 100644 meta/recipes-bsp/pointercal/files/qemuppc/pointercal
--
1.7.4.1
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2011-01-10 17:30 Bruce Ashfield
2011-01-10 21:05 ` Richard Purdie
@ 2011-01-13 6:01 ` Saul Wold
1 sibling, 0 replies; 61+ messages in thread
From: Saul Wold @ 2011-01-13 6:01 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: yocto, poky
On 01/10/2011 09:30 AM, Bruce Ashfield wrote:
> It looks like some of my last pull request didn't make it
> to master, so I've repeated it here. Patches 4/5 have already
> been sent:
>
> kernel-yocto: pass the build directory to configme
> routerstation: disable command line overrides
>
> The remaining three changes are new and are:
>
> - A merge from Darren to update the default 2.6.37 configs
> to enable the debug/ftrace configs we need.
>
> - A change to make board descriptions generic. These are
> transparent to nearly everyone, but any new BSPs will be
> described with: KARCH, KMACHINE and KTYPE which are more
> generic variables and used internally during kernel
> configuration. They are differnet from yocto/poky variables
> on purpose, since the kernel tree can be cloned and used
> distinctly from any build system.
>
> - And finally an update to 2.6.37 with a port of the alternate
> RPC ports patch which reinstates usermode NFS support to
> 2.6.37.
>
> Also out of interest, the routerstation pro and fsl-mpc8315e-rdb
> have all been booted against 2.6.37 and will follow shortly.
> Next up are feature merges (lttng, etc) to match the -stable
> kernel functionality.
>
> Cheers,
>
> Bruce
>
>
> 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 (5):
> kernel-yocto: pass the build directory to configme
> routerstation: disable command line overrides
> linux-yocto: update SRCREV to pickup debug/ftrace config changes
> kern-tools: create generic variables for platform/board/kernel
> linux-yocto: update to 2.6.37
>
> meta/classes/kernel-yocto.bbclass | 2 +-
> .../conf/distro/include/poky-default-revisions.inc | 28 ++++++++++----------
> 2 files changed, 15 insertions(+), 15 deletions(-)
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>
Everything got pulled this time
In Master now
Thanks
Sau!
^ permalink raw reply [flat|nested] 61+ messages in thread
* Re: [PATCH 0/5] linux-yocto: consolidated pull request
2011-01-10 17:30 Bruce Ashfield
@ 2011-01-10 21:05 ` Richard Purdie
2011-01-13 6:01 ` Saul Wold
1 sibling, 0 replies; 61+ messages in thread
From: Richard Purdie @ 2011-01-10 21:05 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: yocto, poky, saul.wold
On Mon, 2011-01-10 at 12:30 -0500, Bruce Ashfield wrote:
> It looks like some of my last pull request didn't make it
> to master, so I've repeated it here. Patches 4/5 have already
> been sent:
>
> kernel-yocto: pass the build directory to configme
> routerstation: disable command line overrides
>
> The remaining three changes are new and are:
>
> - A merge from Darren to update the default 2.6.37 configs
> to enable the debug/ftrace configs we need.
>
> - A change to make board descriptions generic. These are
> transparent to nearly everyone, but any new BSPs will be
> described with: KARCH, KMACHINE and KTYPE which are more
> generic variables and used internally during kernel
> configuration. They are differnet from yocto/poky variables
> on purpose, since the kernel tree can be cloned and used
> distinctly from any build system.
>
> - And finally an update to 2.6.37 with a port of the alternate
> RPC ports patch which reinstates usermode NFS support to
> 2.6.37.
>
> Also out of interest, the routerstation pro and fsl-mpc8315e-rdb
> have all been booted against 2.6.37 and will follow shortly.
> Next up are feature merges (lttng, etc) to match the -stable
> kernel functionality.
Merged into master, thanks!
Richard
^ permalink raw reply [flat|nested] 61+ messages in thread
* [PATCH 0/5] linux-yocto: consolidated pull request
@ 2011-01-10 17:30 Bruce Ashfield
2011-01-10 21:05 ` Richard Purdie
2011-01-13 6:01 ` Saul Wold
0 siblings, 2 replies; 61+ messages in thread
From: Bruce Ashfield @ 2011-01-10 17:30 UTC (permalink / raw)
To: rpurdie; +Cc: yocto, poky, saul.wold
It looks like some of my last pull request didn't make it
to master, so I've repeated it here. Patches 4/5 have already
been sent:
kernel-yocto: pass the build directory to configme
routerstation: disable command line overrides
The remaining three changes are new and are:
- A merge from Darren to update the default 2.6.37 configs
to enable the debug/ftrace configs we need.
- A change to make board descriptions generic. These are
transparent to nearly everyone, but any new BSPs will be
described with: KARCH, KMACHINE and KTYPE which are more
generic variables and used internally during kernel
configuration. They are differnet from yocto/poky variables
on purpose, since the kernel tree can be cloned and used
distinctly from any build system.
- And finally an update to 2.6.37 with a port of the alternate
RPC ports patch which reinstates usermode NFS support to
2.6.37.
Also out of interest, the routerstation pro and fsl-mpc8315e-rdb
have all been booted against 2.6.37 and will follow shortly.
Next up are feature merges (lttng, etc) to match the -stable
kernel functionality.
Cheers,
Bruce
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 (5):
kernel-yocto: pass the build directory to configme
routerstation: disable command line overrides
linux-yocto: update SRCREV to pickup debug/ftrace config changes
kern-tools: create generic variables for platform/board/kernel
linux-yocto: update to 2.6.37
meta/classes/kernel-yocto.bbclass | 2 +-
.../conf/distro/include/poky-default-revisions.inc | 28 ++++++++++----------
2 files changed, 15 insertions(+), 15 deletions(-)
^ permalink raw reply [flat|nested] 61+ messages in thread
end of thread, other threads:[~2023-02-01 16:28 UTC | newest]
Thread overview: 61+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-08-23 18:08 [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
2013-08-23 18:08 ` [PATCH 1/5] kern-tools: usability, bug fixes and no guilt Bruce Ashfield
2013-08-23 18:08 ` [PATCH 2/5] guilt: update to latest git version Bruce Ashfield
2013-08-23 18:08 ` [PATCH 3/5] linux-libc-headers: update to v3.10 Bruce Ashfield
2013-08-23 18:08 ` [PATCH 4/5] gst-plugins-good: fix 3.10 libc-headers build failure Bruce Ashfield
2013-08-23 18:08 ` [PATCH 5/5] linux-yocto: introduce v3.10 Bruce Ashfield
2013-08-24 0:57 ` Jonathan Liu
2013-08-24 13:36 ` Bruce Ashfield
2013-08-23 21:30 ` [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
2013-08-24 6:33 ` Saul Wold
2013-08-24 13:34 ` Bruce Ashfield
2013-08-24 13:45 ` Bruce Ashfield
2013-08-24 13:50 ` Saul Wold
2013-08-24 13:53 ` Bruce Ashfield
2013-08-24 14:47 ` Bruce Ashfield
2013-08-24 14:59 ` Bruce Ashfield
2013-08-24 16:05 ` Bruce Ashfield
-- strict thread matches above, loose matches on Subject: below --
2023-02-01 16:28 bruce.ashfield
2020-11-19 19:17 Bruce Ashfield
2020-05-29 1:29 Bruce Ashfield
2020-05-03 15:44 Bruce Ashfield
2020-05-04 8:30 ` Richard Purdie
2020-05-04 12:56 ` Bruce Ashfield
2020-03-24 23:04 Bruce Ashfield
2016-07-27 16:57 Bruce Ashfield
2016-06-21 15:20 Bruce Ashfield
2016-04-13 16:12 Bruce Ashfield
2015-05-01 1:34 Bruce Ashfield
2015-05-01 22:59 ` Richard Purdie
2015-05-01 23:30 ` Bruce Ashfield
2015-05-02 8:13 ` Martin Jansa
2015-05-03 2:50 ` Bruce Ashfield
2015-05-06 14:42 ` Martin Jansa
2015-05-06 14:58 ` Bruce Ashfield
2015-05-06 15:33 ` Martin Jansa
2015-05-06 15:44 ` Richard Purdie
2015-05-06 16:07 ` Martin Jansa
2015-05-06 17:46 ` Bruce Ashfield
2015-05-06 21:32 ` Richard Purdie
2015-05-06 22:49 ` Martin Jansa
2015-05-07 15:33 ` Bruce Ashfield
2015-05-07 6:33 ` Khem Raj
2015-05-02 9:00 ` Richard Purdie
2015-05-03 2:53 ` Bruce Ashfield
2015-05-03 3:52 ` Bruce Ashfield
2015-05-03 10:48 ` Richard Purdie
2015-05-03 21:30 ` Richard Purdie
2015-05-04 4:36 ` Bruce Ashfield
2015-05-04 15:01 ` Bruce Ashfield
2015-03-24 18:57 Bruce Ashfield
2015-03-25 9:26 ` Richard Purdie
2015-03-25 12:13 ` Bruce Ashfield
2015-03-25 13:26 ` Bruce Ashfield
2015-03-25 13:52 ` Richard Purdie
2012-02-05 6:31 Bruce Ashfield
2012-02-08 4:09 ` Saul Wold
2012-01-11 18:52 Bruce Ashfield
2012-01-17 19:28 ` Saul Wold
2011-01-10 17:30 Bruce Ashfield
2011-01-10 21:05 ` Richard Purdie
2011-01-13 6:01 ` Saul Wold
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.