[yocto] [meta-oracle-java][PATCH] Update jdk and jre to version 67
From 27a16047d97c3c49f889ccf2a89895b98eb55a39 Mon Sep 17 00:00:00 2001
From: Vladimir Redzhepov vladimir_redzhe...@epam.com
Date: Tue, 26 Aug 2014 13:22:49 +0300
Subject: [PATCH] Update jdk and jre to version 67
1. Add BUILD_NUMBER variable.
2. Change SRC_URI for all recipes.
3. Recipe cleanup - remove redundant PR = r0 from all recipes.
4. Update checksums for license files.
Signed-off-by: Vladimir Redzhepov vladimir_redzhe...@epam.com
---
recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb | 10 +-
recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb | 10 +-
recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb | 10 +-
recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb | 10 +-
recipes-devtools/oracle-java/oracle-jse.inc | 4 ++--
5 files changed, 22 insertions(+), 22 deletions(-)
diff --git a/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb
b/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb
index 978fbd5..0667161 100644
--- a/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb
+++ b/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb
@@ -1,9 +1,9 @@
-PR = r0
-PV_UPDATE = 25
+PV_UPDATE = 67
+BUILD_NUMBER = 01
require oracle-jse-jdk.inc
-SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u25-b15/jdk-7u25-linux-i586.tar.gz;
+SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u${PV_UPDATE}-b${BUILD_NUMBER}/jdk-7u${PV_UPDATE}-linux-i586.tar.gz;
-SRC_URI[md5sum] = 23176d0ebf9dedd21e3150b4bb0ee776
-SRC_URI[sha256sum] =
dd89b20afa939992bb7fdc44837fa64f0a98d7ee1e5706fe8a2d9e2247ba6de7
+SRC_URI[md5sum] = 715b0e8ba2a06bded75f6a92427e2701
+SRC_URI[sha256sum] =
b6231064ad2c9fbbcb099dba17b1dcf12033e922b9c24e4348b9a01e9ebaa85c
diff --git a/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb
b/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb
index 7979401..f18ce55 100644
--- a/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb
+++ b/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb
@@ -1,9 +1,9 @@
-PR = r0
-PV_UPDATE = 25
+PV_UPDATE = 67
+BUILD_NUMBER = 01
require oracle-jse-jdk.inc
-SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u25-b15/jdk-7u25-linux-x64.tar.gz;
+SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u${PV_UPDATE}-b${BUILD_NUMBER}/jdk-7u${PV_UPDATE}-linux-x64.tar.gz;
-SRC_URI[md5sum] = 83ba05e260813f7a9140b76e3d37ea33
-SRC_URI[sha256sum] =
f80dff0e19ca8d038cf7fe3aaa89538496b80950f4d10ff5f457988ae159b2a6
+SRC_URI[md5sum] = 81e3e2df33e13781e5fac5756ed90e67
+SRC_URI[sha256sum] =
54dd1e13edf18c64941a55da9c91210b53dc5cf48f1a8f4538c863049e346335
diff --git a/recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb
b/recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb
index 6125025..d0a9300 100644
--- a/recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb
+++ b/recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb
@@ -1,9 +1,9 @@
-PR = r0
-PV_UPDATE = 25
+PV_UPDATE = 67
+BUILD_NUMBER = 01
require oracle-jse-jre.inc
-SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u25-b15/jre-7u25-linux-i586.tar.gz;
+SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u${PV_UPDATE}-b${BUILD_NUMBER}/jre-7u${PV_UPDATE}-linux-i586.tar.gz;
-SRC_URI[md5sum] = 0e9ccefe49e937e592dbb605f2e8e7d8
-SRC_URI[sha256sum] =
4016965536d8607743267812ab04e6d428036dda432893748c1df6cb77b09628
+SRC_URI[md5sum] = 2a256eb2a91f0084e58c612636342c2b
+SRC_URI[sha256sum] =
eadec83a54d3a9d09248a8d16b21c03da9afffc7317e775fb8db962620a0781d
diff --git a/recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb
b/recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb
index 4058d23..0d5f157 100644
--- a/recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb
+++ b/recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb
@@ -1,9 +1,9 @@
-PR = r0
-PV_UPDATE = 25
+PV_UPDATE = 67
+BUILD_NUMBER = 01
require oracle-jse-jre.inc
-SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u25-b15/jre-7u25-linux-x64.tar.gz;
+SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u${PV_UPDATE}-b${BUILD_NUMBER}/jre-7u${PV_UPDATE}-linux-x64.tar.gz;
-SRC_URI[md5sum] = 743ee0ebf73ce428c912866d84e374e0
-SRC_URI[sha256sum] =
3c4496316fb413d5ab0590e9971676a521b9a600b3ceaac311f04c18c98a98c0
+SRC_URI[md5sum] = 9007c79167be0177fb47e5313c53d5cb
+SRC_URI[sha256sum] =
726c37c07bb389b5b96674b7bcbc288e39fb8fbcd42369afa364a18e66248b1f
diff --git a/recipes-devtools/oracle-java/oracle-jse.inc
b/recipes-devtools/oracle-java/oracle-jse.inc
index 3a4e20d..38ceef0 100644
--- a/recipes-devtools/oracle-java/oracle-jse.inc
+++ b/recipes-devtools/oracle-java/oracle-jse.inc
@@ -2,8 +2,8 @@ LICENSE_FLAGS = oracle_java
LICENSE = Oracle_Binary_Code_License_Agreement
LIC_FILES_CHKSUM = \
file://${WORKDIR}/${JDK_JRE}${PV}_${PV_UPDATE}/LICENSE;md5=98f46ab6481d87c4d77e0e91a6dbc15f
\
-
Re: [yocto] [meta-oracle-java][PATCH] Update jdk and jre to version 67
On Tue, Aug 26, 2014 at 10:39:43AM +, Vladimir Redzhepov wrote:
From 27a16047d97c3c49f889ccf2a89895b98eb55a39 Mon Sep 17 00:00:00 2001
From: Vladimir Redzhepov vladimir_redzhe...@epam.com
Date: Tue, 26 Aug 2014 13:22:49 +0300
Subject: [PATCH] Update jdk and jre to version 67
1. Add BUILD_NUMBER variable.
2. Change SRC_URI for all recipes.
3. Recipe cleanup - remove redundant PR = r0 from all recipes.
4. Update checksums for license files.
Signed-off-by: Vladimir Redzhepov vladimir_redzhe...@epam.com
---
recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb | 10 +-
recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb | 10 +-
recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb | 10 +-
recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb | 10 +-
recipes-devtools/oracle-java/oracle-jse.inc | 4 ++--
5 files changed, 22 insertions(+), 22 deletions(-)
diff --git a/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb
b/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb
index 978fbd5..0667161 100644
--- a/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb
+++ b/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb
@@ -1,9 +1,9 @@
-PR = r0
-PV_UPDATE = 25
+PV_UPDATE = 67
+BUILD_NUMBER = 01
require oracle-jse-jdk.inc
-SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u25-b15/jdk-7u25-linux-i586.tar.gz;
+SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u${PV_UPDATE}-b${BUILD_NUMBER}/jdk-7u${PV_UPDATE}-linux-i586.tar.gz;
-SRC_URI[md5sum] = 23176d0ebf9dedd21e3150b4bb0ee776
-SRC_URI[sha256sum] =
dd89b20afa939992bb7fdc44837fa64f0a98d7ee1e5706fe8a2d9e2247ba6de7
+SRC_URI[md5sum] = 715b0e8ba2a06bded75f6a92427e2701
+SRC_URI[sha256sum] =
b6231064ad2c9fbbcb099dba17b1dcf12033e922b9c24e4348b9a01e9ebaa85c
diff --git a/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb
b/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb
index 7979401..f18ce55 100644
--- a/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb
+++ b/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb
@@ -1,9 +1,9 @@
-PR = r0
-PV_UPDATE = 25
+PV_UPDATE = 67
+BUILD_NUMBER = 01
require oracle-jse-jdk.inc
-SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u25-b15/jdk-7u25-linux-x64.tar.gz;
+SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u${PV_UPDATE}-b${BUILD_NUMBER}/jdk-7u${PV_UPDATE}-linux-x64.tar.gz;
-SRC_URI[md5sum] = 83ba05e260813f7a9140b76e3d37ea33
-SRC_URI[sha256sum] =
f80dff0e19ca8d038cf7fe3aaa89538496b80950f4d10ff5f457988ae159b2a6
+SRC_URI[md5sum] = 81e3e2df33e13781e5fac5756ed90e67
+SRC_URI[sha256sum] =
54dd1e13edf18c64941a55da9c91210b53dc5cf48f1a8f4538c863049e346335
diff --git a/recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb
b/recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb
index 6125025..d0a9300 100644
--- a/recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb
+++ b/recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb
@@ -1,9 +1,9 @@
-PR = r0
-PV_UPDATE = 25
+PV_UPDATE = 67
+BUILD_NUMBER = 01
require oracle-jse-jre.inc
-SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u25-b15/jre-7u25-linux-i586.tar.gz;
+SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u${PV_UPDATE}-b${BUILD_NUMBER}/jre-7u${PV_UPDATE}-linux-i586.tar.gz;
-SRC_URI[md5sum] = 0e9ccefe49e937e592dbb605f2e8e7d8
-SRC_URI[sha256sum] =
4016965536d8607743267812ab04e6d428036dda432893748c1df6cb77b09628
+SRC_URI[md5sum] = 2a256eb2a91f0084e58c612636342c2b
+SRC_URI[sha256sum] =
eadec83a54d3a9d09248a8d16b21c03da9afffc7317e775fb8db962620a0781d
diff --git a/recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb
b/recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb
index 4058d23..0d5f157 100644
--- a/recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb
+++ b/recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb
@@ -1,9 +1,9 @@
-PR = r0
-PV_UPDATE = 25
+PV_UPDATE = 67
+BUILD_NUMBER = 01
require oracle-jse-jre.inc
-SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u25-b15/jre-7u25-linux-x64.tar.gz;
+SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u${PV_UPDATE}-b${BUILD_NUMBER}/jre-7u${PV_UPDATE}-linux-x64.tar.gz;
-SRC_URI[md5sum] = 743ee0ebf73ce428c912866d84e374e0
-SRC_URI[sha256sum] =
3c4496316fb413d5ab0590e9971676a521b9a600b3ceaac311f04c18c98a98c0
+SRC_URI[md5sum] = 9007c79167be0177fb47e5313c53d5cb
+SRC_URI[sha256sum] =
726c37c07bb389b5b96674b7bcbc288e39fb8fbcd42369afa364a18e66248b1f
diff --git a/recipes-devtools/oracle-java/oracle-jse.inc
b/recipes-devtools/oracle-java/oracle-jse.inc
index 3a4e20d..38ceef0 100644
--- a/recipes-devtools/oracle-java/oracle-jse.inc
+++ b/recipes-devtools/oracle-java/oracle-jse.inc
@@ -2,8 +2,8 @@ LICENSE_FLAGS = oracle_java
LICENSE =
[yocto] building a hierarchical poky variable glossary, noting what's missing
g'day, eh? for my own benefit (that is, for the sake of my upcoming
yocto project courses), i'm starting a topic-based poky variable
glossary, just so i can quickly display all of the variables related
to a particular topic.
i know there's *some* of that in the ref manual here:
http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#ref-varlocality
but i'm interested in a much more complete list and, more importantly,
i want to add chunks of code or explanations where i think it's
useful. i started one of those a while back, but i'm updating it now
and it's here (ignore everything below - OLD CONTENT, TO BE
DELETED -):
http://www.crashcourse.ca/wiki/index.php/Poky_Variable_Glossary
and here are a couple features i'm adding that might be of interest to
other doc writers (like scott rifenbark).
first, as i add more sections and variables, each variable will be
represented by a link to the (in-progress) ref manual entry, just so i
can take advantage of what already exists, so that's no big deal.
next, in some cases, it's informative to grab some code or output
from grep to accompany the variable reference, such as what i do here
for the PARALLEL_MAKE* variables, just to show how they're being
used:
http://www.crashcourse.ca/wiki/index.php/Poky_Variable_Glossary#General_build_variables
this makes it really easy during class to show what some variables are
doing, and how to use them.
finally, i can also note which variables aren't currently documented
in either the ref manual or in the meta/conf/documentation.conf file,
since that takes little extra time.
here's an example documenting the variables that affect the final
size of the rootfs image:
http://www.crashcourse.ca/wiki/index.php/Poky_Variable_Glossary#Final_rootfs.2Fimage_size
first, as you can see, in some cases, it makes sense to reproduce the
code that uses all those variables so students see how they hang
together, after which i list the variables, and there are two
variations i'm using to show missing documentation.
if there's no hyperlink (as with IMAGE_ROOTFS_MAXSIZE), that means
there is no entry for that variable in the poky reference manual, so
someone is welcome to add that.
also, the string {!doc} means there's no entry for that variable
in the documentation.conf file so, once again, someone is welcome to
do something about that if they want.
finally, in some cases, it's not clear whether a variable should be
documented anywhere if it's obvious it's being used only locally in a
recipe or class and is not meant to be manipulated by the developer.
here's an example:
http://www.crashcourse.ca/wiki/index.php/Poky_Variable_Glossary#U-Boot
note in u-boot.inc the variable SPL_BINARY, then SPL_IMAGE and
SPL_SYMLINK which are calculated based on it. so which of these (if
any) deserve documentation? for now, i'm going with SPL_BINARY since
it's meant to be used by the developer (i even show show where), but
i'm leaving out the other two. it's all a judgment call.
clearly, this is a long-term project but i'll add more sections on a
regular basis and try to keep things up to date. if there's a better
way to do this, i'm open to suggestions.
rday
--
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] building a hierarchical poky variable glossary, noting what's missing
Robert,
I can see your link being referenced from the YP ref-manual to augment variable
descriptions and explanations. Also, your compilation could act as another
source of information similar to the list of other information items that
currently are shown at the front of the dev-manual.
Scott
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-
boun...@yoctoproject.org] On Behalf Of Robert P. J. Day
Sent: Tuesday, August 26, 2014 4:11 AM
To: Yocto discussion list
Subject: [yocto] building a hierarchical poky variable glossary, noting what's
missing
g'day, eh? for my own benefit (that is, for the sake of my upcoming yocto
project courses), i'm starting a topic-based poky variable glossary, just so i
can
quickly display all of the variables related to a particular topic.
i know there's *some* of that in the ref manual here:
http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#ref-
varlocality
but i'm interested in a much more complete list and, more importantly, i want
to add chunks of code or explanations where i think it's useful. i started one
of
those a while back, but i'm updating it now and it's here (ignore everything
below - OLD CONTENT, TO BE DELETED -):
http://www.crashcourse.ca/wiki/index.php/Poky_Variable_Glossary
and here are a couple features i'm adding that might be of interest to other
doc writers (like scott rifenbark).
first, as i add more sections and variables, each variable will be
represented
by a link to the (in-progress) ref manual entry, just so i can take advantage
of
what already exists, so that's no big deal.
next, in some cases, it's informative to grab some code or output from grep
to accompany the variable reference, such as what i do here for the
PARALLEL_MAKE* variables, just to show how they're being
used:
http://www.crashcourse.ca/wiki/index.php/Poky_Variable_Glossary#Genera
l_build_variables
this makes it really easy during class to show what some variables are doing,
and how to use them.
finally, i can also note which variables aren't currently documented in
either
the ref manual or in the meta/conf/documentation.conf file, since that takes
little extra time.
here's an example documenting the variables that affect the final size of the
rootfs image:
http://www.crashcourse.ca/wiki/index.php/Poky_Variable_Glossary#Final_r
ootfs.2Fimage_size
first, as you can see, in some cases, it makes sense to reproduce the code that
uses all those variables so students see how they hang together, after which i
list the variables, and there are two variations i'm using to show missing
documentation.
if there's no hyperlink (as with IMAGE_ROOTFS_MAXSIZE), that means there
is no entry for that variable in the poky reference manual, so someone is
welcome to add that.
also, the string {!doc} means there's no entry for that variable in the
documentation.conf file so, once again, someone is welcome to do
something about that if they want.
finally, in some cases, it's not clear whether a variable should be
documented
anywhere if it's obvious it's being used only locally in a recipe or class and
is
not meant to be manipulated by the developer.
here's an example:
http://www.crashcourse.ca/wiki/index.php/Poky_Variable_Glossary#U-Boot
note in u-boot.inc the variable SPL_BINARY, then SPL_IMAGE and
SPL_SYMLINK which are calculated based on it. so which of these (if
any) deserve documentation? for now, i'm going with SPL_BINARY since it's
meant to be used by the developer (i even show show where), but i'm leaving
out the other two. it's all a judgment call.
clearly, this is a long-term project but i'll add more sections on a regular
basis
and try to keep things up to date. if there's a better way to do this, i'm
open to
suggestions.
rday
--
===
=
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
===
=
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] best bet for WiFi Yocto experience?
http://www.udoo.org/downloads/ has one unofficial version with yocto. On Tue, Aug 26, 2014 at 2:27 AM, Khem Raj raj.k...@gmail.com wrote: On 14-08-25 13:53:01, Rudolf Streif wrote: Hi Pete, Please provide a recommendation for a low cost, out of the box WiFi (802.11n) experience using Yocto. Are you looking for a board that has WiFi on board? The Wandboard ( http://www.wandboard.org/) or the Cubietruck ( http://www.cubietruck.com/products/cubietruck-cubieboard3-cortex-a7-dual-core-2gb-ram-8gb-flash-with-wifi-bt-1 ) have that for example. a bit expensive but well supported in OE/YP universe https://store.gumstix.com/index.php/products/526/ -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-oracle-java][PATCH] Update jdk and jre to version 67
-Original Message-
From: Martin Jansa [mailto:martin.ja...@gmail.com]
Sent: Tuesday, August 26, 2014 2:07 PM
To: Vladimir Redzhepov
Cc: yocto@yoctoproject.org; Maxin B. John
Subject: Re: [meta-oracle-java][PATCH] Update jdk and jre to version 67
On Tue, Aug 26, 2014 at 10:39:43AM +, Vladimir Redzhepov wrote:
From 27a16047d97c3c49f889ccf2a89895b98eb55a39 Mon Sep 17 00:00:00 2001
From: Vladimir Redzhepov vladimir_redzhe...@epam.com
Date: Tue, 26 Aug 2014 13:22:49 +0300
Subject: [PATCH] Update jdk and jre to version 67
1. Add BUILD_NUMBER variable.
2. Change SRC_URI for all recipes.
3. Recipe cleanup - remove redundant PR = r0 from all recipes.
4. Update checksums for license files.
Signed-off-by: Vladimir Redzhepov vladimir_redzhe...@epam.com
---
recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb | 10 +-
recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb | 10 +-
recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb | 10 +-
recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb | 10 +-
recipes-devtools/oracle-java/oracle-jse.inc | 4 ++--
5 files changed, 22 insertions(+), 22 deletions(-)
diff --git a/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb
b/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb
index 978fbd5..0667161 100644
--- a/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb
+++ b/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb
@@ -1,9 +1,9 @@
-PR = r0
-PV_UPDATE = 25
+PV_UPDATE = 67
+BUILD_NUMBER = 01
require oracle-jse-jdk.inc
-SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u25-b15/jdk-7u25-linux-i586.tar.gz;
+SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u${PV_UPDATE}-b${BUILD_NUMBER}/jdk-7u${PV_UPDATE}-linux-i586.tar.gz;
-SRC_URI[md5sum] = 23176d0ebf9dedd21e3150b4bb0ee776
-SRC_URI[sha256sum] =
dd89b20afa939992bb7fdc44837fa64f0a98d7ee1e5706fe8a2d9e2247ba6de7
+SRC_URI[md5sum] = 715b0e8ba2a06bded75f6a92427e2701
+SRC_URI[sha256sum] =
b6231064ad2c9fbbcb099dba17b1dcf12033e922b9c24e4348b9a01e9ebaa85c
diff --git a/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb
b/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb
index 7979401..f18ce55 100644
--- a/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb
+++ b/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb
@@ -1,9 +1,9 @@
-PR = r0
-PV_UPDATE = 25
+PV_UPDATE = 67
+BUILD_NUMBER = 01
require oracle-jse-jdk.inc
-SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u25-b15/jdk-7u25-linux-x64.tar.gz;
+SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u${PV_UPDATE}-b${BUILD_NUMBER}/jdk-7u${PV_UPDATE}-linux-x64.tar.gz;
-SRC_URI[md5sum] = 83ba05e260813f7a9140b76e3d37ea33
-SRC_URI[sha256sum] =
f80dff0e19ca8d038cf7fe3aaa89538496b80950f4d10ff5f457988ae159b2a6
+SRC_URI[md5sum] = 81e3e2df33e13781e5fac5756ed90e67
+SRC_URI[sha256sum] =
54dd1e13edf18c64941a55da9c91210b53dc5cf48f1a8f4538c863049e346335
diff --git a/recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb
b/recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb
index 6125025..d0a9300 100644
--- a/recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb
+++ b/recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb
@@ -1,9 +1,9 @@
-PR = r0
-PV_UPDATE = 25
+PV_UPDATE = 67
+BUILD_NUMBER = 01
require oracle-jse-jre.inc
-SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u25-b15/jre-7u25-linux-i586.tar.gz;
+SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u${PV_UPDATE}-b${BUILD_NUMBER}/jre-7u${PV_UPDATE}-linux-i586.tar.gz;
-SRC_URI[md5sum] = 0e9ccefe49e937e592dbb605f2e8e7d8
-SRC_URI[sha256sum] =
4016965536d8607743267812ab04e6d428036dda432893748c1df6cb77b09628
+SRC_URI[md5sum] = 2a256eb2a91f0084e58c612636342c2b
+SRC_URI[sha256sum] =
eadec83a54d3a9d09248a8d16b21c03da9afffc7317e775fb8db962620a0781d
diff --git a/recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb
b/recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb
index 4058d23..0d5f157 100644
--- a/recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb
+++ b/recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb
@@ -1,9 +1,9 @@
-PR = r0
-PV_UPDATE = 25
+PV_UPDATE = 67
+BUILD_NUMBER = 01
require oracle-jse-jre.inc
-SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u25-b15/jre-7u25-linux-x64.tar.gz;
+SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u${PV_UPDATE}-b${BUILD_NUMBER}/jre-7u${PV_UPDATE}-linux-x64.tar.gz;
-SRC_URI[md5sum] = 743ee0ebf73ce428c912866d84e374e0
-SRC_URI[sha256sum] =
3c4496316fb413d5ab0590e9971676a521b9a600b3ceaac311f04c18c98a98c0
+SRC_URI[md5sum] = 9007c79167be0177fb47e5313c53d5cb
+SRC_URI[sha256sum] =
726c37c07bb389b5b96674b7bcbc288e39fb8fbcd42369afa364a18e66248b1f
diff --git a/recipes-devtools/oracle-java/oracle-jse.inc
Re: [yocto] [meta-oracle-java][PATCH] Update jdk and jre to version 67
On Tue, Aug 26, 2014 at 01:02:34PM +, Vladimir Redzhepov wrote:
-Original Message-
From: Martin Jansa [mailto:martin.ja...@gmail.com]
Sent: Tuesday, August 26, 2014 2:07 PM
To: Vladimir Redzhepov
Cc: yocto@yoctoproject.org; Maxin B. John
Subject: Re: [meta-oracle-java][PATCH] Update jdk and jre to version 67
On Tue, Aug 26, 2014 at 10:39:43AM +, Vladimir Redzhepov wrote:
From 27a16047d97c3c49f889ccf2a89895b98eb55a39 Mon Sep 17 00:00:00 2001
From: Vladimir Redzhepov vladimir_redzhe...@epam.com
Date: Tue, 26 Aug 2014 13:22:49 +0300
Subject: [PATCH] Update jdk and jre to version 67
1. Add BUILD_NUMBER variable.
2. Change SRC_URI for all recipes.
3. Recipe cleanup - remove redundant PR = r0 from all recipes.
4. Update checksums for license files.
Signed-off-by: Vladimir Redzhepov vladimir_redzhe...@epam.com
---
recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb | 10 +-
recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb | 10 +-
recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb | 10 +-
recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb | 10 +-
recipes-devtools/oracle-java/oracle-jse.inc | 4 ++--
5 files changed, 22 insertions(+), 22 deletions(-)
diff --git a/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb
b/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb
index 978fbd5..0667161 100644
--- a/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb
+++ b/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb
@@ -1,9 +1,9 @@
-PR = r0
-PV_UPDATE = 25
+PV_UPDATE = 67
+BUILD_NUMBER = 01
require oracle-jse-jdk.inc
-SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u25-b15/jdk-7u25-linux-i586.tar.gz;
+SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u${PV_UPDATE}-b${BUILD_NUMBER}/jdk-7u${PV_UPDATE}-linux-i586.tar.gz;
-SRC_URI[md5sum] = 23176d0ebf9dedd21e3150b4bb0ee776
-SRC_URI[sha256sum] =
dd89b20afa939992bb7fdc44837fa64f0a98d7ee1e5706fe8a2d9e2247ba6de7
+SRC_URI[md5sum] = 715b0e8ba2a06bded75f6a92427e2701
+SRC_URI[sha256sum] =
b6231064ad2c9fbbcb099dba17b1dcf12033e922b9c24e4348b9a01e9ebaa85c
diff --git a/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb
b/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb
index 7979401..f18ce55 100644
--- a/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb
+++ b/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb
@@ -1,9 +1,9 @@
-PR = r0
-PV_UPDATE = 25
+PV_UPDATE = 67
+BUILD_NUMBER = 01
require oracle-jse-jdk.inc
-SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u25-b15/jdk-7u25-linux-x64.tar.gz;
+SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u${PV_UPDATE}-b${BUILD_NUMBER}/jdk-7u${PV_UPDATE}-linux-x64.tar.gz;
-SRC_URI[md5sum] = 83ba05e260813f7a9140b76e3d37ea33
-SRC_URI[sha256sum] =
f80dff0e19ca8d038cf7fe3aaa89538496b80950f4d10ff5f457988ae159b2a6
+SRC_URI[md5sum] = 81e3e2df33e13781e5fac5756ed90e67
+SRC_URI[sha256sum] =
54dd1e13edf18c64941a55da9c91210b53dc5cf48f1a8f4538c863049e346335
diff --git a/recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb
b/recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb
index 6125025..d0a9300 100644
--- a/recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb
+++ b/recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb
@@ -1,9 +1,9 @@
-PR = r0
-PV_UPDATE = 25
+PV_UPDATE = 67
+BUILD_NUMBER = 01
require oracle-jse-jre.inc
-SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u25-b15/jre-7u25-linux-i586.tar.gz;
+SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u${PV_UPDATE}-b${BUILD_NUMBER}/jre-7u${PV_UPDATE}-linux-i586.tar.gz;
-SRC_URI[md5sum] = 0e9ccefe49e937e592dbb605f2e8e7d8
-SRC_URI[sha256sum] =
4016965536d8607743267812ab04e6d428036dda432893748c1df6cb77b09628
+SRC_URI[md5sum] = 2a256eb2a91f0084e58c612636342c2b
+SRC_URI[sha256sum] =
eadec83a54d3a9d09248a8d16b21c03da9afffc7317e775fb8db962620a0781d
diff --git a/recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb
b/recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb
index 4058d23..0d5f157 100644
--- a/recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb
+++ b/recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb
@@ -1,9 +1,9 @@
-PR = r0
-PV_UPDATE = 25
+PV_UPDATE = 67
+BUILD_NUMBER = 01
require oracle-jse-jre.inc
-SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u25-b15/jre-7u25-linux-x64.tar.gz;
+SRC_URI =
http://download.oracle.com/otn-pub/java/jdk/7u${PV_UPDATE}-b${BUILD_NUMBER}/jre-7u${PV_UPDATE}-linux-x64.tar.gz;
-SRC_URI[md5sum] = 743ee0ebf73ce428c912866d84e374e0
-SRC_URI[sha256sum] =
3c4496316fb413d5ab0590e9971676a521b9a600b3ceaac311f04c18c98a98c0
+SRC_URI[md5sum] =
[yocto] Yocto Bitbake Failure
Hi I'm facing the following error. Not able to figure out what is the failure cause I'm I missing any specific steps. Please support do_rootfs Host OS and architecture - -Ubuntu SMP i686/ i386 GNU/Linux Target architecture/BSP - iMX6 Sabre / meta-fsl-arm The build image - tizen-common-core-image-minimal-dev Below is the log DEBUG: Executing python function rootfs_process_ignore DEBUG: Python function rootfs_process_ignore finished DEBUG: Executing python function rootfs_runtime_mapping DEBUG: Python function rootfs_runtime_mapping finished DEBUG: Executing python function do_rootfs NOTE: configuring RPM platform settings NOTE: configuring RPM system provides NOTE: configuring RPM DB settings NOTE: configuring Smart settings NOTE: Note: adding Smart channel imx6qsabreauto (65) NOTE: Note: adding Smart channel cortexa9hf_vfp_neon_mx6 (60) NOTE: Note: adding Smart channel cortexa9hf_vfp_neon (55) NOTE: Note: adding Smart channel all (50) NOTE: adding Smart RPM DB channel NOTE: Note: configuring RPM cross-install scriptlet_wrapper NOTE: ## Generate rootfs ### NOTE: Executing '/home/sfm/YOCTO/build/tmp/sysroots/i686- linux/usr/bin/createrepo --update -q /home/sfm/YOCTO/build/tmp/deploy/rpm/cortexa9hf_vfp_neon_mx6' ... NOTE: Executing '/home/sfm/YOCTO/build/tmp/sysroots/i686- linux/usr/bin/createrepo --update -q /home/sfm/YOCTO/build/tmp/deploy/rpm/cortexa9hf_vfp_neon' ... NOTE: Executing '/home/sfm/YOCTO/build/tmp/sysroots/i686- linux/usr/bin/createrepo --update -q /home/sfm/YOCTO/build/tmp/deploy/rpm/imx6qsabreauto' ... NOTE: Executing '/home/sfm/YOCTO/build/tmp/sysroots/i686- linux/usr/bin/createrepo --update -q /home/sfm/YOCTO/build/tmp/deploy/rpm/all' ... NOTE: Installing the following packages: packagegroup-core-ssh-dropbear rpm- security-plugin user-session-units less default-ac-domains psplash weston rpm weston-common-config meta-common connman smartpm kernel-modules coreutils weston-init weston-examples pam packagegroup-core-boot mesa- megadriver libgbm weston-common-tz-launcher clutter-1.0-examples bash weston-common desktop-skin psmisc config-image packagegroup-base-extended procps locale-base-en-us locale-base-en-gb NOTE: to be installed: packagegroup-core-ssh-dropbear@all rpm-security- plugin@cortexa9hf_vfp_neon user-session-units@cortexa9hf_vfp_neon less@cortexa9hf_vfp_neon default-ac-domains@cortexa9hf_vfp_neon psplash@cortexa9hf_vfp_neon weston@cortexa9hf_vfp_neon_mx6 rpm@cortexa9hf_vfp_neon weston-common-config@cortexa9hf_vfp_neon meta- common@cortexa9hf_vfp_neon connman@cortexa9hf_vfp_neon smartpm@cortexa9hf_vfp_neon kernel-modules@imx6qsabreauto coreutils@cortexa9hf_vfp_neon weston-init@all weston- examples@cortexa9hf_vfp_neon_mx6 pam@cortexa9hf_vfp_neon packagegroup-core- boot@imx6qsabreauto mesa-megadriver@cortexa9hf_vfp_neon_mx6 libgbm@cortexa9hf_vfp_neon_mx6 weston-common-tz-launcher@cortexa9hf_vfp_neon clutter-1.0-examples@cortexa9hf_vfp_neon_mx6 bash@cortexa9hf_vfp_neon weston-common@cortexa9hf_vfp_neon desktop-skin@cortexa9hf_vfp_neon psmisc@cortexa9hf_vfp_neon config-image@cortexa9hf_vfp_neon packagegroup- base-extended@imx6qsabreauto procps@cortexa9hf_vfp_neon locale-base-en- us@cortexa9hf_vfp_neon locale-base-en-gb@cortexa9hf_vfp_neon NOTE: /home/sfm/YOCTO/build/tmp/sysroots/i686-linux/usr/bin/smart --data- dir=/home/sfm/YOCTO/build/tmp/work/imx6qsabreauto-poky-linux-gnueabi/tizen- common-core-image-minimal/1.0-r0/rootfs/var/lib/smart install -y packagegroup-core-ssh-dropbear@all rpm-security-plugin@cortexa9hf_vfp_neon user-session-units@cortexa9hf_vfp_neon less@cortexa9hf_vfp_neon default-ac- domains@cortexa9hf_vfp_neon psplash@cortexa9hf_vfp_neon weston@cortexa9hf_vfp_neon_mx6 rpm@cortexa9hf_vfp_neon weston-common- config@cortexa9hf_vfp_neon meta-common@cortexa9hf_vfp_neon connman@cortexa9hf_vfp_neon smartpm@cortexa9hf_vfp_neon kernel- modules@imx6qsabreauto coreutils@cortexa9hf_vfp_neon weston-init@all weston- examples@cortexa9hf_vfp_neon_mx6 pam@cortexa9hf_vfp_neon packagegroup-core- boot@imx6qsabreauto mesa-megadriver@cortexa9hf_vfp_neon_mx6 libgbm@cortexa9hf_vfp_neon_mx6 weston-common-tz-launcher@cortexa9hf_vfp_neon clutter-1.0-examples@cortexa9hf_vfp_neon_mx6 bash@cortexa9hf_vfp_neon weston-common@cortexa9hf_vfp_neon desktop-skin@cortexa9hf_vfp_neon psmisc@cortexa9hf_vfp_neon config-image@cortexa9hf_vfp_neon packagegroup- base-extended@imx6qsabreauto procps@cortexa9hf_vfp_neon locale-base-en- us@cortexa9hf_vfp_neon locale-base-en-gb@cortexa9hf_vfp_neon ERROR: Unable to install packages. Command '/home/sfm/YOCTO/build/tmp/sysroots/i686-linux/usr/bin/smart --data- dir=/home/sfm/YOCTO/build/tmp/work/imx6qsabreauto-poky-linux-gnueabi/tizen- common-core-image-minimal/1.0-r0/rootfs/var/lib/smart install -y packagegroup-core-ssh-dropbear@all rpm-security-plugin@cortexa9hf_vfp_neon user-session-units@cortexa9hf_vfp_neon less@cortexa9hf_vfp_neon default-ac- domains@cortexa9hf_vfp_neon psplash@cortexa9hf_vfp_neon
[yocto] [PATCH] Fix USB not mounted in file manager
Currently a USB stick gets mounted on /run/media/sdX, where X is the
letter corresponding to a certain drive. In older builds of core-image-sato
it got mounted in /media/sdX. This change made the drives to not be
displayed in graphical applications which use glib-2.0 such as the
File Manager (pcmanfm). The reason is that the gio component of glib-2.0
which handles mounts contains a function which determines if a mount
is worthy to be displayed in the UI or not. The function is called
g_unix_mount_guess_should_display().
It expects a drive to be mounted in /run/media/username/sdX, but
in the current build the username part is missing in case a root user
is authenticated in the system.
The easiest solution is to allow the display of drives mounted in the
path used by the current configuration and that is /run/media/sdX.
[YOCTO #6492]
Signed-off-by: Marius Avram marius.av...@intel.com
---
...un-media-sdX-drive-mount-if-username-root.patch | 44
meta/recipes-core/glib-2.0/glib-2.0_2.40.0.bb |2 +-
2 files changed, 45 insertions(+), 1 deletion(-)
create mode 100644
meta/recipes-core/glib-2.0/glib-2.0/allow-run-media-sdX-drive-mount-if-username-root.patch
diff --git
a/meta/recipes-core/glib-2.0/glib-2.0/allow-run-media-sdX-drive-mount-if-username-root.patch
b/meta/recipes-core/glib-2.0/glib-2.0/allow-run-media-sdX-drive-mount-if-username-root.patch
new file mode 100644
index 000..3285a54
--- /dev/null
+++
b/meta/recipes-core/glib-2.0/glib-2.0/allow-run-media-sdX-drive-mount-if-username-root.patch
@@ -0,0 +1,44 @@
+From: Marius Avram marius.av...@intel.com
+Date: Tue, 26 Aug 2014 16:31:51 +0300
+Subject: [PATCH] Allow /run/media/sdX drive mount if username root
+
+In case that the username logged in the system is root
+the drives are directly mounted in /run/media/sdX and
+not /run/media/username/sdX as the function
+g_unix_mount_guess_should_display() expects.
+
+Without this change USB stick mounts are not accesible from
+graphical applications such as the File Manager (pcmanfm).
+
+Upstream-Status: Upstream-Status: Inappropriate
+
+Signed-off-by: Marius Avram marius.av...@intel.com
+---
+ gio/gunixmounts.c |6 ++
+ 1 file changed, 6 insertions(+)
+
+diff --git a/gio/gunixmounts.c b/gio/gunixmounts.c
+index 4999354..5053f5e 100644
+--- a/gio/gunixmounts.c
b/gio/gunixmounts.c
+@@ -2131,11 +2131,17 @@ g_unix_mount_guess_should_display (GUnixMountEntry
*mount_entry)
+ /* Check /run/media/$USER/ */
+ user_name = g_get_user_name ();
+ user_name_len = strlen (user_name);
++
+ if (strncmp (mount_path, /run/media/, sizeof (/run/media/) - 1) ==
0
+ strncmp (mount_path + sizeof (/run/media/) - 1, user_name,
user_name_len) == 0
+ mount_path[sizeof (/run/media/) - 1 + user_name_len] == '/')
+ is_in_runtime_dir = TRUE;
+
++ /* Allow no username in path in /run/media if current user is root */
++ if (strcmp(user_name, root) == 0
++ strncmp (mount_path, /run/media/, sizeof(run/media)) == 0)
++is_in_runtime_dir = TRUE;
++
+ if (is_in_runtime_dir || g_str_has_prefix (mount_path, /media/))
+ {
+ char *path;
+--
+1.7.9.5
+
diff --git a/meta/recipes-core/glib-2.0/glib-2.0_2.40.0.bb
b/meta/recipes-core/glib-2.0/glib-2.0_2.40.0.bb
index ff1fb87..211bc32 100644
--- a/meta/recipes-core/glib-2.0/glib-2.0_2.40.0.bb
+++ b/meta/recipes-core/glib-2.0/glib-2.0_2.40.0.bb
@@ -12,7 +12,7 @@ SRC_URI = ${GNOME_MIRROR}/glib/${SHRT_VER}/glib-${PV}.tar.xz
\
file://run-ptest \
file://ptest-paths.patch \
file://uclibc.patch \
-
file://0001-configure.ac-Do-not-use-readlink-when-cross-compilin.patch \
+ file://allow-run-media-sdX-drive-mount-if-username-root.patch \
SRC_URI_append_class-native = file://glib-gettextize-dir.patch
--
1.7.9.5
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] USB not mounted.
I also created a bug on the gnome bugtracker, in case it is a general problem and not simply yocto related: https://bugzilla.gnome.org/show_bug.cgi?id=735447 Marius Avram (1): Fix USB not mounted in file manager ...un-media-sdX-drive-mount-if-username-root.patch | 44 meta/recipes-core/glib-2.0/glib-2.0_2.40.0.bb |2 +- 2 files changed, 45 insertions(+), 1 deletion(-) create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/allow-run-media-sdX-drive-mount-if-username-root.patch -- 1.7.9.5 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [linux-yocto] Review request 0/5: GRE Refresh [ US43662 ]
Hmm. I noticed that this is going to the wrong mailing list *after* I replied once already. This needs review, before broadcasting to the yocto list. Sorry for the noise! Cheers, Bruce On 14-08-26 05:56 AM, jianchuan.w...@windriver.com wrote: Summary: GRE Refresh Tech Review: Yang Shi Gatekeeper: Bruce Ashfield Lockdown Approval (if needed): Branch Tag: master for WRL 7 IP Statement (form link or license statement, usually automated): Crypto URL(s) (if needed): see http://wiki.wrs.com/PBUeng/LinuxProductDivisionExportProcess Parent Template (where applicable): - Impacted area Impact y/n --- --- docs/tech-pubs n tests n build system n host dependencies n RPM/packaging n toolchain n kernel codey user code n configuration filesn target configuration n Other n Applicable to Yocto/upstream n Comments (indicate scope for each y above): - 0001-gre-add-x-netns-support.patch This patch allows to switch the netns when packet is encapsulated or decapsulated. In other word, the encapsulated packet is received in a netns, where the lookup is done to find the tunnel. Once the tunnel is found, the packet is decapsulated and injecting into the corresponding interface which stands to another netns. 0002-gre-allow-changing-mac-address-when-device-is-up.patch There is no need to require forcing device down on a Ethernet GRE (gretap) tunnel to change the MAC address. 0003-ip6gre-add-x-netns-support.patch This patch allows to switch the netns when packet is encapsulated or decapsulated. In other word, the encapsulated packet is received in a netns, where the lookup is done to find the tunnel. Once the tunnel is found, the packet is decapsulated and injecting into the corresponding interface which stands to another netns. 0004-net-Generalize-checksum_init-functions.patch Create a general __skb_checksum_validate function (actually a macro) to subsume the various checksum_init functions. This function can either init the checksum, or do the full validation (logically checksum_init+skb_check_complete)-- a flag specifies if full vaidation is performed. Also, there is a flag to the function to indicate that zero checksums are allowed (to support optional UDP checksums). 0005-gre6-Call-skb_checksum_simple_validate.patch Use skb_checksum_simple_validate to verify checksum. 0001-GRE-enable-gre-feature.patch GRE: enable gre feature Added Files: None Removed Files: -- None Remaining Changes (diffstat): - include/linux/skbuff.h | 93 +++ net/ipv4/ip_gre.c | 7 --- net/ipv6/ip6_gre.c | 64 ++- 3 files changed, 130 insertions(+), 34 deletions(-) Testing Commands: - Testing gre both ipv4 and ipv6. Node A: 128.224.165.109 Node B: 128.224.165.126 The node A and node B configures For IPV4 as flows: node A: ip tunnel add grem mode gre remote 128.224.165.126 local 128.224.165.109 ttl 255 ip link set grem up ip addr add 10.10.10.1/24 dev grem node B: ip tunnel add grem mode gre remote 128.224.165.109 local 128.224.165.126 ttl 255 ip link set grem up ip addr add 10.10.10.2/24 dev grem The node A and node B configures For IPV6 as flows: node A: ip tunnel add sixbone mode sit remote 128.224.165.126 local 128.224.165.109 ttl 255 ip link set sixbone up ip addr add 3ffe:406:5:1:5:a:2:1/96 dev sixbone #ip route add 3ffe::/15 dev sixbone node B: ip tunnel add sixbone mode sit remote 128.224.165.109 local 128.224.165.126 ttl 255 ip link set sixbone up ip addr add 3ffe:406:5:1:5:a:2:2/96 dev sixbone #ip route add 3ffe::/15 dev sixbone Testing, Expected Results: -- After configuring sucessfully, ping each other is ok. Conditions of submission: - Archbuilt boot boardname - MIPS n n MIPS64n n MIPS64n32 n n ARM n n x86 n n x86_64y y intel-xeon-core PPC n n PPC64 n n SPARC64 n n Reviewer Checklist: --- [Submitters: make sure that your review doesn't trigger any checkmarks!] Your checkin has not passed review/gatekeep because (see checked entries): ___ Your RR template is generally incomplete; it has too many blank entries that
Re: [yocto] [PATCH] Fix USB not mounted in file manager
Wrong list, this should go to oe-core@. On 26 August 2014 15:24, Marius Avram marius.av...@intel.com wrote: +Upstream-Status: Upstream-Status: Inappropriate Duplicated tag, and probably wise to add (OE-specific) to inappropriate. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] cmake + qt4e in bitbake fails to detect/supply all requested qt include paths
This works with qt4 (non-embedded) when built natively, is there some
bitbake incantation I'm missing to have qt4e+cmake work? Or does qt4e
just not play nice with cmake?
Error message:
| [100%] Building CXX object CMakeFiles/kiosk-web.dir/kiosk.cc.o
|
/home/cody/obj/yocto/tmp/sysroots/x86_64-linux/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-g++
-DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -march=armv7-a
-mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a8
--sysroot=/home/cody/obj/yocto/tmp/sysroots/beaglebone -O2 -pipe -g
-feliminate-unused-debug-types -fvisibility-inlines-hidden
-fpermissive -isystem
/home/cody/obj/yocto/tmp/sysroots/x86_64-linux/usr/include/qt4
-isystem /home/cody/obj/yocto/tmp/sysroots/x86_64-linux/usr/include/qt4/QtGui
-isystem /home/cody/obj/yocto/tmp/sysroots/x86_64-linux/usr/include/qt4/QtCore
-o CMakeFiles/kiosk-web.dir/kiosk.cc.o -c
/home/cody/obj/yocto/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/kiosk-web/0.0+gitrAUTOINC+dfe3db9730-r0/git/kiosk-web/kiosk.cc
|
/home/cody/obj/yocto/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/kiosk-web/0.0+gitrAUTOINC+dfe3db9730-r0/git/kiosk-web/kiosk.cc:6:28:
fatal error: QGraphicsWebView: No such file or directory
| #include QGraphicsWebView
| ^
Relevent portion of my kiosk-web_0.1.bb file (remainder is srcs, revs,
desc, and license junk)
S = ${WORKDIR}/git/${PN}
inherit cmake qt4e
do_configure () {
cmake_do_configure
}
CMakeLists.txt:
cmake_minimum_required(VERSION 2.6)
project(kiosk-web)
find_package(Qt4 REQUIRED)
set(kiosk-web_SOURCES kiosk.cc)
set(QT_USE_QTWEBKIT 1)
include(${QT_USE_FILE})
add_definitions(${QT_DEFINITIONS})
add_executable(kiosk-web ${kiosk-web_SOURCES})
target_link_libraries(kiosk-web ${QT_LIBRARIES})
kiosk.cc :
#include QApplication
#include QGraphicsScene
#include QGraphicsView
#include QGraphicsWebView
#include QWebSettings
int main(int argc, char **argv)
{
QApplication app(argc, argv);
QGraphicsScene scene;
QGraphicsView view(scene);
view.setFrameShape(QFrame::NoFrame);
view.setVerticalScrollBarPolicy(Qt::ScrollBarAlwaysOff);
view.setHorizontalScrollBarPolicy(Qt::ScrollBarAlwaysOff);
QGraphicsWebView webview;
webview.load(QUrl(http://google.com/;));
webview.setResizesToContents(true);
scene.addItem(webview);
view.showFullScreen();
return app.exec();
}
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Remove Bluez4 and add Bluez5 in core-image-base
I am using yocto project for imx6sl evolution kit based custom board. I want to use core-image-base as basic image and put other packages on that. By default , core-image-base have Bluez4, but i want to use Bluez5. How can i remove default Bluez4 from core-image-base? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Agenda: Yocto Project Technical Team Meeting - Tuesday, August 26, 2014 8:00 AM US Pacific Time
Attendees: Armin, Stephen, Saul, Herb, Michael, Jeff, Bruce, Matthew, Alex D., Belen, Tom, Richard, Denys, Doug, Nitin, Alex V., Joe, * Opens collection - 5 min (Stephen) * Yocto Project status - 5 min (Stephen/team) https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.7_Status https://wiki.yoctoproject.org/wiki/Yocto_1.7_Schedule https://wiki.yoctoproject.org/wiki/Yocto_1.7_Features YP 1.7 M3 cutoff date is next week on 9/3. YP 1.6.2 - no driving need at this time. Accumulating patches. YP 1.5.4 - no driving need at this time. Accumulating patches. * SWAT team rotation: Ross - Cristian https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team * Opens - 10 min * Team Sharing - 10 min Richard - Due to resource issues; a few of the enhancements around developer work-flow are behind schedule on development. We will consider pushing them either into M4 or into the next major release. We want to minimize the changes in M4. Michael - Considering adding a form requesting account access. Anyone have an issue? All who commented thought this a good idea. Thanks, Stephen K. Jolley Yocto Project Program Manager INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 * Work Telephone: (503) 712-0534 *Cell:(208) 244-4460 * Email: stephen.k.jol...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Remove Bluez4 and add Bluez5 in core-image-base
On 14-08-26 20:18:36, jags gediya wrote: I am using yocto project for imx6sl evolution kit based custom board. I want to use core-image-base as basic image and put other packages on that. By default , core-image-base have Bluez4, but i want to use Bluez5. How can i remove default Bluez4 from core-image-base? PREFERRED_PROVIDER_bluez4 ?= bluez5 and have 'bluetooth' in DISTRO_FEATURES -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-freescale] Remove Bluez4 and add Bluez5 in core-image-base
On Tue, Aug 26, 2014 at 9:47 AM, Khem Raj raj.k...@gmail.com wrote: On 14-08-26 20:18:36, jags gediya wrote: I am using yocto project for imx6sl evolution kit based custom board. I want to use core-image-base as basic image and put other packages on that. By default , core-image-base have Bluez4, but i want to use Bluez5. How can i remove default Bluez4 from core-image-base? PREFERRED_PROVIDER_bluez4 ?= bluez5 and have 'bluetooth' in DISTRO_FEATURES Afaik bluez5 is not a provider of bluez4, so oe-core doesn't provide a way to swap between the two at this time. -- Christopher Larson clarson at kergoth dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-freescale] Remove Bluez4 and add Bluez5 in core-image-base
On 14-08-26 10:09:45, Christopher Larson wrote: On Tue, Aug 26, 2014 at 9:47 AM, Khem Raj raj.k...@gmail.com wrote: On 14-08-26 20:18:36, jags gediya wrote: I am using yocto project for imx6sl evolution kit based custom board. I want to use core-image-base as basic image and put other packages on that. By default , core-image-base have Bluez4, but i want to use Bluez5. How can i remove default Bluez4 from core-image-base? PREFERRED_PROVIDER_bluez4 ?= bluez5 and have 'bluetooth' in DISTRO_FEATURES ah, I thought it could since we ask for PREFERRED_PROVIDER_bluez4 may be we should have a packagegroup for bluez5 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Using uboot to boot a large uimage
I am currently attempting to boot with an initramfs built into my uimage using uboot. However, I cannot get it to boot correctly. If I make the uimage totally bare-bones, and just use core-image-minimal-initramfs, then it hangs huring init at the waiting for devices... printout. Going and gutting the init script, I can get to single user mode and it looks like the filesystem is there. I want a more full system, so I included core-image-boot and core-image-basic. I figured this would initialize better. When I do this, my uImage jumps up to ~50MB. U-boot then hangs at starting kernel... I don't think that the uimage is clobbering the device tree, because the device tree is loaded at 0x100, and the uimage is loaded at 0x8000. Any ideas? Nick Crast Associate Software Engineer Saab Sensis Corporation Phone: 315-445-5703 Email: nicholas.cr...@saabsensis.com - This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately. - -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] systemd - how do I wait for a driver to load?
I've got a service running under systemd that will only start once a kernel module has loaded and created its /dev/dvb/adaptor nodes. Unfortunately, it doesn't load until after the service has failed and gone into an error state due to too many restarts. I could fix this by increasing the restart interval, but is there a way of adding a dependancy on the kernel module? -- Chris Tapp opensou...@keylevel.com www.keylevel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Using uboot to boot a large uimage
On 14-08-26 18:41:22, Crast, Nicholas wrote: I am currently attempting to boot with an initramfs built into my uimage using uboot. However, I cannot get it to boot correctly. If I make the uimage totally bare-bones, and just use core-image-minimal-initramfs, then it hangs huring init at the waiting for devices... printout. Going and gutting the init script, I can get to single user mode and it looks like the filesystem is there. I want a more full system, so I included core-image-boot and core-image-basic. I figured this would initialize better. When I do this, my uImage jumps up to ~50MB. U-boot then hangs at starting kernel... core-image-minimal should boot you into shell console. That should have been enough I don't think that the uimage is clobbering the device tree, because the device tree is loaded at 0x100, and the uimage is loaded at 0x8000. make sure that memory is not overlapping and is initiaized -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] systemd - how do I wait for a driver to load?
You should look at ConditionPathExists= Options of systemd-units. Otherwise if udev is loading your device module, you could add the device-unit to Requires= option. Am 26.08.2014 21:52, schrieb Chris Tapp: I've got a service running under systemd that will only start once a kernel module has loaded and created its /dev/dvb/adaptor nodes. Unfortunately, it doesn't load until after the service has failed and gone into an error state due to too many restarts. I could fix this by increasing the restart interval, but is there a way of adding a dependancy on the kernel module? -- Chris Tapp opensou...@keylevel.com www.keylevel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] systemd - how do I wait for a driver to load?
On 14-08-26 20:52:58, Chris Tapp wrote: I've got a service running under systemd that will only start once a kernel module has loaded and created its /dev/dvb/adaptor nodes. Unfortunately, it doesn't load until after the service has failed and gone into an error state due to too many restarts. I could fix this by increasing the restart interval, but is there a way of adding a dependancy on the kernel module? if you module is loaded automatically on boot then dependent service could use below dependency After=systemd-modules-load.service -- Chris Tapp opensou...@keylevel.com www.keylevel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] systemd - how do I wait for a driver to load?
On 26 Aug 2014, at 21:02, Sven Ebenfeld sven.ebenf...@gmail.com wrote: You should look at ConditionPathExists= Options of systemd-units. Thanks, that looks like it would do the job. I was hoping not to hard code paths as they may change if a configuration file is changed, but... Otherwise if udev is loading your device module, you could add the device-unit to Requires= option. This sounds better. Is there an easy way to tell if udev did load the module? There's nothing obvious in the syslog. Am 26.08.2014 21:52, schrieb Chris Tapp: I've got a service running under systemd that will only start once a kernel module has loaded and created its /dev/dvb/adaptor nodes. Unfortunately, it doesn't load until after the service has failed and gone into an error state due to too many restarts. I could fix this by increasing the restart interval, but is there a way of adding a dependancy on the kernel module? -- Chris Tapp opensou...@keylevel.com www.keylevel.com -- Chris Tapp opensou...@keylevel.com www.keylevel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Using uboot to boot a large uimage
Here is what I am seeing with core-image-minimal
32612024 bytes read in 11244 ms (2.8 MiB/s)
18179 bytes read in 30 ms (590.8 KiB/s)
## Booting kernel from Legacy Image at 0010 ...
Image Name: Linux-3.12.0
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size:32611960 Bytes = 31.1 MiB
Load Address: 8000
Entry Point: 8000
## Flattened Device Tree blob at 0100
Booting using the fdt blob at 0x0100
Loading Kernel Image ... OK
OK
Loading Device Tree to 03ff8000, end 03fff702 ... OK
Starting kernel ...
If I make the uBoot image ~3 MB just using core-image-minimal-initramfs, I get
different results. Here are the relevant part of my uboot configuration:
fdtaddr=0x0100
fdtimage=/boot/socfpga_mitysom5csx.dtb
fdtimagesize=0x2000
mmcboot=setenv bootargs console=ttyS0,115200 root=${mmcroot} rw rootwait;bootm
${loadaddr} - ${fdtaddr}
mmcload=mmc rescan;${mmcloadcmd} mmc 0:${mmcloadpart} ${loadaddr}
${bootimage};${mmcloadcmd} mmc 0:${mmcloadpart} ${fdtaddr} ${fdtimage}
mmcloadcmd=ext2load
mmcloadpart=2
mmcroot=/dev/mmcblk0p2
Nick Crast
Associate Software Engineer
Saab Sensis Corporation
Phone: 315-445-5703
Email: nicholas.cr...@saabsensis.com
-Original Message-
From: Khem Raj [mailto:raj.k...@gmail.com]
Sent: Tuesday, August 26, 2014 4:01 PM
To: Crast, Nicholas
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Using uboot to boot a large uimage
On 14-08-26 18:41:22, Crast, Nicholas wrote:
I am currently attempting to boot with an initramfs built into my uimage
using uboot.
However, I cannot get it to boot correctly. If I make the uimage totally
bare-bones, and just use core-image-minimal-initramfs, then it hangs huring
init at the waiting for devices... printout. Going and gutting the init
script, I can get to single user mode and it looks like the filesystem is
there.
I want a more full system, so I included core-image-boot and
core-image-basic. I figured this would initialize better. When I do this, my
uImage jumps up to ~50MB. U-boot then hangs at starting kernel...
core-image-minimal should boot you into shell console. That should have been
enough
I don't think that the uimage is clobbering the device tree, because the
device tree is loaded at 0x100, and the uimage is loaded at 0x8000.
make sure that memory is not overlapping and is initiaized
-
This message is intended only for the addressee and may contain information
that is company confidential or privileged. Any technical data in this message
may be exported only in accordance with the U.S. International Traffic in Arms
Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15
CFR Parts 730-774). Unauthorized use is strictly prohibited and may be
unlawful. If you are not the intended recipient, or the person responsible for
delivering to the intended recipient, you should not read, copy, disclose or
otherwise use this message. If you have received this email in error, please
delete it, and advise the sender immediately.
-
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Weekly build now available.
http://autobuilder.yoctoproject.org/pub/nightly/20140826-2 bitbake 5d858e23de8b15badc3ab7f56ad5160a76a89de1 eclipse-poky-juno 26bfc407781aa185f244a47ba63120343cee4a37 eclipse-poky-kepler 4a167fd662262ebdaa3cf0d332ac0debb52d7904 meta-fsl-arm c9b88d89e862d623997402104e2d875c36664afc meta-fsl-ppc d953212ae5936a7d969d13801b0c2c1eb65cee6f meta-intel 579cd30427b0cb2941eca06bc0b0b9b1573d0e50 meta-minnow 238a45e9da8bbfff7a6af220b48c11cabd31e01c meta-qt3 3016129d90b7ac8517a5227d819f10ad417b5b45 oecore 217aa4d9802609d2c3628c8751a27a5d25900898 poky 52b788c6df9201764130ab744bf67b770b24b896 -- Elizabeth Flanagan Yocto Project Build and Release -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [linux-yocto] Review request 0/5: GRE Refresh [ US43662 ]
On 14-08-26 05:56 AM, jianchuan.w...@windriver.com wrote: Summary: GRE Refresh Tech Review: Yang Shi Gatekeeper: Bruce Ashfield Lockdown Approval (if needed): Branch Tag: master for WRL 7 IP Statement (form link or license statement, usually automated): Crypto URL(s) (if needed): see http://wiki.wrs.com/PBUeng/LinuxProductDivisionExportProcess Parent Template (where applicable): - Impacted area Impact y/n --- --- docs/tech-pubs n tests n build system n host dependencies n RPM/packaging n toolchain n kernel codey user code n configuration filesn target configuration n Other n Applicable to Yocto/upstream n Comments (indicate scope for each y above): - 0001-gre-add-x-netns-support.patch This patch allows to switch the netns when packet is encapsulated or decapsulated. In other word, the encapsulated packet is received in a netns, where the lookup is done to find the tunnel. Once the tunnel is found, the packet is decapsulated and injecting into the corresponding interface which stands to another netns. 0002-gre-allow-changing-mac-address-when-device-is-up.patch There is no need to require forcing device down on a Ethernet GRE (gretap) tunnel to change the MAC address. 0003-ip6gre-add-x-netns-support.patch This patch allows to switch the netns when packet is encapsulated or decapsulated. In other word, the encapsulated packet is received in a netns, where the lookup is done to find the tunnel. Once the tunnel is found, the packet is decapsulated and injecting into the corresponding interface which stands to another netns. 0004-net-Generalize-checksum_init-functions.patch Create a general __skb_checksum_validate function (actually a macro) to subsume the various checksum_init functions. This function can either init the checksum, or do the full validation (logically checksum_init+skb_check_complete)-- a flag specifies if full vaidation is performed. Also, there is a flag to the function to indicate that zero checksums are allowed (to support optional UDP checksums). 0005-gre6-Call-skb_checksum_simple_validate.patch Use skb_checksum_simple_validate to verify checksum. 0001-GRE-enable-gre-feature.patch GRE: enable gre feature Added Files: None Removed Files: -- None Remaining Changes (diffstat): - include/linux/skbuff.h | 93 +++ net/ipv4/ip_gre.c | 7 --- net/ipv6/ip6_gre.c | 64 ++- 3 files changed, 130 insertions(+), 34 deletions(-) Testing Commands: - Testing gre both ipv4 and ipv6. Node A: 128.224.165.109 Node B: 128.224.165.126 The node A and node B configures For IPV4 as flows: node A: ip tunnel add grem mode gre remote 128.224.165.126 local 128.224.165.109 ttl 255 ip link set grem up ip addr add 10.10.10.1/24 dev grem node B: ip tunnel add grem mode gre remote 128.224.165.109 local 128.224.165.126 ttl 255 ip link set grem up ip addr add 10.10.10.2/24 dev grem The node A and node B configures For IPV6 as flows: node A: ip tunnel add sixbone mode sit remote 128.224.165.126 local 128.224.165.109 ttl 255 ip link set sixbone up ip addr add 3ffe:406:5:1:5:a:2:1/96 dev sixbone #ip route add 3ffe::/15 dev sixbone node B: ip tunnel add sixbone mode sit remote 128.224.165.109 local 128.224.165.126 ttl 255 ip link set sixbone up ip addr add 3ffe:406:5:1:5:a:2:2/96 dev sixbone #ip route add 3ffe::/15 dev sixbone gk Bruce Testing, Expected Results: -- After configuring sucessfully, ping each other is ok. Conditions of submission: - Archbuilt boot boardname - MIPS n n MIPS64n n MIPS64n32 n n ARM n n x86 n n x86_64y y intel-xeon-core PPC n n PPC64 n n SPARC64 n n Reviewer Checklist: --- [Submitters: make sure that your review doesn't trigger any checkmarks!] Your checkin has not passed review/gatekeep because (see checked entries): ___ Your RR template is generally incomplete; it has too many blank entries that need proper data filled in. ___ You've not properly listed things in the proper sections from the perspective of the SCM for new, removed, and changed files ___ You have
Re: [linux-yocto] [PATCH] Meta: add qemuppc64 bsp config
On 14-08-26 11:05 AM, Armin Kuster wrote: This is the initial meta data for qemu ppc64 bsp that supports the IBM pseries power* arch with is supported in Qemu. Thanks for the patch .. see below for some comments. Yes, its not pretty but it works. Do you have a bootlog capture ? And a list of supported features ? Signed-off-by: Armin Kuster akuster...@gmail.com --- .../bsp/qemu-ppc64/qemu-ppc64-standard.scc |8 + .../cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg | 2778 .../cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.scc |1 + 3 files changed, 2787 insertions(+) create mode 100644 meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc create mode 100644 meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg create mode 100644 meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.scc diff --git a/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc new file mode 100644 index 000..bf48141 --- /dev/null +++ b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc @@ -0,0 +1,8 @@ +define KMACHINE qemuppc64 +define KTYPE standard +define KARCH powerpc + +include ktypes/standard/standard.scc +branch qemuppc + +include qemu-ppc64.scc diff --git a/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg new file mode 100644 index 000..68c3264 --- /dev/null +++ b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg @@ -0,0 +1,2778 @@ +CONFIG_PPC64=y + +# +# Processor support This looks like a deconfig capture, which is fine as a starting point. But it means that the consistency/policy of the base fragments is not being used. Are we saying that we don't know which ones are platform options ? A visual pass can prune things down quickly .. see below: +# +CONFIG_PPC_BOOK3S_64=y +# CONFIG_PPC_BOOK3E_64 is not set +CONFIG_GENERIC_CPU=y +# CONFIG_CELL_CPU is not set +# CONFIG_POWER4_CPU is not set +# CONFIG_POWER5_CPU is not set +# CONFIG_POWER6_CPU is not set +# CONFIG_POWER7_CPU is not set +CONFIG_PPC_BOOK3S=y +CONFIG_POWER3=y +CONFIG_POWER4=y +# CONFIG_TUNE_CELL is not set +CONFIG_PPC_FPU=y +CONFIG_ALTIVEC=y +CONFIG_VSX=y +# CONFIG_PPC_ICSWX is not set +CONFIG_PPC_STD_MMU=y +CONFIG_PPC_STD_MMU_64=y +CONFIG_PPC_MM_SLICES=y +CONFIG_PPC_HAVE_PMU_SUPPORT=y +CONFIG_PPC_PERF_CTRS=y +CONFIG_SMP=y +CONFIG_NR_CPUS=2048 +CONFIG_PPC_DOORBELL=y +CONFIG_CPU_BIG_ENDIAN=y +# CONFIG_CPU_LITTLE_ENDIAN is not set +CONFIG_64BIT=y +CONFIG_WORD_SIZE=64 +CONFIG_ARCH_PHYS_ADDR_T_64BIT=y +CONFIG_ARCH_DMA_ADDR_T_64BIT=y +CONFIG_MMU=y +CONFIG_HAVE_SETUP_PER_CPU_AREA=y +CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y +CONFIG_NR_IRQS=512 +CONFIG_STACKTRACE_SUPPORT=y +CONFIG_HAVE_LATENCYTOP_SUPPORT=y +CONFIG_TRACE_IRQFLAGS_SUPPORT=y +CONFIG_LOCKDEP_SUPPORT=y +CONFIG_RWSEM_XCHGADD_ALGORITHM=y +CONFIG_ARCH_HAS_ILOG2_U32=y +CONFIG_ARCH_HAS_ILOG2_U64=y +CONFIG_GENERIC_HWEIGHT=y +CONFIG_PPC=y +# CONFIG_GENERIC_CSUM is not set +CONFIG_EARLY_PRINTK=y Things like early printk, are not in board h/w fragments. +CONFIG_PANIC_TIMEOUT=180 +CONFIG_COMPAT=y +CONFIG_SYSVIPC_COMPAT=y +CONFIG_SCHED_OMIT_FRAME_POINTER=y +CONFIG_ARCH_MAY_HAVE_PC_FDC=y +CONFIG_PPC_OF=y +CONFIG_PPC_UDBG_16550=y +# CONFIG_GENERIC_TBSYNC is not set +CONFIG_AUDIT_ARCH=y +CONFIG_GENERIC_BUG=y +CONFIG_EPAPR_BOOT=y +# CONFIG_DEFAULT_UIMAGE is not set +CONFIG_ARCH_HIBERNATION_POSSIBLE=y +CONFIG_ARCH_SUSPEND_POSSIBLE=y +# CONFIG_PPC_DCR_NATIVE is not set +# CONFIG_PPC_DCR_MMIO is not set +# CONFIG_PPC_OF_PLATFORM_PCI is not set +CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y +CONFIG_ARCH_SUPPORTS_UPROBES=y +CONFIG_PPC_EMULATE_SSTEP=y +CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config +CONFIG_IRQ_WORK=y + +# +# General setup +# +CONFIG_INIT_ENV_ARG_LIMIT=32 +CONFIG_CROSS_COMPILE= +# CONFIG_COMPILE_TEST is not set +CONFIG_LOCALVERSION= +CONFIG_LOCALVERSION_AUTO=y +CONFIG_DEFAULT_HOSTNAME=(none) +CONFIG_SWAP=y +CONFIG_SYSVIPC=y +CONFIG_SYSVIPC_SYSCTL=y +CONFIG_POSIX_MQUEUE=y +CONFIG_POSIX_MQUEUE_SYSCTL=y +# CONFIG_FHANDLE is not set +CONFIG_AUDIT=y +CONFIG_AUDITSYSCALL=y +CONFIG_AUDIT_WATCH=y +CONFIG_AUDIT_TREE=y The above block are all non-hw options. + +# +# IRQ subsystem +# +CONFIG_GENERIC_IRQ_SHOW=y +CONFIG_GENERIC_IRQ_SHOW_LEVEL=y +CONFIG_IRQ_DOMAIN=y +CONFIG_IRQ_DOMAIN_DEBUG=y +CONFIG_IRQ_FORCED_THREADING=y +CONFIG_SPARSE_IRQ=y +CONFIG_GENERIC_TIME_VSYSCALL_OLD=y +CONFIG_GENERIC_CLOCKEVENTS=y +CONFIG_GENERIC_CLOCKEVENTS_BUILD=y +CONFIG_GENERIC_CMOS_UPDATE=y + +# +# Timers subsystem +# +CONFIG_TICK_ONESHOT=y +CONFIG_NO_HZ_COMMON=y +# CONFIG_HZ_PERIODIC is not set +CONFIG_NO_HZ_IDLE=y +# CONFIG_NO_HZ_FULL is not set +CONFIG_NO_HZ=y +CONFIG_HIGH_RES_TIMERS=y + +# +# CPU/Task time and stats accounting +# +CONFIG_VIRT_CPU_ACCOUNTING=y +# CONFIG_TICK_CPU_ACCOUNTING is not set +CONFIG_VIRT_CPU_ACCOUNTING_NATIVE=y +# CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set +# CONFIG_BSD_PROCESS_ACCT is not set
[linux-yocto] [PATCH 1/5] gre: add x-netns support
From: Nicolas Dichtel nicolas.dich...@6wind.com
commit b57708add31494175be741ed3fd24023b50c3423 upstream
This patch allows to switch the netns when packet is encapsulated or
decapsulated. In other word, the encapsulated packet is received in a netns,
where the lookup is done to find the tunnel. Once the tunnel is found, the
packet is decapsulated and injecting into the corresponding interface which
stands to another netns.
When one of the two netns is removed, the tunnel is destroyed.
Signed-off-by: Nicolas Dichtel nicolas.dich...@6wind.com
Signed-off-by: David S. Miller da...@davemloft.net
Signed-off-by: Jianchuan Wang jianchuan.w...@windriver.com
---
net/ipv4/ip_gre.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/net/ipv4/ip_gre.c b/net/ipv4/ip_gre.c
index 94213c8..c5a557a 100644
--- a/net/ipv4/ip_gre.c
+++ b/net/ipv4/ip_gre.c
@@ -410,7 +410,7 @@ static int ipgre_open(struct net_device *dev)
struct flowi4 fl4;
struct rtable *rt;
- rt = ip_route_output_gre(dev_net(dev), fl4,
+ rt = ip_route_output_gre(t-net, fl4,
t-parms.iph.daddr,
t-parms.iph.saddr,
t-parms.o_key,
@@ -434,7 +434,7 @@ static int ipgre_close(struct net_device *dev)
if (ipv4_is_multicast(t-parms.iph.daddr) t-mlink) {
struct in_device *in_dev;
- in_dev = inetdev_by_index(dev_net(dev), t-mlink);
+ in_dev = inetdev_by_index(t-net, t-mlink);
if (in_dev)
ip_mc_dec_group(in_dev, t-parms.iph.daddr);
}
@@ -478,7 +478,7 @@ static void __gre_tunnel_init(struct net_device *dev)
dev-needed_headroom= LL_MAX_HEADER + sizeof(struct iphdr) + 4;
dev-mtu= ETH_DATA_LEN - sizeof(struct iphdr) - 4;
- dev-features |= NETIF_F_NETNS_LOCAL | GRE_FEATURES;
+ dev-features |= GRE_FEATURES;
dev-hw_features|= GRE_FEATURES;
if (!(tunnel-parms.o_flags TUNNEL_SEQ)) {
--
1.9.1
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH] GRE: enable gre feature.
From: Jianchuan Wang jianchuan.w...@windriver.com Signed-off-by: Jianchuan Wang jianchuan.w...@windriver.com --- meta/cfg/kernel-cache/features/gre/gre-enable.scc | 1 + meta/cfg/kernel-cache/features/gre/gre.cfg| 6 ++ 2 files changed, 7 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/gre/gre-enable.scc create mode 100644 meta/cfg/kernel-cache/features/gre/gre.cfg diff --git a/meta/cfg/kernel-cache/features/gre/gre-enable.scc b/meta/cfg/kernel-cache/features/gre/gre-enable.scc new file mode 100644 index 000..cd60fa1 --- /dev/null +++ b/meta/cfg/kernel-cache/features/gre/gre-enable.scc @@ -0,0 +1 @@ +kconf non-hardware gre.cfg diff --git a/meta/cfg/kernel-cache/features/gre/gre.cfg b/meta/cfg/kernel-cache/features/gre/gre.cfg new file mode 100644 index 000..3eff707 --- /dev/null +++ b/meta/cfg/kernel-cache/features/gre/gre.cfg @@ -0,0 +1,6 @@ +CONFIG_NET_IPGRE_DEMUX=m +CONFIG_NET_IPGRE=m +CONFIG_NET_IPGRE_BROADCAST=y +CONFIG_IPV6_GRE=m +CONFIG_OPENVSWITCH_GRE=y +# CONFIG_PPTP is not set -- 1.9.1 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 4/5] net: Generalize checksum_init functions
From: Tom Herbert therb...@google.com
commit 76ba0aae673075c77a8b775e9133c8e8b1a44563 upstream
Create a general __skb_checksum_validate function (actually a
macro) to subsume the various checksum_init functions. This
function can either init the checksum, or do the full validation
(logically checksum_init+skb_check_complete)-- a flag specifies
if full vaidation is performed. Also, there is a flag to the function
to indicate that zero checksums are allowed (to support optional
UDP checksums).
Added several stub functions for calling __skb_checksum_validate.
Signed-off-by: Tom Herbert therb...@google.com
Signed-off-by: David S. Miller da...@davemloft.net
Signed-off-by: Jianchuan Wang jianchuan.w...@windriver.com
---
include/linux/skbuff.h | 93 ++
1 file changed, 93 insertions(+)
diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
index 15ede6a..1fba79c 100644
--- a/include/linux/skbuff.h
+++ b/include/linux/skbuff.h
@@ -2686,6 +2686,99 @@ static inline __sum16 skb_checksum_complete(struct
sk_buff *skb)
0 : __skb_checksum_complete(skb);
}
+/* Check if we need to perform checksum complete validation.
+ *
+ * Returns true if checksum complete is needed, false otherwise
+ * (either checksum is unnecessary or zero checksum is allowed).
+ */
+static inline bool __skb_checksum_validate_needed(struct sk_buff *skb,
+ bool zero_okay,
+ __sum16 check)
+{
+ if (skb_csum_unnecessary(skb)) {
+ return false;
+ } else if (zero_okay !check) {
+ skb-ip_summed = CHECKSUM_UNNECESSARY;
+ return false;
+ }
+
+ return true;
+}
+
+/* For small packets = CHECKSUM_BREAK peform checksum complete directly
+ * in checksum_init.
+ */
+#define CHECKSUM_BREAK 76
+
+/* Validate (init) checksum based on checksum complete.
+ *
+ * Return values:
+ * 0: checksum is validated or try to in skb_checksum_complete. In the latter
+ * case the ip_summed will not be CHECKSUM_UNNECESSARY and the pseudo
+ * checksum is stored in skb-csum for use in __skb_checksum_complete
+ * non-zero: value of invalid checksum
+ *
+ */
+static inline __sum16 __skb_checksum_validate_complete(struct sk_buff *skb,
+ bool complete,
+ __wsum psum)
+{
+ if (skb-ip_summed == CHECKSUM_COMPLETE) {
+ if (!csum_fold(csum_add(psum, skb-csum))) {
+ skb-ip_summed = CHECKSUM_UNNECESSARY;
+ return 0;
+ }
+ }
+
+ skb-csum = psum;
+
+ if (complete || skb-len = CHECKSUM_BREAK)
+ return __skb_checksum_complete(skb);
+
+ return 0;
+}
+
+static inline __wsum null_compute_pseudo(struct sk_buff *skb, int proto)
+{
+ return 0;
+}
+
+/* Perform checksum validate (init). Note that this is a macro since we only
+ * want to calculate the pseudo header which is an input function if necessary.
+ * First we try to validate without any computation (checksum unnecessary) and
+ * then calculate based on checksum complete calling the function to compute
+ * pseudo header.
+ *
+ * Return values:
+ * 0: checksum is validated or try to in skb_checksum_complete
+ * non-zero: value of invalid checksum
+ */
+#define __skb_checksum_validate(skb, proto, complete, \
+ zero_okay, check, compute_pseudo) \
+({ \
+ __sum16 __ret = 0; \
+ if (__skb_checksum_validate_needed(skb, zero_okay, check)) \
+ __ret = __skb_checksum_validate_complete(skb, \
+ complete, compute_pseudo(skb, proto)); \
+ __ret; \
+})
+
+#define skb_checksum_init(skb, proto, compute_pseudo) \
+ __skb_checksum_validate(skb, proto, false, false, 0, compute_pseudo)
+
+#define skb_checksum_init_zero_check(skb, proto, check, compute_pseudo)
\
+ __skb_checksum_validate(skb, proto, false, true, check, compute_pseudo)
+
+#define skb_checksum_validate(skb, proto, compute_pseudo) \
+ __skb_checksum_validate(skb, proto, true, false, 0, compute_pseudo)
+
+#define skb_checksum_validate_zero_check(skb, proto, check,\
+compute_pseudo)\
+ __skb_checksum_validate_(skb, proto, true, true, check, compute_pseudo)
+
+#define skb_checksum_simple_validate(skb) \
+ __skb_checksum_validate(skb, 0, true, false, 0, null_compute_pseudo)
+
#if defined(CONFIG_NF_CONNTRACK) || defined(CONFIG_NF_CONNTRACK_MODULE)
void
[linux-yocto] [PATCH 3/5] ip6gre: add x-netns support
From: Nicolas Dichtel nicolas.dich...@6wind.com
commit 22f08069e8b415b827e910ad75ed55eeadc4a877 upstream
This patch allows to switch the netns when packet is encapsulated or
decapsulated. In other word, the encapsulated packet is received in a netns,
where the lookup is done to find the tunnel. Once the tunnel is found, the
packet is decapsulated and injecting into the corresponding interface which
stands to another netns.
When one of the two netns is removed, the tunnel is destroyed.
Signed-off-by: Nicolas Dichtel nicolas.dich...@6wind.com
Signed-off-by: David S. Miller da...@davemloft.net
Signed-off-by: Jianchuan Wang jianchuan.w...@windriver.com
---
net/ipv6/ip6_gre.c | 52
1 file changed, 32 insertions(+), 20 deletions(-)
diff --git a/net/ipv6/ip6_gre.c b/net/ipv6/ip6_gre.c
index 2465d18..084bde3 100644
--- a/net/ipv6/ip6_gre.c
+++ b/net/ipv6/ip6_gre.c
@@ -72,6 +72,7 @@ struct ip6gre_net {
};
static struct rtnl_link_ops ip6gre_link_ops __read_mostly;
+static struct rtnl_link_ops ip6gre_tap_ops __read_mostly;
static int ip6gre_tunnel_init(struct net_device *dev);
static void ip6gre_tunnel_setup(struct net_device *dev);
static void ip6gre_tunnel_link(struct ip6gre_net *ign, struct ip6_tnl *t);
@@ -353,10 +354,10 @@ failed_free:
static void ip6gre_tunnel_uninit(struct net_device *dev)
{
- struct net *net = dev_net(dev);
- struct ip6gre_net *ign = net_generic(net, ip6gre_net_id);
+ struct ip6_tnl *t = netdev_priv(dev);
+ struct ip6gre_net *ign = net_generic(t-net, ip6gre_net_id);
- ip6gre_tunnel_unlink(ign, netdev_priv(dev));
+ ip6gre_tunnel_unlink(ign, t);
dev_put(dev);
}
@@ -611,8 +612,8 @@ static netdev_tx_t ip6gre_xmit2(struct sk_buff *skb,
int encap_limit,
__u32 *pmtu)
{
- struct net *net = dev_net(dev);
struct ip6_tnl *tunnel = netdev_priv(dev);
+ struct net *net = tunnel-net;
struct net_device *tdev;/* Device to other host */
struct ipv6hdr *ipv6h; /* Our new IP header */
unsigned int max_headroom = 0; /* The extra header space needed */
@@ -979,7 +980,7 @@ static void ip6gre_tnl_link_config(struct ip6_tnl *t, int
set_mtu)
int strict = (ipv6_addr_type(p-raddr)
(IPV6_ADDR_MULTICAST|IPV6_ADDR_LINKLOCAL));
- struct rt6_info *rt = rt6_lookup(dev_net(dev),
+ struct rt6_info *rt = rt6_lookup(t-net,
p-raddr, p-laddr,
p-link, strict);
@@ -1063,13 +1064,12 @@ static int ip6gre_tunnel_ioctl(struct net_device *dev,
int err = 0;
struct ip6_tnl_parm2 p;
struct __ip6_tnl_parm p1;
- struct ip6_tnl *t;
- struct net *net = dev_net(dev);
+ struct ip6_tnl *t = netdev_priv(dev);
+ struct net *net = t-net;
struct ip6gre_net *ign = net_generic(net, ip6gre_net_id);
switch (cmd) {
case SIOCGETTUNNEL:
- t = NULL;
if (dev == ign-fb_tunnel_dev) {
if (copy_from_user(p, ifr-ifr_ifru.ifru_data,
sizeof(p))) {
err = -EFAULT;
@@ -1077,9 +1077,9 @@ static int ip6gre_tunnel_ioctl(struct net_device *dev,
}
ip6gre_tnl_parm_from_user(p1, p);
t = ip6gre_tunnel_locate(net, p1, 0);
+ if (t == NULL)
+ t = netdev_priv(dev);
}
- if (t == NULL)
- t = netdev_priv(dev);
memset(p, 0, sizeof(p));
ip6gre_tnl_parm_to_user(p, t-parms);
if (copy_to_user(ifr-ifr_ifru.ifru_data, p, sizeof(p)))
@@ -1242,7 +1242,6 @@ static void ip6gre_tunnel_setup(struct net_device *dev)
dev-flags |= IFF_NOARP;
dev-iflink = 0;
dev-addr_len = sizeof(struct in6_addr);
- dev-features |= NETIF_F_NETNS_LOCAL;
dev-priv_flags = ~IFF_XMIT_DST_RELEASE;
}
@@ -1297,11 +1296,17 @@ static struct inet6_protocol ip6gre_protocol
__read_mostly = {
.flags = INET6_PROTO_NOPOLICY|INET6_PROTO_FINAL,
};
-static void ip6gre_destroy_tunnels(struct ip6gre_net *ign,
- struct list_head *head)
+static void ip6gre_destroy_tunnels(struct net *net, struct list_head *head)
{
+ struct ip6gre_net *ign = net_generic(net, ip6gre_net_id);
+ struct net_device *dev, *aux;
int prio;
+ for_each_netdev_safe(net, dev, aux)
+ if (dev-rtnl_link_ops == ip6gre_link_ops ||
+ dev-rtnl_link_ops == ip6gre_tap_ops)
+ unregister_netdevice_queue(dev, head);
+
for (prio = 0; prio 4; prio++) {
int h;
for (h = 0; h HASH_SIZE; h++) {
@@ -1310,7 +1315,12 @@ static void
[linux-yocto] [PATCH 4/4] vxlan: use dev-needed_headroom instead of dev-hard_header_len
From: Cong Wang cw...@twopensource.com commit 2853af6a2ea1a8ed09b09dd4fb578e7f435e8d34 upstream vxlan: use dev-needed_headroom instead of dev-hard_header_len When we mirror packets from a vxlan tunnel to other device, the mirror device should see the same packets (that is, without outer header). Because vxlan tunnel sets dev-hard_header_len, tcf_mirred() resets mac header back to outer mac, the mirror device actually sees packets with outer headers Vxlan tunnel should set dev-needed_headroom instead of dev-hard_header_len, like what other ip tunnels do. This fixes the above problem. Cc: David S. Miller da...@davemloft.net Cc: stephen hemminger step...@networkplumber.org Cc: Pravin B Shelar pshe...@nicira.com Signed-off-by: Cong Wang cw...@twopensource.com Signed-off-by: Cong Wang xiyou.wangc...@gmail.com Signed-off-by: David S. Miller da...@davemloft.net Signed-off-by: Jianchuan Wang jianchuan.w...@windriver.com --- drivers/net/vxlan.c | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/drivers/net/vxlan.c b/drivers/net/vxlan.c index 4a5c522..d63dfbf 100644 --- a/drivers/net/vxlan.c +++ b/drivers/net/vxlan.c @@ -2288,9 +2288,9 @@ static void vxlan_setup(struct net_device *dev) eth_hw_addr_random(dev); ether_setup(dev); if (vxlan-default_dst.remote_ip.sa.sa_family == AF_INET6) - dev-hard_header_len = ETH_HLEN + VXLAN6_HEADROOM; + dev-needed_headroom = ETH_HLEN + VXLAN6_HEADROOM; else - dev-hard_header_len = ETH_HLEN + VXLAN_HEADROOM; + dev-needed_headroom = ETH_HLEN + VXLAN_HEADROOM; dev-netdev_ops = vxlan_netdev_ops; dev-destructor = free_netdev; @@ -2674,8 +2674,7 @@ static int vxlan_newlink(struct net *net, struct net_device *dev, if (!tb[IFLA_MTU]) dev-mtu = lowerdev-mtu - (use_ipv6 ? VXLAN6_HEADROOM : VXLAN_HEADROOM); - /* update header length based on lower device */ - dev-hard_header_len = lowerdev-hard_header_len + + dev-needed_headroom = lowerdev-hard_header_len + (use_ipv6 ? VXLAN6_HEADROOM : VXLAN_HEADROOM); } else if (use_ipv6) vxlan-flags |= VXLAN_F_IPV6; -- 1.9.1 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH] vxlan: Enable vxlan support
From: Jianchuan Wang jianchuan.w...@windriver.com vxlan: Enable vxlan support Signed-off-by: Jianchuan Wang jianchuan.w...@windriver.com --- meta/cfg/kernel-cache/features/vxlan/vxlan-enable.scc | 4 meta/cfg/kernel-cache/features/vxlan/vxlan.cfg| 1 + 2 files changed, 5 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/vxlan/vxlan-enable.scc create mode 100644 meta/cfg/kernel-cache/features/vxlan/vxlan.cfg diff --git a/meta/cfg/kernel-cache/features/vxlan/vxlan-enable.scc b/meta/cfg/kernel-cache/features/vxlan/vxlan-enable.scc new file mode 100644 index 000..b2f0c7d --- /dev/null +++ b/meta/cfg/kernel-cache/features/vxlan/vxlan-enable.scc @@ -0,0 +1,4 @@ +define KFEATURE_DESCRIPTION Enable vxlan support +define KFEATURE_COMPATIBILITY all + +kconf non-hardware vxlan.cfg diff --git a/meta/cfg/kernel-cache/features/vxlan/vxlan.cfg b/meta/cfg/kernel-cache/features/vxlan/vxlan.cfg new file mode 100644 index 000..2aa404d --- /dev/null +++ b/meta/cfg/kernel-cache/features/vxlan/vxlan.cfg @@ -0,0 +1 @@ +CONFIG_VXLAN=m -- 1.9.1 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 3/4] vxlan: add x-netns support
From: Nicolas Dichtel nicolas.dich...@6wind.com
commit f01ec1c017dead42092997a2b8684fcab4cbf126 upstream
vxlan: add x-netns support
This patch allows to switch the netns when packet is encapsulated or
decapsulated.
The vxlan socket is openned into the i/o netns, ie into the netns where
encapsulated packets are received. The socket lookup is done into this netns to
find the corresponding vxlan tunnel. After decapsulation, the packet is
injecting into the corresponding interface which may stand to another netns.
When one of the two netns is removed, the tunnel is destroyed.
Configuration example:
ip netns add netns1
ip netns exec netns1 ip link set lo up
ip link add vxlan10 type vxlan id 10 group 239.0.0.10 dev eth0 dstport 0
ip link set vxlan10 netns netns1
ip netns exec netns1 ip addr add 192.168.0.249/24 broadcast 192.168.0.255 dev
vxlan10
ip netns exec netns1 ip link set vxlan10 up
Signed-off-by: Nicolas Dichtel nicolas.dich...@6wind.com
Signed-off-by: David S. Miller da...@davemloft.net
Signed-off-by: Jianchuan Wang jianchuan.w...@windriver.com
---
drivers/net/vxlan.c | 63 ---
include/net/vxlan.h | 2 +-
net/openvswitch/vport-vxlan.c | 3 ++-
3 files changed, 50 insertions(+), 18 deletions(-)
diff --git a/drivers/net/vxlan.c b/drivers/net/vxlan.c
index 806881a..4a5c522 100644
--- a/drivers/net/vxlan.c
+++ b/drivers/net/vxlan.c
@@ -127,6 +127,7 @@ struct vxlan_dev {
struct list_head next; /* vxlan's per namespace list */
struct vxlan_sock *vn_sock; /* listening socket */
struct net_device *dev;
+ struct net*net; /* netns for packet i/o */
struct vxlan_rdst default_dst; /* default destination */
union vxlan_addr saddr;/* source address */
__be16dst_port;
@@ -1203,6 +1204,7 @@ static void vxlan_rcv(struct vxlan_sock *vs,
remote_ip = vxlan-default_dst.remote_ip;
skb_reset_mac_header(skb);
+ skb_scrub_packet(skb, !net_eq(vxlan-net, dev_net(vxlan-dev)));
skb-protocol = eth_type_trans(skb, vxlan-dev);
/* Ignore packet loops (and multicast echo) */
@@ -1618,7 +1620,8 @@ static int vxlan6_xmit_skb(struct vxlan_sock *vs,
struct dst_entry *dst, struct sk_buff *skb,
struct net_device *dev, struct in6_addr *saddr,
struct in6_addr *daddr, __u8 prio, __u8 ttl,
- __be16 src_port, __be16 dst_port, __be32 vni)
+ __be16 src_port, __be16 dst_port, __be32 vni,
+ bool xnet)
{
struct ipv6hdr *ip6h;
struct vxlanhdr *vxh;
@@ -1631,7 +1634,7 @@ static int vxlan6_xmit_skb(struct vxlan_sock *vs,
skb-encapsulation = 1;
}
- skb_scrub_packet(skb, false);
+ skb_scrub_packet(skb, xnet);
min_headroom = LL_RESERVED_SPACE(dst-dev) + dst-header_len
+ VXLAN_HLEN + sizeof(struct ipv6hdr)
@@ -1711,7 +1714,7 @@ static int vxlan6_xmit_skb(struct vxlan_sock *vs,
int vxlan_xmit_skb(struct vxlan_sock *vs,
struct rtable *rt, struct sk_buff *skb,
__be32 src, __be32 dst, __u8 tos, __u8 ttl, __be16 df,
- __be16 src_port, __be16 dst_port, __be32 vni)
+ __be16 src_port, __be16 dst_port, __be32 vni, bool xnet)
{
struct vxlanhdr *vxh;
struct udphdr *uh;
@@ -1760,7 +1763,7 @@ int vxlan_xmit_skb(struct vxlan_sock *vs,
return err;
return iptunnel_xmit(rt, skb, src, dst, IPPROTO_UDP, tos, ttl, df,
-false);
+xnet);
}
EXPORT_SYMBOL_GPL(vxlan_xmit_skb);
@@ -1853,7 +1856,7 @@ static void vxlan_xmit_one(struct sk_buff *skb, struct
net_device *dev,
fl4.daddr = dst-sin.sin_addr.s_addr;
fl4.saddr = vxlan-saddr.sin.sin_addr.s_addr;
- rt = ip_route_output_key(dev_net(dev), fl4);
+ rt = ip_route_output_key(vxlan-net, fl4);
if (IS_ERR(rt)) {
netdev_dbg(dev, no route to %pI4\n,
dst-sin.sin_addr.s_addr);
@@ -1874,7 +1877,7 @@ static void vxlan_xmit_one(struct sk_buff *skb, struct
net_device *dev,
struct vxlan_dev *dst_vxlan;
ip_rt_put(rt);
- dst_vxlan = vxlan_find_vni(dev_net(dev), vni, dst_port);
+ dst_vxlan = vxlan_find_vni(vxlan-net, vni, dst_port);
if (!dst_vxlan)
goto tx_error;
vxlan_encap_bypass(skb, vxlan, dst_vxlan);
@@ -1887,7 +1890,8 @@ static void vxlan_xmit_one(struct sk_buff *skb, struct
net_device *dev,
err = vxlan_xmit_skb(vxlan-vn_sock, rt, skb,
fl4.saddr,
[linux-yocto] [PATCH 1/4] vxlan: remove unused port variable in vxlan_udp_encap_recv()
From: Pablo Neira Ayuso pa...@gnumonks.org
commit 86c3f0f8307ac18f3ad3109e1969c62b8fbed5df upstream
vxlan: remove unused port variable in vxlan_udp_encap_recv()
Signed-off-by: Pablo Neira Ayuso pa...@gnumonks.org
Signed-off-by: David S. Miller da...@davemloft.net
Signed-off-by: Jianchuan Wang jianchuan.w...@windriver.com
---
drivers/net/vxlan.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/net/vxlan.c b/drivers/net/vxlan.c
index d091e52..6bab66a 100644
--- a/drivers/net/vxlan.c
+++ b/drivers/net/vxlan.c
@@ -1135,7 +1135,6 @@ static int vxlan_udp_encap_recv(struct sock *sk, struct
sk_buff *skb)
{
struct vxlan_sock *vs;
struct vxlanhdr *vxh;
- __be16 port;
/* Need Vxlan and inner Ethernet header to be present */
if (!pskb_may_pull(skb, VXLAN_HLEN))
@@ -1153,8 +1152,6 @@ static int vxlan_udp_encap_recv(struct sock *sk, struct
sk_buff *skb)
if (iptunnel_pull_header(skb, VXLAN_HLEN, htons(ETH_P_TEB)))
goto drop;
- port = inet_sk(sk)-inet_sport;
-
vs = rcu_dereference_sk_user_data(sk);
if (!vs)
goto drop;
--
1.9.1
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 3/3] block, bfq: add Early Queue Merge (EQM) to BFQ-v7r5 for 3.14.0
From: Mauro Andreolini mauro.andreol...@unimore.it
Original patch taken from:
http://algo.ing.unimo.it/people/paolo/disk_sched/patches/3.14.0-v7r5
A set of processes may happen to perform interleaved reads, i.e.,requests
whose union would give rise to a sequential read pattern. There are two
typical cases: in the first case, processes read fixed-size chunks of
data at a fixed distance from each other, while in the second case processes
may read variable-size chunks at variable distances. The latter case occurs
for example with QEMU, which splits the I/O generated by the guest into
multiple chunks, and lets these chunks be served by a pool of cooperating
processes, iteratively assigning the next chunk of I/O to the first
available process. CFQ uses actual queue merging for the first type of
rocesses, whereas it uses preemption to get a sequential read pattern out
of the read requests performed by the second type of processes. In the end
it uses two different mechanisms to achieve the same goal: boosting the
throughput with interleaved I/O.
This patch introduces Early Queue Merge (EQM), a unified mechanism to get a
sequential read pattern with both types of processes. The main idea is
checking newly arrived requests against the next request of the active queue
both in case of actual request insert and in case of request merge. By doing
so, both the types of processes can be handled by just merging their queues.
EQM is then simpler and more compact than the pair of mechanisms used in
CFQ.
Finally, EQM also preserves the typical low-latency properties of BFQ, by
properly restoring the weight-raising state of a queue when it gets back to
a non-merged state.
Signed-off-by: Mauro Andreolini mauro.andreol...@unimore.it
Signed-off-by: Arianna Avanzini avanzini.aria...@gmail.com
Signed-off-by: Paolo Valente paolo.vale...@unimore.it
Signed-off-by: Jianchuan Wang jianchuan.w...@windriver.com
---
block/bfq-iosched.c | 736
block/bfq-sched.c | 28 --
block/bfq.h | 46 +++-
3 files changed, 556 insertions(+), 254 deletions(-)
diff --git a/block/bfq-iosched.c b/block/bfq-iosched.c
index 0cbb182..452f477 100644
--- a/block/bfq-iosched.c
+++ b/block/bfq-iosched.c
@@ -571,6 +571,57 @@ static inline unsigned int bfq_wr_duration(struct bfq_data
*bfqd)
return dur;
}
+static inline unsigned
+bfq_bfqq_cooperations(struct bfq_queue *bfqq)
+{
+ return bfqq-bic ? bfqq-bic-cooperations : 0;
+}
+
+static inline void
+bfq_bfqq_resume_state(struct bfq_queue *bfqq, struct bfq_io_cq *bic)
+{
+ if (bic-saved_idle_window)
+ bfq_mark_bfqq_idle_window(bfqq);
+ else
+ bfq_clear_bfqq_idle_window(bfqq);
+ if (bic-saved_IO_bound)
+ bfq_mark_bfqq_IO_bound(bfqq);
+ else
+ bfq_clear_bfqq_IO_bound(bfqq);
+ if (bic-wr_time_left bfqq-bfqd-low_latency
+ bic-cooperations bfqq-bfqd-bfq_coop_thresh) {
+ /*
+* Start a weight raising period with the duration given by
+* the raising_time_left snapshot.
+*/
+ if (bfq_bfqq_busy(bfqq))
+ bfqq-bfqd-wr_busy_queues++;
+ bfqq-wr_coeff = bfqq-bfqd-bfq_wr_coeff;
+ bfqq-wr_cur_max_time = bic-wr_time_left;
+ bfqq-last_wr_start_finish = jiffies;
+ bfqq-entity.ioprio_changed = 1;
+ }
+ /*
+* Clear wr_time_left to prevent bfq_bfqq_save_state() from
+* getting confused about the queue's need of a weight-raising
+* period.
+*/
+ bic-wr_time_left = 0;
+}
+
+/*
+ * Must be called with the queue_lock held.
+ */
+static int bfqq_process_refs(struct bfq_queue *bfqq)
+{
+ int process_refs, io_refs;
+
+ io_refs = bfqq-allocated[READ] + bfqq-allocated[WRITE];
+ process_refs = atomic_read(bfqq-ref) - io_refs - bfqq-entity.on_st;
+ BUG_ON(process_refs 0);
+ return process_refs;
+}
+
static void bfq_add_request(struct request *rq)
{
struct bfq_queue *bfqq = RQ_BFQQ(rq);
@@ -602,8 +653,11 @@ static void bfq_add_request(struct request *rq)
if (!bfq_bfqq_busy(bfqq)) {
int soft_rt = bfqd-bfq_wr_max_softrt_rate 0
+ bfq_bfqq_cooperations(bfqq) bfqd-bfq_coop_thresh
time_is_before_jiffies(bfqq-soft_rt_next_start);
- idle_for_long_time = time_is_before_jiffies(
+ idle_for_long_time = bfq_bfqq_cooperations(bfqq)
+bfqd-bfq_coop_thresh
+ time_is_before_jiffies(
bfqq-budget_timeout +
bfqd-bfq_wr_min_idle_time);
entity-budget = max_t(unsigned long, bfqq-max_budget,
@@ -624,11 +678,20 @@ static void bfq_add_request(struct request *rq)
[linux-yocto] [PATCH 1/3] block: cgroups, kconfig, build bits for BFQ-v7r5-3.14
From: Paolo Valente paolo.vale...@unimore.it Original patch taken from: http://algo.ing.unimo.it/people/paolo/disk_sched/patches/3.14.0-v7r5 Update Kconfig.iosched and do the related Makefile changes to include kernel configuration options for BFQ. Also add the bfqio controller to the cgroups subsystem. Signed-off-by: Paolo Valente paolo.vale...@unimore.it Signed-off-by: Arianna Avanzini avanzini.aria...@gmail.com Signed-off-by: Jianchuan Wang jianchuan.w...@windriver.com --- block/Kconfig.iosched | 32 block/Makefile| 1 + include/linux/cgroup_subsys.h | 4 3 files changed, 37 insertions(+) diff --git a/block/Kconfig.iosched b/block/Kconfig.iosched index 421bef9..0ee5f0f 100644 --- a/block/Kconfig.iosched +++ b/block/Kconfig.iosched @@ -39,6 +39,27 @@ config CFQ_GROUP_IOSCHED ---help--- Enable group IO scheduling in CFQ. +config IOSCHED_BFQ + tristate BFQ I/O scheduler + default n + ---help--- + The BFQ I/O scheduler tries to distribute bandwidth among + all processes according to their weights. + It aims at distributing the bandwidth as desired, independently of + the disk parameters and with any workload. It also tries to + guarantee low latency to interactive and soft real-time + applications. If compiled built-in (saying Y here), BFQ can + be configured to support hierarchical scheduling. + +config CGROUP_BFQIO + bool BFQ hierarchical scheduling support + depends on CGROUPS IOSCHED_BFQ=y + default n + ---help--- + Enable hierarchical scheduling in BFQ, using the cgroups + filesystem interface. The name of the subsystem will be + bfqio. + choice prompt Default I/O scheduler default DEFAULT_CFQ @@ -52,6 +73,16 @@ choice config DEFAULT_CFQ bool CFQ if IOSCHED_CFQ=y + config DEFAULT_BFQ + bool BFQ if IOSCHED_BFQ=y + help + Selects BFQ as the default I/O scheduler which will be + used by default for all block devices. + The BFQ I/O scheduler aims at distributing the bandwidth + as desired, independently of the disk parameters and with + any workload. It also tries to guarantee low latency to + interactive and soft real-time applications. + config DEFAULT_NOOP bool No-op @@ -61,6 +92,7 @@ config DEFAULT_IOSCHED string default deadline if DEFAULT_DEADLINE default cfq if DEFAULT_CFQ + default bfq if DEFAULT_BFQ default noop if DEFAULT_NOOP endmenu diff --git a/block/Makefile b/block/Makefile index 20645e8..cbd83fb 100644 --- a/block/Makefile +++ b/block/Makefile @@ -16,6 +16,7 @@ obj-$(CONFIG_BLK_DEV_THROTTLING) += blk-throttle.o obj-$(CONFIG_IOSCHED_NOOP) += noop-iosched.o obj-$(CONFIG_IOSCHED_DEADLINE) += deadline-iosched.o obj-$(CONFIG_IOSCHED_CFQ) += cfq-iosched.o +obj-$(CONFIG_IOSCHED_BFQ) += bfq-iosched.o obj-$(CONFIG_BLOCK_COMPAT) += compat_ioctl.o obj-$(CONFIG_BLK_DEV_INTEGRITY)+= blk-integrity.o diff --git a/include/linux/cgroup_subsys.h b/include/linux/cgroup_subsys.h index 7b99d71..4e8c0ff 100644 --- a/include/linux/cgroup_subsys.h +++ b/include/linux/cgroup_subsys.h @@ -39,6 +39,10 @@ SUBSYS(net_cls) SUBSYS(blkio) #endif +#if IS_SUBSYS_ENABLED(CONFIG_CGROUP_BFQIO) +SUBSYS(bfqio) +#endif + #if IS_SUBSYS_ENABLED(CONFIG_CGROUP_PERF) SUBSYS(perf) #endif -- 1.9.1 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH] BFQ: Support Budget Fair Queueing (BFQ) Storage-I/O Scheduler
From: Jianchuan Wang jianchuan.w...@windriver.com BFQ: Support Budget Fair Queueing (BFQ) Storage-I/O Scheduler Signed-off-by: Jianchuan Wang jianchuan.w...@windriver.com --- meta/cfg/kernel-cache/features/bfq/bfq-enable.scc | 1 + meta/cfg/kernel-cache/features/bfq/bfq.cfg| 2 ++ 2 files changed, 3 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/bfq/bfq-enable.scc create mode 100644 meta/cfg/kernel-cache/features/bfq/bfq.cfg diff --git a/meta/cfg/kernel-cache/features/bfq/bfq-enable.scc b/meta/cfg/kernel-cache/features/bfq/bfq-enable.scc new file mode 100644 index 000..c75a014 --- /dev/null +++ b/meta/cfg/kernel-cache/features/bfq/bfq-enable.scc @@ -0,0 +1 @@ +kconf non-hardware bfq.cfg diff --git a/meta/cfg/kernel-cache/features/bfq/bfq.cfg b/meta/cfg/kernel-cache/features/bfq/bfq.cfg new file mode 100644 index 000..df82ebc --- /dev/null +++ b/meta/cfg/kernel-cache/features/bfq/bfq.cfg @@ -0,0 +1,2 @@ +CONFIG_IOSCHED_BFQ=y +CONFIG_CGROUP_BFQIO=y -- 1.9.1 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH] Meta: add qemuppc64 bsp config
On 2014-08-26, 8:25 PM, akuster808 wrote: On 08/26/2014 10:04 AM, Bruce Ashfield wrote: On 14-08-26 11:05 AM, Armin Kuster wrote: This is the initial meta data for qemu ppc64 bsp that supports the IBM pseries power* arch with is supported in Qemu. Thanks for the patch .. see below for some comments. Yes, its not pretty but it works. Do you have a bootlog capture ? I can on getting one. is this normally need ( process question). There's no firm process, but it is something that I've asked for over the years, since it gives us a good reference to what was working when the BSP was first introduced. And a list of supported features ? is the a doc on what is meant by features? It's mainly features from the point of view of the h/w. i.e. what ethernet is used (emulated or not), clock sources, etc. The yocto reference BSPs capture some of this in the README files. Again, no hard and fast rules .. but the more we know, the more I can not break the board with merges, and when someone wanders by later, they'll know what to expect. Signed-off-by: Armin Kuster akuster...@gmail.com --- .../bsp/qemu-ppc64/qemu-ppc64-standard.scc |8 + .../cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg | 2778 .../cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.scc |1 + 3 files changed, 2787 insertions(+) create mode 100644 meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc create mode 100644 meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg create mode 100644 meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.scc diff --git a/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc new file mode 100644 index 000..bf48141 --- /dev/null +++ b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc @@ -0,0 +1,8 @@ +define KMACHINE qemuppc64 +define KTYPE standard +define KARCH powerpc + +include ktypes/standard/standard.scc +branch qemuppc + +include qemu-ppc64.scc diff --git a/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg new file mode 100644 index 000..68c3264 --- /dev/null +++ b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg @@ -0,0 +1,2778 @@ +CONFIG_PPC64=y + +# +# Processor support This looks like a deconfig capture, which is fine as a starting point. correct. easiest thing to do for now. But it means that the consistency/policy of the base fragments is not being used. this is the goal I hope to achieve as I learn this process. Are we saying that we don't know which ones are platform options ? A visual pass can prune things down quickly .. see below: I will take out my chainsaw and do a bit of trimming and clean up. Excellent :) +# +CONFIG_PPC_BOOK3S_64=y +# CONFIG_PPC_BOOK3E_64 is not set +CONFIG_GENERIC_CPU=y +# CONFIG_CELL_CPU is not set +# CONFIG_POWER4_CPU is not set +# CONFIG_POWER5_CPU is not set +# CONFIG_POWER6_CPU is not set +# CONFIG_POWER7_CPU is not set +CONFIG_PPC_BOOK3S=y +CONFIG_POWER3=y +CONFIG_POWER4=y +# CONFIG_TUNE_CELL is not set +CONFIG_PPC_FPU=y +CONFIG_ALTIVEC=y +CONFIG_VSX=y +# CONFIG_PPC_ICSWX is not set +CONFIG_PPC_STD_MMU=y +CONFIG_PPC_STD_MMU_64=y +CONFIG_PPC_MM_SLICES=y +CONFIG_PPC_HAVE_PMU_SUPPORT=y +CONFIG_PPC_PERF_CTRS=y +CONFIG_SMP=y +CONFIG_NR_CPUS=2048 +CONFIG_PPC_DOORBELL=y +CONFIG_CPU_BIG_ENDIAN=y +# CONFIG_CPU_LITTLE_ENDIAN is not set +CONFIG_64BIT=y +CONFIG_WORD_SIZE=64 +CONFIG_ARCH_PHYS_ADDR_T_64BIT=y +CONFIG_ARCH_DMA_ADDR_T_64BIT=y +CONFIG_MMU=y +CONFIG_HAVE_SETUP_PER_CPU_AREA=y +CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y +CONFIG_NR_IRQS=512 +CONFIG_STACKTRACE_SUPPORT=y +CONFIG_HAVE_LATENCYTOP_SUPPORT=y +CONFIG_TRACE_IRQFLAGS_SUPPORT=y +CONFIG_LOCKDEP_SUPPORT=y +CONFIG_RWSEM_XCHGADD_ALGORITHM=y +CONFIG_ARCH_HAS_ILOG2_U32=y +CONFIG_ARCH_HAS_ILOG2_U64=y +CONFIG_GENERIC_HWEIGHT=y +CONFIG_PPC=y +# CONFIG_GENERIC_CSUM is not set +CONFIG_EARLY_PRINTK=y Things like early printk, are not in board h/w fragments. ok +CONFIG_PANIC_TIMEOUT=180 +CONFIG_COMPAT=y +CONFIG_SYSVIPC_COMPAT=y +CONFIG_SCHED_OMIT_FRAME_POINTER=y +CONFIG_ARCH_MAY_HAVE_PC_FDC=y +CONFIG_PPC_OF=y +CONFIG_PPC_UDBG_16550=y +# CONFIG_GENERIC_TBSYNC is not set +CONFIG_AUDIT_ARCH=y +CONFIG_GENERIC_BUG=y +CONFIG_EPAPR_BOOT=y +# CONFIG_DEFAULT_UIMAGE is not set +CONFIG_ARCH_HIBERNATION_POSSIBLE=y +CONFIG_ARCH_SUSPEND_POSSIBLE=y +# CONFIG_PPC_DCR_NATIVE is not set +# CONFIG_PPC_DCR_MMIO is not set +# CONFIG_PPC_OF_PLATFORM_PCI is not set +CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y +CONFIG_ARCH_SUPPORTS_UPROBES=y +CONFIG_PPC_EMULATE_SSTEP=y +CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config +CONFIG_IRQ_WORK=y + +# +# General setup +# +CONFIG_INIT_ENV_ARG_LIMIT=32 +CONFIG_CROSS_COMPILE= +# CONFIG_COMPILE_TEST is not set +CONFIG_LOCALVERSION= +CONFIG_LOCALVERSION_AUTO=y +CONFIG_DEFAULT_HOSTNAME=(none) +CONFIG_SWAP=y +CONFIG_SYSVIPC=y +CONFIG_SYSVIPC_SYSCTL=y +CONFIG_POSIX_MQUEUE=y
[linux-yocto] [PATCH 1/2] yaffs: Avoid setting any ACL releated xattr
YAFFS doesn't sopport ACL yet, it must refuse any related settings.
Signed-off-by: Zhang Xiao xiao.zh...@windriver.com
---
fs/yaffs2/yaffs_vfs.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/fs/yaffs2/yaffs_vfs.c b/fs/yaffs2/yaffs_vfs.c
index 13de856..d372a4e 100644
--- a/fs/yaffs2/yaffs_vfs.c
+++ b/fs/yaffs2/yaffs_vfs.c
@@ -931,6 +931,12 @@ static int yaffs_setxattr(struct dentry *dentry, const
char *name,
yaffs_trace(YAFFS_TRACE_OS, yaffs_setxattr of object %d, obj-obj_id);
+ /* Currently we don't support posix ACL so never accept any settings
+* start with system.posix_acl_.
+*/
+ if (strncmp(name, system.posix_acl_, 17))
+ error = -EOPNOTSUPP;
+
if (error == 0) {
int result;
dev = obj-my_dev;
--
1.8.5.2.233.g932f7e4
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 2/2] yaffs: fix yaffs_vfs.c warnings.
fs/yaffs2/yaffs_vfs.c:3036:14: warning: 'yaffs_dump_dev_part0' defined but not
used [-Wunused-function]
fs/yaffs2/yaffs_vfs.c:3074:14: warning: 'yaffs_dump_dev_part1' defined but not
used [-Wunused-function]
fs/yaffs2/yaffs_vfs.c:3192:3: warning: 'mask_flags' defined but not used
[-Wunused-variable]
Signed-off-by: Zhang Xiao xiao.zh...@windriver.com
---
fs/yaffs2/yaffs_vfs.c | 4
1 file changed, 4 deletions(-)
diff --git a/fs/yaffs2/yaffs_vfs.c b/fs/yaffs2/yaffs_vfs.c
index d372a4e..2abb127 100644
--- a/fs/yaffs2/yaffs_vfs.c
+++ b/fs/yaffs2/yaffs_vfs.c
@@ -3140,7 +3140,6 @@ static DECLARE_FSTYPE(yaffs2_fs_type, yaffs2,
yaffs2_read_super,
#if (LINUX_VERSION_CODE KERNEL_VERSION(3, 9, 0))
static struct proc_dir_entry *my_proc_entry;
-#endif
static char *yaffs_dump_dev_part0(char *buf, struct yaffs_dev *dev)
{
@@ -3229,7 +3228,6 @@ static char *yaffs_dump_dev_part1(char *buf, struct
yaffs_dev *dev)
return buf;
}
-#if (LINUX_VERSION_CODE KERNEL_VERSION(3, 9, 0))
static int yaffs_proc_read(char *page,
char **start,
off_t offset, int count, int *eof, void *data)
@@ -3285,7 +3283,6 @@ static int yaffs_proc_read(char *page,
return buf - page count ? buf - page : count;
}
-#endif
/**
* Set the verbosity of the warnings and error messages.
@@ -3328,7 +3325,6 @@ static struct {
{NULL, 0},
};
-#if (LINUX_VERSION_CODE KERNEL_VERSION(3, 9, 0))
#define MAX_MASK_NAME_LENGTH 40
static int yaffs_proc_write_trace_options(struct file *file, const char *buf,
unsigned long count, void *data)
--
1.8.5.2.233.g932f7e4
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
