[U-Boot] [PATCH] u-boot: Upgrade to 2017.09
This upgrades the U-Boot to the 2017.09 release.
Signed-off-by: Otavio Salvador otavio@ossystems.com.br ---
.../u-boot/{u-boot-common_2017.07.inc => u-boot-common_2017.09.inc} | 2 +- .../u-boot/{u-boot-fw-utils_2017.07.bb => u-boot-fw-utils_2017.09.bb} | 0 .../u-boot/{u-boot-mkimage_2017.07.bb => u-boot-mkimage_2017.09.bb} | 0 meta/recipes-bsp/u-boot/{u-boot_2017.07.bb => u-boot_2017.09.bb} | 0 4 files changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-bsp/u-boot/{u-boot-common_2017.07.inc => u-boot-common_2017.09.inc} (89%) rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2017.07.bb => u-boot-fw-utils_2017.09.bb} (100%) rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2017.07.bb => u-boot-mkimage_2017.09.bb} (100%) rename meta/recipes-bsp/u-boot/{u-boot_2017.07.bb => u-boot_2017.09.bb} (100%)
diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc b/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc similarity index 89% rename from meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc rename to meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc index e37f5fd409..02e51242cb 100644 --- a/meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc +++ b/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc @@ -7,7 +7,7 @@ PE = "1"
# We use the revision in order to avoid having to fetch it from the # repo during parse -SRCREV = "d85ca029f257b53a96da6c2fb421e78a003a9943" +SRCREV = "c98ac3487e413c71e5d36322ef3324b21c6f60f9"
SRC_URI = "git://git.denx.de/u-boot.git \ file://MPC8315ERDB-enable-DHCP.patch \ diff --git a/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.07.bb b/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.09.bb similarity index 100% rename from meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.07.bb rename to meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.09.bb diff --git a/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.07.bb b/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.09.bb similarity index 100% rename from meta/recipes-bsp/u-boot/u-boot-mkimage_2017.07.bb rename to meta/recipes-bsp/u-boot/u-boot-mkimage_2017.09.bb diff --git a/meta/recipes-bsp/u-boot/u-boot_2017.07.bb b/meta/recipes-bsp/u-boot/u-boot_2017.09.bb similarity index 100% rename from meta/recipes-bsp/u-boot/u-boot_2017.07.bb rename to meta/recipes-bsp/u-boot/u-boot_2017.09.bb
On 09/11/2017 10:30 PM, Otavio Salvador wrote:
This upgrades the U-Boot to the 2017.09 release.
Signed-off-by: Otavio Salvador otavio@ossystems.com.br
Wrong ML, but since this is already here ...
.../u-boot/{u-boot-common_2017.07.inc => u-boot-common_2017.09.inc} | 2 +- .../u-boot/{u-boot-fw-utils_2017.07.bb => u-boot-fw-utils_2017.09.bb} | 0 .../u-boot/{u-boot-mkimage_2017.07.bb => u-boot-mkimage_2017.09.bb} | 0 meta/recipes-bsp/u-boot/{u-boot_2017.07.bb => u-boot_2017.09.bb} | 0 4 files changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-bsp/u-boot/{u-boot-common_2017.07.inc => u-boot-common_2017.09.inc} (89%) rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2017.07.bb => u-boot-fw-utils_2017.09.bb} (100%) rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2017.07.bb => u-boot-mkimage_2017.09.bb} (100%) rename meta/recipes-bsp/u-boot/{u-boot_2017.07.bb => u-boot_2017.09.bb} (100%)
diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc b/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc similarity index 89% rename from meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc rename to meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc index e37f5fd409..02e51242cb 100644 --- a/meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc +++ b/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc @@ -7,7 +7,7 @@ PE = "1"
# We use the revision in order to avoid having to fetch it from the # repo during parse -SRCREV = "d85ca029f257b53a96da6c2fb421e78a003a9943" +SRCREV = "c98ac3487e413c71e5d36322ef3324b21c6f60f9"
SRC_URI = "git://git.denx.de/u-boot.git \ file://MPC8315ERDB-enable-DHCP.patch \
... file://10m50-update-device-tree.patch
What is the status of those dangling patches ? They were apparently posted, but didn't make it into the last two (?) releases.
[...]
On Wed, Sep 13, 2017 at 5:05 PM, Marek Vasut marek.vasut@gmail.com wrote: ...
What is the status of those dangling patches ? They were apparently posted, but didn't make it into the last two (?) releases.
I am confused. Are you asking for U-Boot community or OE community?
On 09/13/2017 10:11 PM, Otavio Salvador wrote:
On Wed, Sep 13, 2017 at 5:05 PM, Marek Vasut marek.vasut@gmail.com wrote: ...
What is the status of those dangling patches ? They were apparently posted, but didn't make it into the last two (?) releases.
I am confused. Are you asking for U-Boot community or OE community?
How does that matter ? I am asking about the status of those patches and why they didn't make it upstream yet. Something should be done about that.
Automated update of the U-Boot recipe version is great and all, but that's not all that should be done when new version is released . The outstanding patches need to be rechecked every now and then too so they get upstream and don't start piling up in OE core.
Marek,
On Wed, Sep 13, 2017 at 5:20 PM, Marek Vasut marek.vasut@gmail.com wrote:
On 09/13/2017 10:11 PM, Otavio Salvador wrote:
On Wed, Sep 13, 2017 at 5:05 PM, Marek Vasut marek.vasut@gmail.com wrote: ...
What is the status of those dangling patches ? They were apparently posted, but didn't make it into the last two (?) releases.
I am confused. Are you asking for U-Boot community or OE community?
How does that matter ? I am asking about the status of those patches and why they didn't make it upstream yet. Something should be done about that.
Automated update of the U-Boot recipe version is great and all, but that's not all that should be done when new version is released . The outstanding patches need to be rechecked every now and then too so they get upstream and don't start piling up in OE core.
You are the maintainer, so step up and do it. I did the upgrade as I had it here for testing so I thought it would be good to send it.
On 09/13/2017 11:02 PM, Otavio Salvador wrote:
Marek,
On Wed, Sep 13, 2017 at 5:20 PM, Marek Vasut marek.vasut@gmail.com wrote:
On 09/13/2017 10:11 PM, Otavio Salvador wrote:
On Wed, Sep 13, 2017 at 5:05 PM, Marek Vasut marek.vasut@gmail.com wrote: ...
What is the status of those dangling patches ? They were apparently posted, but didn't make it into the last two (?) releases.
I am confused. Are you asking for U-Boot community or OE community?
How does that matter ? I am asking about the status of those patches and why they didn't make it upstream yet. Something should be done about that.
Automated update of the U-Boot recipe version is great and all, but that's not all that should be done when new version is released . The outstanding patches need to be rechecked every now and then too so they get upstream and don't start piling up in OE core.
You are the maintainer, so step up and do it. I did the upgrade as I had it here for testing so I thought it would be good to send it.
Right ... low-hanging fruit and all, so sad :-(
Let's see about those two patches then, they should be sorted out shortly ...
Is anyone seeing u-boot-fw-utils.do_install failure with this?
u-boot-fw-utils/1_2017.09-r0/git/tools/env/fw_printenv: No such file or directory
I've tried u-boot-fw-utils-cross, but it fails as well even sooner in do_compile:
Log data follows: | DEBUG: Executing shell function do_compile | NOTE: make -j 32 ARCH=arm CC=gcc -isystemwork/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/usr/include -O2 -pipe -Lwork/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/usr/lib -Lwork/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/lib -Wl,-rpath-link,work/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/usr/lib -Wl,-rpath-link,work/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/lib -Wl,-rpath,work/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/usr/lib -Wl,-rpath,work/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/lib -Wl,-O1 V=1 rpi_3_32b_config | make -f ./scripts/Makefile.build obj=scripts/basic | cc -Wp,-MD,scripts/basic/.fixdep.d -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o scripts/basic/fixdep scripts/basic/fixdep.c | /bin/sh: 1: cc: not found | make[1]: *** [scripts/basic/fixdep] Error 127 | make: *** [scripts_basic] Error 2 | ERROR: oe_runmake failed | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_compile (log file is located at work/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/temp/log.do_compile.12859) ERROR: Task (virtual:cross:oe-core/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.09.bb:do_compile) failed with exit code '1'
On Mon, Sep 11, 2017 at 10:30 PM, Otavio Salvador otavio@ossystems.com.br wrote:
This upgrades the U-Boot to the 2017.09 release.
Signed-off-by: Otavio Salvador otavio@ossystems.com.br
.../u-boot/{u-boot-common_2017.07.inc => u-boot-common_2017.09.inc} | 2 +- .../u-boot/{u-boot-fw-utils_2017.07.bb => u-boot-fw-utils_2017.09.bb} | 0 .../u-boot/{u-boot-mkimage_2017.07.bb => u-boot-mkimage_2017.09.bb} | 0 meta/recipes-bsp/u-boot/{u-boot_2017.07.bb => u-boot_2017.09.bb} | 0 4 files changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-bsp/u-boot/{u-boot-common_2017.07.inc => u-boot-common_2017.09.inc} (89%) rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2017.07.bb => u-boot-fw-utils_2017.09.bb} (100%) rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2017.07.bb => u-boot-mkimage_2017.09.bb} (100%) rename meta/recipes-bsp/u-boot/{u-boot_2017.07.bb => u-boot_2017.09.bb} (100%)
diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc b/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc similarity index 89% rename from meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc rename to meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc index e37f5fd409..02e51242cb 100644 --- a/meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc +++ b/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc @@ -7,7 +7,7 @@ PE = "1"
# We use the revision in order to avoid having to fetch it from the # repo during parse -SRCREV = "d85ca029f257b53a96da6c2fb421e78a003a9943" +SRCREV = "c98ac3487e413c71e5d36322ef3324b21c6f60f9"
SRC_URI = "git://git.denx.de/u-boot.git \ file://MPC8315ERDB-enable-DHCP.patch \ diff --git a/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.07.bb b/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.09.bb similarity index 100% rename from meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.07.bb rename to meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.09.bb diff --git a/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.07.bb b/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.09.bb similarity index 100% rename from meta/recipes-bsp/u-boot/u-boot-mkimage_2017.07.bb rename to meta/recipes-bsp/u-boot/u-boot-mkimage_2017.09.bb diff --git a/meta/recipes-bsp/u-boot/u-boot_2017.07.bb b/meta/recipes-bsp/u-boot/u-boot_2017.09.bb similarity index 100% rename from meta/recipes-bsp/u-boot/u-boot_2017.07.bb rename to meta/recipes-bsp/u-boot/u-boot_2017.09.bb -- 2.14.1
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
I've verified that u-boot-fw-utils builds and installs fw_printenv correctly with 2017.07.
And that u-boot-fw-utils-cross was broken even with Yocto 2.3 Pyro and 2017.01 version there, maybe it's time to remove cross version? As nobody is using it and it's not tested?
On Sun, Sep 17, 2017 at 11:18 AM, Martin Jansa martin.jansa@gmail.com wrote:
Is anyone seeing u-boot-fw-utils.do_install failure with this?
u-boot-fw-utils/1_2017.09-r0/git/tools/env/fw_printenv: No such file or directory
I've tried u-boot-fw-utils-cross, but it fails as well even sooner in do_compile:
Log data follows: | DEBUG: Executing shell function do_compile | NOTE: make -j 32 ARCH=arm CC=gcc -isystemwork/x86_64-linux/u- boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/usr/include -O2 -pipe -Lwork/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/usr/lib -Lwork/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/lib -Wl,-rpath-link,work/x86_64-linux/u-boot-fw-utils-cross/1_ 2017.09-r0/recipe-sysroot-native/usr/lib -Wl,-rpath-link,work/x86_64- linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/lib -Wl,-rpath,work/x86_64-linux/u-boot-fw-utils-cross/1_2017. 09-r0/recipe-sysroot-native/usr/lib -Wl,-rpath,work/x86_64-linux/ u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/lib -Wl,-O1 V=1 rpi_3_32b_config | make -f ./scripts/Makefile.build obj=scripts/basic | cc -Wp,-MD,scripts/basic/.fixdep.d -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o scripts/basic/fixdep scripts/basic/fixdep.c | /bin/sh: 1: cc: not found | make[1]: *** [scripts/basic/fixdep] Error 127 | make: *** [scripts_basic] Error 2 | ERROR: oe_runmake failed | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_compile (log file is located at work/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/temp/ log.do_compile.12859) ERROR: Task (virtual:cross:oe-core/meta/recipes-bsp/u-boot/u-boot-fw- utils_2017.09.bb:do_compile) failed with exit code '1'
On Mon, Sep 11, 2017 at 10:30 PM, Otavio Salvador <otavio@ossystems.com.br
wrote:
This upgrades the U-Boot to the 2017.09 release.
Signed-off-by: Otavio Salvador otavio@ossystems.com.br
.../u-boot/{u-boot-common_2017.07.inc => u-boot-common_2017.09.inc} | 2 +- .../u-boot/{u-boot-fw-utils_2017.07.bb => u-boot-fw-utils_2017.09.bb} | 0 .../u-boot/{u-boot-mkimage_2017.07.bb => u-boot-mkimage_2017.09.bb} | 0 meta/recipes-bsp/u-boot/{u-boot_2017.07.bb => u-boot_2017.09.bb} | 0 4 files changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-bsp/u-boot/{u-boot-common_2017.07.inc => u-boot-common_2017.09.inc} (89%) rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2017.07.bb => u-boot-fw-utils_2017.09.bb} (100%) rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2017.07.bb => u-boot-mkimage_2017.09.bb} (100%) rename meta/recipes-bsp/u-boot/{u-boot_2017.07.bb => u-boot_2017.09.bb} (100%)
diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc b/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc similarity index 89% rename from meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc rename to meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc index e37f5fd409..02e51242cb 100644 --- a/meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc +++ b/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc @@ -7,7 +7,7 @@ PE = "1"
# We use the revision in order to avoid having to fetch it from the # repo during parse -SRCREV = "d85ca029f257b53a96da6c2fb421e78a003a9943" +SRCREV = "c98ac3487e413c71e5d36322ef3324b21c6f60f9"
SRC_URI = "git://git.denx.de/u-boot.git \ file://MPC8315ERDB-enable-DHCP.patch \ diff --git a/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.07.bb b/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.09.bb similarity index 100% rename from meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.07.bb rename to meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.09.bb diff --git a/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.07.bb b/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.09.bb similarity index 100% rename from meta/recipes-bsp/u-boot/u-boot-mkimage_2017.07.bb rename to meta/recipes-bsp/u-boot/u-boot-mkimage_2017.09.bb diff --git a/meta/recipes-bsp/u-boot/u-boot_2017.07.bb b/meta/recipes-bsp/u-boot/u-boot_2017.09.bb similarity index 100% rename from meta/recipes-bsp/u-boot/u-boot_2017.07.bb rename to meta/recipes-bsp/u-boot/u-boot_2017.09.bb -- 2.14.1
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
On 09/17/2017 01:06 PM, Martin Jansa wrote:
I've verified that u-boot-fw-utils builds and installs fw_printenv correctly with 2017.07.
And that u-boot-fw-utils-cross was broken even with Yocto 2.3 Pyro and 2017.01 version there, maybe it's time to remove cross version? As nobody is using it and it's not tested?
Nobody apparently even build-tested this patch before submission, gurrr.
Speaking of cross versions of U-Boot fwutils and printenv/setenv , they are used by boards for modifying U-Boot environment on the target from Linux, so removing them would break a lot of boards -- NAK.
On Sun, Sep 17, 2017 at 11:18 AM, Martin Jansa martin.jansa@gmail.com wrote:
Is anyone seeing u-boot-fw-utils.do_install failure with this?
u-boot-fw-utils/1_2017.09-r0/git/tools/env/fw_printenv: No such file or directory
I've tried u-boot-fw-utils-cross, but it fails as well even sooner in do_compile:
Log data follows: | DEBUG: Executing shell function do_compile | NOTE: make -j 32 ARCH=arm CC=gcc -isystemwork/x86_64-linux/u- boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/usr/include -O2 -pipe -Lwork/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/usr/lib -Lwork/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/lib -Wl,-rpath-link,work/x86_64-linux/u-boot-fw-utils-cross/1_ 2017.09-r0/recipe-sysroot-native/usr/lib -Wl,-rpath-link,work/x86_64- linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/lib -Wl,-rpath,work/x86_64-linux/u-boot-fw-utils-cross/1_2017. 09-r0/recipe-sysroot-native/usr/lib -Wl,-rpath,work/x86_64-linux/ u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/lib -Wl,-O1 V=1 rpi_3_32b_config | make -f ./scripts/Makefile.build obj=scripts/basic | cc -Wp,-MD,scripts/basic/.fixdep.d -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o scripts/basic/fixdep scripts/basic/fixdep.c | /bin/sh: 1: cc: not found | make[1]: *** [scripts/basic/fixdep] Error 127 | make: *** [scripts_basic] Error 2 | ERROR: oe_runmake failed | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_compile (log file is located at work/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/temp/ log.do_compile.12859) ERROR: Task (virtual:cross:oe-core/meta/recipes-bsp/u-boot/u-boot-fw- utils_2017.09.bb:do_compile) failed with exit code '1'
On Mon, Sep 11, 2017 at 10:30 PM, Otavio Salvador <otavio@ossystems.com.br
wrote:
This upgrades the U-Boot to the 2017.09 release.
Signed-off-by: Otavio Salvador otavio@ossystems.com.br
.../u-boot/{u-boot-common_2017.07.inc => u-boot-common_2017.09.inc} | 2 +- .../u-boot/{u-boot-fw-utils_2017.07.bb => u-boot-fw-utils_2017.09.bb} | 0 .../u-boot/{u-boot-mkimage_2017.07.bb => u-boot-mkimage_2017.09.bb} | 0 meta/recipes-bsp/u-boot/{u-boot_2017.07.bb => u-boot_2017.09.bb} | 0 4 files changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-bsp/u-boot/{u-boot-common_2017.07.inc => u-boot-common_2017.09.inc} (89%) rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2017.07.bb => u-boot-fw-utils_2017.09.bb} (100%) rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2017.07.bb => u-boot-mkimage_2017.09.bb} (100%) rename meta/recipes-bsp/u-boot/{u-boot_2017.07.bb => u-boot_2017.09.bb} (100%)
diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc b/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc similarity index 89% rename from meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc rename to meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc index e37f5fd409..02e51242cb 100644 --- a/meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc +++ b/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc @@ -7,7 +7,7 @@ PE = "1"
# We use the revision in order to avoid having to fetch it from the # repo during parse -SRCREV = "d85ca029f257b53a96da6c2fb421e78a003a9943" +SRCREV = "c98ac3487e413c71e5d36322ef3324b21c6f60f9"
SRC_URI = "git://git.denx.de/u-boot.git \ file://MPC8315ERDB-enable-DHCP.patch \ diff --git a/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.07.bb b/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.09.bb similarity index 100% rename from meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.07.bb rename to meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.09.bb diff --git a/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.07.bb b/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.09.bb similarity index 100% rename from meta/recipes-bsp/u-boot/u-boot-mkimage_2017.07.bb rename to meta/recipes-bsp/u-boot/u-boot-mkimage_2017.09.bb diff --git a/meta/recipes-bsp/u-boot/u-boot_2017.07.bb b/meta/recipes-bsp/u-boot/u-boot_2017.09.bb similarity index 100% rename from meta/recipes-bsp/u-boot/u-boot_2017.07.bb rename to meta/recipes-bsp/u-boot/u-boot_2017.09.bb -- 2.14.1
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
u-boot-fw-utils-cross is broken for at least a year, if it breaks a lot of boards, why nobody complained yet?
On Mon, Sep 18, 2017 at 7:32 AM, Marek Vasut marek.vasut@gmail.com wrote:
On 09/17/2017 01:06 PM, Martin Jansa wrote:
I've verified that u-boot-fw-utils builds and installs fw_printenv correctly with 2017.07.
And that u-boot-fw-utils-cross was broken even with Yocto 2.3 Pyro and 2017.01 version there, maybe it's time to remove cross version? As nobody is using it and it's not tested?
Nobody apparently even build-tested this patch before submission, gurrr.
Speaking of cross versions of U-Boot fwutils and printenv/setenv , they are used by boards for modifying U-Boot environment on the target from Linux, so removing them would break a lot of boards -- NAK.
On Sun, Sep 17, 2017 at 11:18 AM, Martin Jansa martin.jansa@gmail.com wrote:
Is anyone seeing u-boot-fw-utils.do_install failure with this?
u-boot-fw-utils/1_2017.09-r0/git/tools/env/fw_printenv: No such file or directory
I've tried u-boot-fw-utils-cross, but it fails as well even sooner in do_compile:
Log data follows: | DEBUG: Executing shell function do_compile | NOTE: make -j 32 ARCH=arm CC=gcc -isystemwork/x86_64-linux/u- boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/usr/include -O2 -pipe -Lwork/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/
recipe-sysroot-native/usr/lib
-Lwork/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/
recipe-sysroot-native/lib
-Wl,-rpath-link,work/x86_64-linux/u-boot-fw-utils-cross/1_ 2017.09-r0/recipe-sysroot-native/usr/lib -Wl,-rpath-link,work/x86_64- linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/lib -Wl,-rpath,work/x86_64-linux/u-boot-fw-utils-cross/1_2017. 09-r0/recipe-sysroot-native/usr/lib -Wl,-rpath,work/x86_64-linux/ u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/lib -Wl,-O1
V=1
rpi_3_32b_config | make -f ./scripts/Makefile.build obj=scripts/basic | cc -Wp,-MD,scripts/basic/.fixdep.d -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o scripts/basic/fixdep scripts/basic/fixdep.c | /bin/sh: 1: cc: not found | make[1]: *** [scripts/basic/fixdep] Error 127 | make: *** [scripts_basic] Error 2 | ERROR: oe_runmake failed | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_compile (log file is located at work/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/temp/ log.do_compile.12859) ERROR: Task (virtual:cross:oe-core/meta/recipes-bsp/u-boot/u-boot-fw- utils_2017.09.bb:do_compile) failed with exit code '1'
On Mon, Sep 11, 2017 at 10:30 PM, Otavio Salvador <
otavio@ossystems.com.br
wrote:
This upgrades the U-Boot to the 2017.09 release.
Signed-off-by: Otavio Salvador otavio@ossystems.com.br
.../u-boot/{u-boot-common_2017.07.inc => u-boot-common_2017.09.inc} | 2 +- .../u-boot/{u-boot-fw-utils_2017.07.bb => u-boot-fw-utils_2017.09.bb} | 0 .../u-boot/{u-boot-mkimage_2017.07.bb => u-boot-mkimage_2017.09.bb} | 0 meta/recipes-bsp/u-boot/{u-boot_2017.07.bb => u-boot_2017.09.bb} | 0 4 files changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-bsp/u-boot/{u-boot-common_2017.07.inc => u-boot-common_2017.09.inc} (89%) rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2017.07.bb => u-boot-fw-utils_2017.09.bb} (100%) rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2017.07.bb => u-boot-mkimage_2017.09.bb} (100%) rename meta/recipes-bsp/u-boot/{u-boot_2017.07.bb =>
u-boot_2017.09.bb}
(100%)
diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc b/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc similarity index 89% rename from meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc rename to meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc index e37f5fd409..02e51242cb 100644 --- a/meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc +++ b/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc @@ -7,7 +7,7 @@ PE = "1"
# We use the revision in order to avoid having to fetch it from the # repo during parse -SRCREV = "d85ca029f257b53a96da6c2fb421e78a003a9943" +SRCREV = "c98ac3487e413c71e5d36322ef3324b21c6f60f9"
SRC_URI = "git://git.denx.de/u-boot.git \ file://MPC8315ERDB-enable-DHCP.patch \ diff --git a/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.07.bb b/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.09.bb similarity index 100% rename from meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.07.bb rename to meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.09.bb diff --git a/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.07.bb b/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.09.bb similarity index 100% rename from meta/recipes-bsp/u-boot/u-boot-mkimage_2017.07.bb rename to meta/recipes-bsp/u-boot/u-boot-mkimage_2017.09.bb diff --git a/meta/recipes-bsp/u-boot/u-boot_2017.07.bb b/meta/recipes-bsp/u-boot/u-boot_2017.09.bb similarity index 100% rename from meta/recipes-bsp/u-boot/u-boot_2017.07.bb rename to meta/recipes-bsp/u-boot/u-boot_2017.09.bb -- 2.14.1
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
-- Best regards, Marek Vasut
On 09/18/2017 09:54 AM, Martin Jansa wrote:
u-boot-fw-utils-cross is broken for at least a year, if it breaks a lot of boards, why nobody complained yet?
Didn't you say it worked for 2017.07 or did I misunderstand that ?
btw stop top-posting please.
On Mon, Sep 18, 2017 at 7:32 AM, Marek Vasut <marek.vasut@gmail.com mailto:marek.vasut@gmail.com> wrote:
On 09/17/2017 01:06 PM, Martin Jansa wrote: > I've verified that u-boot-fw-utils builds and installs fw_printenv > correctly with 2017.07. > > And that u-boot-fw-utils-cross was broken even with Yocto 2.3 Pyro > and 2017.01 version there, maybe it's time to remove cross version? As > nobody is using it and it's not tested? Nobody apparently even build-tested this patch before submission, gurrr. Speaking of cross versions of U-Boot fwutils and printenv/setenv , they are used by boards for modifying U-Boot environment on the target from Linux, so removing them would break a lot of boards -- NAK. > On Sun, Sep 17, 2017 at 11:18 AM, Martin Jansa <martin.jansa@gmail.com <mailto:martin.jansa@gmail.com>> > wrote: > >> Is anyone seeing u-boot-fw-utils.do_install failure with this? >> >> u-boot-fw-utils/1_2017.09-r0/git/tools/env/fw_printenv: No such file or >> directory >> >> I've tried u-boot-fw-utils-cross, but it fails as well even sooner in >> do_compile: >> >> Log data follows: >> | DEBUG: Executing shell function do_compile >> | NOTE: make -j 32 ARCH=arm CC=gcc -isystemwork/x86_64-linux/u- >> boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/usr/include -O2 >> -pipe -Lwork/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/usr/lib >> -Lwork/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/lib >> -Wl,-rpath-link,work/x86_64-linux/u-boot-fw-utils-cross/1_ >> 2017.09-r0/recipe-sysroot-native/usr/lib -Wl,-rpath-link,work/x86_64- >> linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/lib >> -Wl,-rpath,work/x86_64-linux/u-boot-fw-utils-cross/1_2017. >> 09-r0/recipe-sysroot-native/usr/lib -Wl,-rpath,work/x86_64-linux/ >> u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/lib -Wl,-O1 V=1 >> rpi_3_32b_config >> | make -f ./scripts/Makefile.build obj=scripts/basic >> | cc -Wp,-MD,scripts/basic/.fixdep.d -Wall -Wstrict-prototypes -O2 >> -fomit-frame-pointer -o scripts/basic/fixdep scripts/basic/fixdep.c >> | /bin/sh: 1: cc: not found >> | make[1]: *** [scripts/basic/fixdep] Error 127 >> | make: *** [scripts_basic] Error 2 >> | ERROR: oe_runmake failed >> | WARNING: exit code 1 from a shell command. >> | ERROR: Function failed: do_compile (log file is located at >> work/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/temp/ >> log.do_compile.12859) >> ERROR: Task (virtual:cross:oe-core/meta/recipes-bsp/u-boot/u-boot-fw- >> utils_2017.09.bb:do_compile) failed with exit code '1' >> >> >> On Mon, Sep 11, 2017 at 10:30 PM, Otavio Salvador <otavio@ossystems.com.br <mailto:otavio@ossystems.com.br> >>> wrote: >> >>> This upgrades the U-Boot to the 2017.09 release. >>> >>> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br <mailto:otavio@ossystems.com.br>> >>> --- >>> >>> .../u-boot/{u-boot-common_2017.07.inc => u-boot-common_2017.09.inc} >>> | 2 +- >>> .../u-boot/{u-boot-fw-utils_2017.07.bb <http://u-boot-fw-utils_2017.07.bb> => u-boot-fw-utils_2017.09.bb <http://u-boot-fw-utils_2017.09.bb>} >>> | 0 >>> .../u-boot/{u-boot-mkimage_2017.07.bb <http://u-boot-mkimage_2017.07.bb> => u-boot-mkimage_2017.09.bb <http://u-boot-mkimage_2017.09.bb>} >>> | 0 >>> meta/recipes-bsp/u-boot/{u-boot_2017.07.bb <http://u-boot_2017.07.bb> => u-boot_2017.09.bb <http://u-boot_2017.09.bb>} >>> | 0 >>> 4 files changed, 1 insertion(+), 1 deletion(-) >>> rename meta/recipes-bsp/u-boot/{u-boot-common_2017.07.inc => >>> u-boot-common_2017.09.inc} (89%) >>> rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2017.07.bb <http://u-boot-fw-utils_2017.07.bb> => >>> u-boot-fw-utils_2017.09.bb <http://u-boot-fw-utils_2017.09.bb>} (100%) >>> rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2017.07.bb <http://u-boot-mkimage_2017.07.bb> => >>> u-boot-mkimage_2017.09.bb <http://u-boot-mkimage_2017.09.bb>} (100%) >>> rename meta/recipes-bsp/u-boot/{u-boot_2017.07.bb <http://u-boot_2017.07.bb> => u-boot_2017.09.bb <http://u-boot_2017.09.bb>} >>> (100%) >>> >>> diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc >>> b/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc >>> similarity index 89% >>> rename from meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc >>> rename to meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc >>> index e37f5fd409..02e51242cb 100644 >>> --- a/meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc >>> +++ b/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc >>> @@ -7,7 +7,7 @@ PE = "1" >>> >>> # We use the revision in order to avoid having to fetch it from the >>> # repo during parse >>> -SRCREV = "d85ca029f257b53a96da6c2fb421e78a003a9943" >>> +SRCREV = "c98ac3487e413c71e5d36322ef3324b21c6f60f9" >>> >>> SRC_URI = "git://git.denx.de/u-boot.git <http://git.denx.de/u-boot.git> \ >>> file://MPC8315ERDB-enable-DHCP.patch \ >>> diff --git a/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.07.bb <http://u-boot-fw-utils_2017.07.bb> >>> b/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.09.bb <http://u-boot-fw-utils_2017.09.bb> >>> similarity index 100% >>> rename from meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.07.bb <http://u-boot-fw-utils_2017.07.bb> >>> rename to meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.09.bb <http://u-boot-fw-utils_2017.09.bb> >>> diff --git a/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.07.bb <http://u-boot-mkimage_2017.07.bb> >>> b/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.09.bb <http://u-boot-mkimage_2017.09.bb> >>> similarity index 100% >>> rename from meta/recipes-bsp/u-boot/u-boot-mkimage_2017.07.bb <http://u-boot-mkimage_2017.07.bb> >>> rename to meta/recipes-bsp/u-boot/u-boot-mkimage_2017.09.bb <http://u-boot-mkimage_2017.09.bb> >>> diff --git a/meta/recipes-bsp/u-boot/u-boot_2017.07.bb <http://u-boot_2017.07.bb> >>> b/meta/recipes-bsp/u-boot/u-boot_2017.09.bb <http://u-boot_2017.09.bb> >>> similarity index 100% >>> rename from meta/recipes-bsp/u-boot/u-boot_2017.07.bb <http://u-boot_2017.07.bb> >>> rename to meta/recipes-bsp/u-boot/u-boot_2017.09.bb <http://u-boot_2017.09.bb> >>> -- >>> 2.14.1 >>> >>> -- >>> _______________________________________________ >>> Openembedded-core mailing list >>> Openembedded-core@lists.openembedded.org <mailto:Openembedded-core@lists.openembedded.org> >>> http://lists.openembedded.org/mailman/listinfo/openembedded-core <http://lists.openembedded.org/mailman/listinfo/openembedded-core> >>> >> >> > _______________________________________________ > U-Boot mailing list > U-Boot@lists.denx.de <mailto:U-Boot@lists.denx.de> > https://lists.denx.de/listinfo/u-boot <https://lists.denx.de/listinfo/u-boot> > -- Best regards, Marek Vasut
On Mon, Sep 18, 2017 at 10:31:05AM +0200, Marek Vasut wrote:
On 09/18/2017 09:54 AM, Martin Jansa wrote:
u-boot-fw-utils-cross is broken for at least a year, if it breaks a lot of boards, why nobody complained yet?
Didn't you say it worked for 2017.07 or did I misunderstand that ?
u-boot-fw-utils did work, u-boot-fw-utils-cross no, read it again:
And that u-boot-fw-utils-cross was broken even with Yocto 2.3 Pyro and 2017.01 version there, maybe it's time to remove cross version? As nobody is using it and it's not tested?
On 09/18/2017 02:39 AM, Martin Jansa wrote:
On Mon, Sep 18, 2017 at 10:31:05AM +0200, Marek Vasut wrote:
On 09/18/2017 09:54 AM, Martin Jansa wrote:
u-boot-fw-utils-cross is broken for at least a year, if it breaks a lot of boards, why nobody complained yet?
Didn't you say it worked for 2017.07 or did I misunderstand that ?
u-boot-fw-utils did work, u-boot-fw-utils-cross no, read it again:
And that u-boot-fw-utils-cross was broken even with Yocto 2.3 Pyro and 2017.01 version there, maybe it's time to remove cross version? As nobody is using it and it's not tested?
What is the policy on doing u-boot version upgrades this late in the release cycle? SHouldn't this wait until after the release?
Philip
Em 18 de set de 2017 12:20 PM, "Philip Balister" philip@balister.org escreveu:
On 09/18/2017 02:39 AM, Martin Jansa wrote:
On Mon, Sep 18, 2017 at 10:31:05AM +0200, Marek Vasut wrote:
On 09/18/2017 09:54 AM, Martin Jansa wrote:
u-boot-fw-utils-cross is broken for at least a year, if it breaks a lot of boards, why nobody complained yet?
Didn't you say it worked for 2017.07 or did I misunderstand that ?
u-boot-fw-utils did work, u-boot-fw-utils-cross no, read it again:
And that u-boot-fw-utils-cross was broken even with Yocto 2.3 Pyro and 2017.01 version there, maybe it's time to remove cross version? As nobody is using it and it's not tested?
What is the policy on doing u-boot version upgrades this late in the release cycle? SHouldn't this wait until after the release?
Why?
It is just another recipe and we are upgrading to the final release.
As Martin said, it was already broken.
I'll take the responsibility to fix it. But as other packages, upgrades has risk and we have more than enough time to proper fix it.
On 18 September 2017 at 16:46, Otavio Salvador < otavio.salvador@ossystems.com.br> wrote:
What is the policy on doing u-boot version upgrades this late in the
release cycle? SHouldn't this wait until after the release?
Why?
It is just another recipe and we are upgrading to the final release.
As Martin said, it was already broken.
I'll take the responsibility to fix it. But as other packages, upgrades has risk and we have more than enough time to proper fix it.
Why? Because it was merged to master after the freeze.
Personally I'm of the opinion that u-boot is one of those special recipes that if an upgrade appears just after freeze, we consider it. If we don't keep it up to date BSPs won't use the recipe, and we'll be back to every BSP layer containing its own special copy of the u-boot recipe.
Ross
On Mon, Sep 18, 2017 at 04:51:31PM +0100, Burton, Ross wrote:
On 18 September 2017 at 16:46, Otavio Salvador < otavio.salvador@ossystems.com.br> wrote:
What is the policy on doing u-boot version upgrades this late in the
release cycle? SHouldn't this wait until after the release?
Why?
It is just another recipe and we are upgrading to the final release.
As Martin said, it was already broken.
I'll take the responsibility to fix it. But as other packages, upgrades has risk and we have more than enough time to proper fix it.
Why? Because it was merged to master after the freeze.
Personally I'm of the opinion that u-boot is one of those special recipes that if an upgrade appears just after freeze, we consider it. If we don't keep it up to date BSPs won't use the recipe, and we'll be back to every BSP layer containing its own special copy of the u-boot recipe.
Also please note that U-Boot has a rather regular and public release schedule: http://www.denx.de/wiki/U-Boot/ReleaseCycle so you can have a good idea beforehand if you want to grab something for a release or not.
Personally, I would like to see this in. But the security issue that's been disclosed now is "resolved" just by not enabling functionality that no one was enabling in mainline, and will be removed in the next release, so don't feel you need to pull it in on those grounds.
On 09/18/2017 06:06 PM, Tom Rini wrote:
On Mon, Sep 18, 2017 at 04:51:31PM +0100, Burton, Ross wrote:
On 18 September 2017 at 16:46, Otavio Salvador < otavio.salvador@ossystems.com.br> wrote:
What is the policy on doing u-boot version upgrades this late in the
release cycle? SHouldn't this wait until after the release?
Why?
It is just another recipe and we are upgrading to the final release.
As Martin said, it was already broken.
I'll take the responsibility to fix it. But as other packages, upgrades has risk and we have more than enough time to proper fix it.
Why? Because it was merged to master after the freeze.
Personally I'm of the opinion that u-boot is one of those special recipes that if an upgrade appears just after freeze, we consider it. If we don't keep it up to date BSPs won't use the recipe, and we'll be back to every BSP layer containing its own special copy of the u-boot recipe.
Also please note that U-Boot has a rather regular and public release schedule: http://www.denx.de/wiki/U-Boot/ReleaseCycle so you can have a good idea beforehand if you want to grab something for a release or not.
Personally, I would like to see this in. But the security issue that's been disclosed now is "resolved" just by not enabling functionality that no one was enabling in mainline, and will be removed in the next release, so don't feel you need to pull it in on those grounds.
I agree that the 2017.09 upgrade is a good idea.
On 09/19/2017 04:15 AM, Marek Vasut wrote:
On 09/18/2017 06:06 PM, Tom Rini wrote:
On Mon, Sep 18, 2017 at 04:51:31PM +0100, Burton, Ross wrote:
On 18 September 2017 at 16:46, Otavio Salvador < otavio.salvador@ossystems.com.br> wrote:
What is the policy on doing u-boot version upgrades this late in the
release cycle? SHouldn't this wait until after the release?
Why?
It is just another recipe and we are upgrading to the final release.
As Martin said, it was already broken.
I'll take the responsibility to fix it. But as other packages, upgrades has risk and we have more than enough time to proper fix it.
Why? Because it was merged to master after the freeze.
Personally I'm of the opinion that u-boot is one of those special recipes that if an upgrade appears just after freeze, we consider it. If we don't keep it up to date BSPs won't use the recipe, and we'll be back to every BSP layer containing its own special copy of the u-boot recipe.
Also please note that U-Boot has a rather regular and public release schedule: http://www.denx.de/wiki/U-Boot/ReleaseCycle so you can have a good idea beforehand if you want to grab something for a release or not.
Personally, I would like to see this in. But the security issue that's been disclosed now is "resolved" just by not enabling functionality that no one was enabling in mainline, and will be removed in the next release, so don't feel you need to pull it in on those grounds.
I agree that the 2017.09 upgrade is a good idea.
OK, I just wanted to make sure everyone was on the same page about timing of the update. We certainly don't want very many recipes to decide they are special and take version bumps right up to release.
Philip
On 09/21/2017 11:35 PM, Philip Balister wrote:
On 09/19/2017 04:15 AM, Marek Vasut wrote:
On 09/18/2017 06:06 PM, Tom Rini wrote:
On Mon, Sep 18, 2017 at 04:51:31PM +0100, Burton, Ross wrote:
On 18 September 2017 at 16:46, Otavio Salvador < otavio.salvador@ossystems.com.br> wrote:
What is the policy on doing u-boot version upgrades this late in the
release cycle? SHouldn't this wait until after the release?
Why?
It is just another recipe and we are upgrading to the final release.
As Martin said, it was already broken.
I'll take the responsibility to fix it. But as other packages, upgrades has risk and we have more than enough time to proper fix it.
Why? Because it was merged to master after the freeze.
Personally I'm of the opinion that u-boot is one of those special recipes that if an upgrade appears just after freeze, we consider it. If we don't keep it up to date BSPs won't use the recipe, and we'll be back to every BSP layer containing its own special copy of the u-boot recipe.
Also please note that U-Boot has a rather regular and public release schedule: http://www.denx.de/wiki/U-Boot/ReleaseCycle so you can have a good idea beforehand if you want to grab something for a release or not.
Personally, I would like to see this in. But the security issue that's been disclosed now is "resolved" just by not enabling functionality that no one was enabling in mainline, and will be removed in the next release, so don't feel you need to pull it in on those grounds.
I agree that the 2017.09 upgrade is a good idea.
OK, I just wanted to make sure everyone was on the same page about timing of the update. We certainly don't want very many recipes to decide they are special and take version bumps right up to release.
Agreed. So what is the conclusion here about this , are we updating to 2017.09 or not ?
Philip
Hi Marek,
On Fri, Sep 22, 2017 at 3:19 PM, Marek Vasut marex@denx.de wrote:
On 09/21/2017 11:35 PM, Philip Balister wrote:
On 09/19/2017 04:15 AM, Marek Vasut wrote:
On 09/18/2017 06:06 PM, Tom Rini wrote:
On Mon, Sep 18, 2017 at 04:51:31PM +0100, Burton, Ross wrote:
On 18 September 2017 at 16:46, Otavio Salvador < otavio.salvador@ossystems.com.br> wrote:
What is the policy on doing u-boot version upgrades this late in the
release cycle? SHouldn't this wait until after the release?
Why?
It is just another recipe and we are upgrading to the final release.
As Martin said, it was already broken.
I'll take the responsibility to fix it. But as other packages, upgrades has risk and we have more than enough time to proper fix it.
Why? Because it was merged to master after the freeze.
Personally I'm of the opinion that u-boot is one of those special recipes that if an upgrade appears just after freeze, we consider it. If we don't keep it up to date BSPs won't use the recipe, and we'll be back to every BSP layer containing its own special copy of the u-boot recipe.
Also please note that U-Boot has a rather regular and public release schedule: http://www.denx.de/wiki/U-Boot/ReleaseCycle so you can have a good idea beforehand if you want to grab something for a release or not.
Personally, I would like to see this in. But the security issue that's been disclosed now is "resolved" just by not enabling functionality that no one was enabling in mainline, and will be removed in the next release, so don't feel you need to pull it in on those grounds.
I agree that the 2017.09 upgrade is a good idea.
OK, I just wanted to make sure everyone was on the same page about timing of the update. We certainly don't want very many recipes to decide they are special and take version bumps right up to release.
Agreed. So what is the conclusion here about this , are we updating to 2017.09 or not ?
+1 for upgrade.
- morats
Philip
-- Best regards, Marek Vasut -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
On Sat, Sep 23, 2017 at 12:19:27AM +0200, Marek Vasut wrote:
Agreed. So what is the conclusion here about this , are we updating to 2017.09 or not ?
It was already merged couple days ago: http://git.openembedded.org/openembedded-core/commit/?id=340d413f678a4a64dfa...
and the follow-up fix for u-boot-fw-utils as well: http://git.openembedded.org/openembedded-core/commit/?id=73afabf8e69019f08b4...
On 09/23/2017 01:36 AM, Martin Jansa wrote:
On Sat, Sep 23, 2017 at 12:19:27AM +0200, Marek Vasut wrote:
Agreed. So what is the conclusion here about this , are we updating to 2017.09 or not ?
It was already merged couple days ago: http://git.openembedded.org/openembedded-core/commit/?id=340d413f678a4a64dfa...
and the follow-up fix for u-boot-fw-utils as well: http://git.openembedded.org/openembedded-core/commit/?id=73afabf8e69019f08b4...
Super, thanks.
On Sun, Sep 17, 2017 at 2:18 AM, Martin Jansa martin.jansa@gmail.com wrote:
Is anyone seeing u-boot-fw-utils.do_install failure with this?
I am seeing same failures too. havent yet dug into it.
u-boot-fw-utils/1_2017.09-r0/git/tools/env/fw_printenv: No such file or directory
I've tried u-boot-fw-utils-cross, but it fails as well even sooner in do_compile:
Log data follows: | DEBUG: Executing shell function do_compile | NOTE: make -j 32 ARCH=arm CC=gcc -isystemwork/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/usr/include -O2 -pipe -Lwork/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/usr/lib -Lwork/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/lib -Wl,-rpath-link,work/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/usr/lib -Wl,-rpath-link,work/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/lib -Wl,-rpath,work/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/usr/lib -Wl,-rpath,work/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/lib -Wl,-O1 V=1 rpi_3_32b_config | make -f ./scripts/Makefile.build obj=scripts/basic | cc -Wp,-MD,scripts/basic/.fixdep.d -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o scripts/basic/fixdep scripts/basic/fixdep.c | /bin/sh: 1: cc: not found | make[1]: *** [scripts/basic/fixdep] Error 127 | make: *** [scripts_basic] Error 2 | ERROR: oe_runmake failed | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_compile (log file is located at work/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/temp/log.do_compile.12859) ERROR: Task (virtual:cross:oe-core/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.09.bb:do_compile) failed with exit code '1'
On Mon, Sep 11, 2017 at 10:30 PM, Otavio Salvador otavio@ossystems.com.br wrote:
This upgrades the U-Boot to the 2017.09 release.
Signed-off-by: Otavio Salvador otavio@ossystems.com.br
.../u-boot/{u-boot-common_2017.07.inc => u-boot-common_2017.09.inc} | 2 +- .../u-boot/{u-boot-fw-utils_2017.07.bb => u-boot-fw-utils_2017.09.bb} | 0 .../u-boot/{u-boot-mkimage_2017.07.bb => u-boot-mkimage_2017.09.bb} | 0 meta/recipes-bsp/u-boot/{u-boot_2017.07.bb => u-boot_2017.09.bb} | 0 4 files changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-bsp/u-boot/{u-boot-common_2017.07.inc => u-boot-common_2017.09.inc} (89%) rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2017.07.bb => u-boot-fw-utils_2017.09.bb} (100%) rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2017.07.bb => u-boot-mkimage_2017.09.bb} (100%) rename meta/recipes-bsp/u-boot/{u-boot_2017.07.bb => u-boot_2017.09.bb} (100%)
diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc b/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc similarity index 89% rename from meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc rename to meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc index e37f5fd409..02e51242cb 100644 --- a/meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc +++ b/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc @@ -7,7 +7,7 @@ PE = "1"
# We use the revision in order to avoid having to fetch it from the # repo during parse -SRCREV = "d85ca029f257b53a96da6c2fb421e78a003a9943" +SRCREV = "c98ac3487e413c71e5d36322ef3324b21c6f60f9"
SRC_URI = "git://git.denx.de/u-boot.git \ file://MPC8315ERDB-enable-DHCP.patch \ diff --git a/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.07.bb b/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.09.bb similarity index 100% rename from meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.07.bb rename to meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.09.bb diff --git a/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.07.bb b/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.09.bb similarity index 100% rename from meta/recipes-bsp/u-boot/u-boot-mkimage_2017.07.bb rename to meta/recipes-bsp/u-boot/u-boot-mkimage_2017.09.bb diff --git a/meta/recipes-bsp/u-boot/u-boot_2017.07.bb b/meta/recipes-bsp/u-boot/u-boot_2017.09.bb similarity index 100% rename from meta/recipes-bsp/u-boot/u-boot_2017.07.bb rename to meta/recipes-bsp/u-boot/u-boot_2017.09.bb -- 2.14.1
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Hi Khem,
On Sun, Sep 17, 2017 at 2:18 AM, Martin Jansa martin.jansa@gmail.com wrote:
Is anyone seeing u-boot-fw-utils.do_install failure with this?
I am seeing same failures too. havent yet dug into it.
Please pay note to change in directory structure in u-boot envs (from 2017.09):
Now to build fw_printenv one needs to run:
do_compile () { oe_runmake ${UBOOT_MACHINE} oe_runmake envtools (<- was env) }
And Yes, I do agree with Marek, fw_printf is widely used on many, many boards .....
u-boot-fw-utils/1_2017.09-r0/git/tools/env/fw_printenv: No such file or directory
I've tried u-boot-fw-utils-cross, but it fails as well even sooner in do_compile:
Log data follows: | DEBUG: Executing shell function do_compile | NOTE: make -j 32 ARCH=arm CC=gcc -isystemwork/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/usr/include -O2 -pipe -Lwork/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/usr/lib -Lwork/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/lib -Wl,-rpath-link,work/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/usr/lib -Wl,-rpath-link,work/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/lib -Wl,-rpath,work/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/usr/lib -Wl,-rpath,work/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/recipe-sysroot-native/lib -Wl,-O1 V=1 rpi_3_32b_config | make -f ./scripts/Makefile.build obj=scripts/basic | cc -Wp,-MD,scripts/basic/.fixdep.d -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o scripts/basic/fixdep scripts/basic/fixdep.c | /bin/sh: 1: cc: not found | make[1]: *** [scripts/basic/fixdep] Error 127 | make: *** [scripts_basic] Error 2 | ERROR: oe_runmake failed | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_compile (log file is located at work/x86_64-linux/u-boot-fw-utils-cross/1_2017.09-r0/temp/log.do_compile.12859) ERROR: Task (virtual:cross:oe-core/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.09.bb:do_compile) failed with exit code '1'
On Mon, Sep 11, 2017 at 10:30 PM, Otavio Salvador otavio@ossystems.com.br wrote:
This upgrades the U-Boot to the 2017.09 release.
Signed-off-by: Otavio Salvador otavio@ossystems.com.br
.../u-boot/{u-boot-common_2017.07.inc => u-boot-common_2017.09.inc} | 2 +- .../u-boot/{u-boot-fw-utils_2017.07.bb => u-boot-fw-utils_2017.09.bb} | 0 .../u-boot/{u-boot-mkimage_2017.07.bb => u-boot-mkimage_2017.09.bb} | 0 meta/recipes-bsp/u-boot/{u-boot_2017.07.bb => u-boot_2017.09.bb} | 0 4 files changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-bsp/u-boot/{u-boot-common_2017.07.inc => u-boot-common_2017.09.inc} (89%) rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2017.07.bb => u-boot-fw-utils_2017.09.bb} (100%) rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2017.07.bb => u-boot-mkimage_2017.09.bb} (100%) rename meta/recipes-bsp/u-boot/{u-boot_2017.07.bb => u-boot_2017.09.bb} (100%)
diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc b/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc similarity index 89% rename from meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc rename to meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc index e37f5fd409..02e51242cb 100644 --- a/meta/recipes-bsp/u-boot/u-boot-common_2017.07.inc +++ b/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc @@ -7,7 +7,7 @@ PE = "1"
# We use the revision in order to avoid having to fetch it from the # repo during parse -SRCREV = "d85ca029f257b53a96da6c2fb421e78a003a9943" +SRCREV = "c98ac3487e413c71e5d36322ef3324b21c6f60f9"
SRC_URI = "git://git.denx.de/u-boot.git \ file://MPC8315ERDB-enable-DHCP.patch \ diff --git a/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.07.bb b/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.09.bb similarity index 100% rename from meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.07.bb rename to meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.09.bb diff --git a/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.07.bb b/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.09.bb similarity index 100% rename from meta/recipes-bsp/u-boot/u-boot-mkimage_2017.07.bb rename to meta/recipes-bsp/u-boot/u-boot-mkimage_2017.09.bb diff --git a/meta/recipes-bsp/u-boot/u-boot_2017.07.bb b/meta/recipes-bsp/u-boot/u-boot_2017.09.bb similarity index 100% rename from meta/recipes-bsp/u-boot/u-boot_2017.07.bb rename to meta/recipes-bsp/u-boot/u-boot_2017.09.bb -- 2.14.1
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
On 2017-09-17 11:35 AM, Khem Raj wrote:
I am seeing same failures too. havent yet dug into it.
Same here.
Jackie said that he's going to investigate now.
We've only seen this failure since 2017-09-15 06:00 AM ET after we rebased onto 2017-09-14 content/ this commit: 583dca2 meta/conf/layers.conf: Add ca-certificates as ABISAFE 75e918d linux-firmware: package Marvell PCIe WiFi firmwares 0001cee insane: don't pass skip list to functions which don't ... 340d413 u-boot: Upgrade to 2017.09 ...
participants (12)
-
Burton, Ross -
Khem Raj -
Marek Vasut -
Marek Vasut -
Martin Jansa -
Moritz Fischer -
Otavio Salvador -
Otavio Salvador -
Philip Balister -
Randy MacLeod -
Tom Rini -
Łukasz Majewski