[PATCH] u-boot: Upgrade to 2018.03 release

[PATCH] u-boot: Upgrade to 2018.03 release

[Marek Vasut]

This upgrades the U-Boot from 2018.01 to 2018.03 release and drops
patches accepted upstream, getting the patch count to zero.

Signed-off-by: Marek Vasut <marex@denx.de>
Cc: Otavio Salvador <otavio@ossystems.com.br>
Cc: Ross Burton <ross.burton@intel.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>
---
 .../u-boot/files/MPC8315ERDB-enable-DHCP.patch        | 19 -------------------
 ...t-common_2018.01.inc => u-boot-common_2018.03.inc} |  6 ++----
 ...fw-utils_2018.01.bb => u-boot-fw-utils_2018.03.bb} |  0
 ...t-mkimage_2018.01.bb => u-boot-mkimage_2018.03.bb} |  0
 .../u-boot/{u-boot_2018.01.bb => u-boot_2018.03.bb}   |  0
 5 files changed, 2 insertions(+), 23 deletions(-)
 delete mode 100644 meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
 rename meta/recipes-bsp/u-boot/{u-boot-common_2018.01.inc => u-boot-common_2018.03.inc} (68%)
 rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2018.01.bb => u-boot-fw-utils_2018.03.bb} (100%)
 rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2018.01.bb => u-boot-mkimage_2018.03.bb} (100%)
 rename meta/recipes-bsp/u-boot/{u-boot_2018.01.bb => u-boot_2018.03.bb} (100%)

diff --git a/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch b/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
deleted file mode 100644
index ecaa1796a4..0000000000
--- a/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
+++ /dev/null
@@ -1,19 +0,0 @@
-Enabled dhcp client functionality for Yocto reference
-hardware MPC8315E-RDB.
-
-Upstream-Status: Pending
-
-Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
-
-Index: git/configs/MPC8315ERDB_defconfig
-===================================================================
---- git.orig/configs/MPC8315ERDB_defconfig
-+++ git/configs/MPC8315ERDB_defconfig
-@@ -12,6 +12,7 @@ CONFIG_CMD_PCI=y
- CONFIG_CMD_SATA=y
- CONFIG_CMD_USB=y
- # CONFIG_CMD_SETEXPR is not set
-+CONFIG_CMD_DHCP=y
- CONFIG_CMD_MII=y
- CONFIG_CMD_PING=y
- CONFIG_CMD_DATE=y
diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2018.01.inc b/meta/recipes-bsp/u-boot/u-boot-common_2018.03.inc
similarity index 68%
rename from meta/recipes-bsp/u-boot/u-boot-common_2018.01.inc
rename to meta/recipes-bsp/u-boot/u-boot-common_2018.03.inc
index d2073ea0c7..8ffae365a9 100644
--- a/meta/recipes-bsp/u-boot/u-boot-common_2018.01.inc
+++ b/meta/recipes-bsp/u-boot/u-boot-common_2018.03.inc
@@ -7,10 +7,8 @@ PE = "1"
 
 # We use the revision in order to avoid having to fetch it from the
 # repo during parse
-SRCREV = "f3dd87e0b98999a78e500e8c6d2b063ebadf535a"
+SRCREV = "f95ab1fb6e37f0601f397091bb011edf7a98b890"
 
-SRC_URI = "git://git.denx.de/u-boot.git \
-    file://MPC8315ERDB-enable-DHCP.patch \
-"
+SRC_URI = "git://git.denx.de/u-boot.git"
 
 S = "${WORKDIR}/git"
diff --git a/meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.01.bb b/meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.03.bb
similarity index 100%
rename from meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.01.bb
rename to meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.03.bb
diff --git a/meta/recipes-bsp/u-boot/u-boot-mkimage_2018.01.bb b/meta/recipes-bsp/u-boot/u-boot-mkimage_2018.03.bb
similarity index 100%
rename from meta/recipes-bsp/u-boot/u-boot-mkimage_2018.01.bb
rename to meta/recipes-bsp/u-boot/u-boot-mkimage_2018.03.bb
diff --git a/meta/recipes-bsp/u-boot/u-boot_2018.01.bb b/meta/recipes-bsp/u-boot/u-boot_2018.03.bb
similarity index 100%
rename from meta/recipes-bsp/u-boot/u-boot_2018.01.bb
rename to meta/recipes-bsp/u-boot/u-boot_2018.03.bb
-- 
2.16.2

Re: [PATCH] u-boot: Upgrade to 2018.03 release

[Khem Raj]

[-- Attachment #1: Type: text/plain, Size: 4241 bytes --]

On Sun, Apr 8, 2018 at 4:10 PM Marek Vasut <marex@denx.de> wrote:

> This upgrades the U-Boot from 2018.01 to 2018.03 release and drops
> patches accepted upstream, getting the patch count to zero.



It fails for me if I have libfdt installed on build host
It seems build is doing the include dance which goes all the way into hosts
system include directories

>
>
> Signed-off-by: Marek Vasut <marex@denx.de>
> Cc: Otavio Salvador <otavio@ossystems.com.br>
> Cc: Ross Burton <ross.burton@intel.com>
> Cc: Richard Purdie <richard.purdie@linuxfoundation.org>
> ---
>  .../u-boot/files/MPC8315ERDB-enable-DHCP.patch        | 19
> -------------------
>  ...t-common_2018.01.inc => u-boot-common_2018.03.inc} |  6 ++----
>  ...fw-utils_2018.01.bb => u-boot-fw-utils_2018.03.bb} |  0
>  ...t-mkimage_2018.01.bb => u-boot-mkimage_2018.03.bb} |  0
>  .../u-boot/{u-boot_2018.01.bb => u-boot_2018.03.bb}   |  0
>  5 files changed, 2 insertions(+), 23 deletions(-)
>  delete mode 100644
> meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
>  rename meta/recipes-bsp/u-boot/{u-boot-common_2018.01.inc =>
> u-boot-common_2018.03.inc} (68%)
>  rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2018.01.bb =>
> u-boot-fw-utils_2018.03.bb} (100%)
>  rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2018.01.bb =>
> u-boot-mkimage_2018.03.bb} (100%)
>  rename meta/recipes-bsp/u-boot/{u-boot_2018.01.bb => u-boot_2018.03.bb}
> (100%)
>
> diff --git a/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
> b/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
> deleted file mode 100644
> index ecaa1796a4..0000000000
> --- a/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
> +++ /dev/null
> @@ -1,19 +0,0 @@
> -Enabled dhcp client functionality for Yocto reference
> -hardware MPC8315E-RDB.
> -
> -Upstream-Status: Pending
> -
> -Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
> -
> -Index: git/configs/MPC8315ERDB_defconfig
> -===================================================================
> ---- git.orig/configs/MPC8315ERDB_defconfig
> -+++ git/configs/MPC8315ERDB_defconfig
> -@@ -12,6 +12,7 @@ CONFIG_CMD_PCI=y
> - CONFIG_CMD_SATA=y
> - CONFIG_CMD_USB=y
> - # CONFIG_CMD_SETEXPR is not set
> -+CONFIG_CMD_DHCP=y
> - CONFIG_CMD_MII=y
> - CONFIG_CMD_PING=y
> - CONFIG_CMD_DATE=y
> diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2018.01.inc
> b/meta/recipes-bsp/u-boot/u-boot-common_2018.03.inc
> similarity index 68%
> rename from meta/recipes-bsp/u-boot/u-boot-common_2018.01.inc
> rename to meta/recipes-bsp/u-boot/u-boot-common_2018.03.inc
> index d2073ea0c7..8ffae365a9 100644
> --- a/meta/recipes-bsp/u-boot/u-boot-common_2018.01.inc
> +++ b/meta/recipes-bsp/u-boot/u-boot-common_2018.03.inc
> @@ -7,10 +7,8 @@ PE = "1"
>
>  # We use the revision in order to avoid having to fetch it from the
>  # repo during parse
> -SRCREV = "f3dd87e0b98999a78e500e8c6d2b063ebadf535a"
> +SRCREV = "f95ab1fb6e37f0601f397091bb011edf7a98b890"
>
> -SRC_URI = "git://git.denx.de/u-boot.git \
> -    file://MPC8315ERDB-enable-DHCP.patch \
> -"
> +SRC_URI = "git://git.denx.de/u-boot.git"
>
>  S = "${WORKDIR}/git"
> diff --git a/meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.01.bb
> b/meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.03.bb
> similarity index 100%
> rename from meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.01.bb
> rename to meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.03.bb
> diff --git a/meta/recipes-bsp/u-boot/u-boot-mkimage_2018.01.bb
> b/meta/recipes-bsp/u-boot/u-boot-mkimage_2018.03.bb
> similarity index 100%
> rename from meta/recipes-bsp/u-boot/u-boot-mkimage_2018.01.bb
> rename to meta/recipes-bsp/u-boot/u-boot-mkimage_2018.03.bb
> diff --git a/meta/recipes-bsp/u-boot/u-boot_2018.01.bb
> b/meta/recipes-bsp/u-boot/u-boot_2018.03.bb
> similarity index 100%
> rename from meta/recipes-bsp/u-boot/u-boot_2018.01.bb
> rename to meta/recipes-bsp/u-boot/u-boot_2018.03.bb
> --
> 2.16.2
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>

[-- Attachment #2: Type: text/html, Size: 7449 bytes --]

Re: [PATCH] u-boot: Upgrade to 2018.03 release

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 5003 bytes --]

Isn't it fail again because of autodetected swig from host?

Since 2017.07 I have:

do_compile_prepend () {
    sed 's@\(^always += $(if $(shell which swig 2>
/dev/null),_libfdt.so)$\)@# do not autodetect swig, there is no swig-native
dependency \1@g' -i ${S}/tools/Makefile
}

to prevent rebuilding libfdt which was failing because of host headers.

On Mon, Apr 9, 2018 at 2:54 AM, Khem Raj <raj.khem@gmail.com> wrote:

>
> On Sun, Apr 8, 2018 at 4:10 PM Marek Vasut <marex@denx.de> wrote:
>
>> This upgrades the U-Boot from 2018.01 to 2018.03 release and drops
>> patches accepted upstream, getting the patch count to zero.
>
>
>
> It fails for me if I have libfdt installed on build host
> It seems build is doing the include dance which goes all the way into
> hosts system include directories
>
>>
>>
>> Signed-off-by: Marek Vasut <marex@denx.de>
>> Cc: Otavio Salvador <otavio@ossystems.com.br>
>> Cc: Ross Burton <ross.burton@intel.com>
>> Cc: Richard Purdie <richard.purdie@linuxfoundation.org>
>> ---
>>  .../u-boot/files/MPC8315ERDB-enable-DHCP.patch        | 19
>> -------------------
>>  ...t-common_2018.01.inc => u-boot-common_2018.03.inc} |  6 ++----
>>  ...fw-utils_2018.01.bb => u-boot-fw-utils_2018.03.bb} |  0
>>  ...t-mkimage_2018.01.bb => u-boot-mkimage_2018.03.bb} |  0
>>  .../u-boot/{u-boot_2018.01.bb => u-boot_2018.03.bb}   |  0
>>  5 files changed, 2 insertions(+), 23 deletions(-)
>>  delete mode 100644 meta/recipes-bsp/u-boot/files/
>> MPC8315ERDB-enable-DHCP.patch
>>  rename meta/recipes-bsp/u-boot/{u-boot-common_2018.01.inc =>
>> u-boot-common_2018.03.inc} (68%)
>>  rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2018.01.bb =>
>> u-boot-fw-utils_2018.03.bb} (100%)
>>  rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2018.01.bb =>
>> u-boot-mkimage_2018.03.bb} (100%)
>>  rename meta/recipes-bsp/u-boot/{u-boot_2018.01.bb => u-boot_2018.03.bb}
>> (100%)
>>
>> diff --git a/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
>> b/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
>> deleted file mode 100644
>> index ecaa1796a4..0000000000
>> --- a/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
>> +++ /dev/null
>> @@ -1,19 +0,0 @@
>> -Enabled dhcp client functionality for Yocto reference
>> -hardware MPC8315E-RDB.
>> -
>> -Upstream-Status: Pending
>> -
>> -Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
>> -
>> -Index: git/configs/MPC8315ERDB_defconfig
>> -===================================================================
>> ---- git.orig/configs/MPC8315ERDB_defconfig
>> -+++ git/configs/MPC8315ERDB_defconfig
>> -@@ -12,6 +12,7 @@ CONFIG_CMD_PCI=y
>> - CONFIG_CMD_SATA=y
>> - CONFIG_CMD_USB=y
>> - # CONFIG_CMD_SETEXPR is not set
>> -+CONFIG_CMD_DHCP=y
>> - CONFIG_CMD_MII=y
>> - CONFIG_CMD_PING=y
>> - CONFIG_CMD_DATE=y
>> diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2018.01.inc
>> b/meta/recipes-bsp/u-boot/u-boot-common_2018.03.inc
>> similarity index 68%
>> rename from meta/recipes-bsp/u-boot/u-boot-common_2018.01.inc
>> rename to meta/recipes-bsp/u-boot/u-boot-common_2018.03.inc
>> index d2073ea0c7..8ffae365a9 100644
>> --- a/meta/recipes-bsp/u-boot/u-boot-common_2018.01.inc
>> +++ b/meta/recipes-bsp/u-boot/u-boot-common_2018.03.inc
>> @@ -7,10 +7,8 @@ PE = "1"
>>
>>  # We use the revision in order to avoid having to fetch it from the
>>  # repo during parse
>> -SRCREV = "f3dd87e0b98999a78e500e8c6d2b063ebadf535a"
>> +SRCREV = "f95ab1fb6e37f0601f397091bb011edf7a98b890"
>>
>> -SRC_URI = "git://git.denx.de/u-boot.git \
>> -    file://MPC8315ERDB-enable-DHCP.patch \
>> -"
>> +SRC_URI = "git://git.denx.de/u-boot.git"
>>
>>  S = "${WORKDIR}/git"
>> diff --git a/meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.01.bb
>> b/meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.03.bb
>> similarity index 100%
>> rename from meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.01.bb
>> rename to meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.03.bb
>> diff --git a/meta/recipes-bsp/u-boot/u-boot-mkimage_2018.01.bb
>> b/meta/recipes-bsp/u-boot/u-boot-mkimage_2018.03.bb
>> similarity index 100%
>> rename from meta/recipes-bsp/u-boot/u-boot-mkimage_2018.01.bb
>> rename to meta/recipes-bsp/u-boot/u-boot-mkimage_2018.03.bb
>> diff --git a/meta/recipes-bsp/u-boot/u-boot_2018.01.bb
>> b/meta/recipes-bsp/u-boot/u-boot_2018.03.bb
>> similarity index 100%
>> rename from meta/recipes-bsp/u-boot/u-boot_2018.01.bb
>> rename to meta/recipes-bsp/u-boot/u-boot_2018.03.bb
>> --
>> 2.16.2
>>
>> --
>> _______________________________________________
>> 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
>
>

[-- Attachment #2: Type: text/html, Size: 8995 bytes --]

Re: [PATCH] u-boot: Upgrade to 2018.03 release

[Marek Vasut]

On 04/09/2018 02:54 AM, Khem Raj wrote:
> 
> On Sun, Apr 8, 2018 at 4:10 PM Marek Vasut <marex@denx.de
> <mailto:marex@denx.de>> wrote:
> 
>     This upgrades the U-Boot from 2018.01 to 2018.03 release and drops
>     patches accepted upstream, getting the patch count to zero.
> 
> 
> 
> It fails for me if I have libfdt installed on build host 
> It seems build is doing the include dance which goes all the way into
> hosts system include directories 

Which version of libfdt and dtc do you have installed ?
And is it really libfdt or dtc ?

-- 
Best regards,
Marek Vasut

Re: [PATCH] u-boot: Upgrade to 2018.03 release

[Khem Raj]

On Mon, Apr 9, 2018 at 1:25 AM, Marek Vasut <marex@denx.de> wrote:
> On 04/09/2018 02:54 AM, Khem Raj wrote:
>>
>> On Sun, Apr 8, 2018 at 4:10 PM Marek Vasut <marex@denx.de
>> <mailto:marex@denx.de>> wrote:
>>
>>     This upgrades the U-Boot from 2018.01 to 2018.03 release and drops
>>     patches accepted upstream, getting the patch count to zero.
>>
>>
>>
>> It fails for me if I have libfdt installed on build host
>> It seems build is doing the include dance which goes all the way into
>> hosts system include directories
>
> Which version of libfdt and dtc do you have installed ?
> And is it really libfdt or dtc ?
>

its dtc probably but header it picks is libfdt.h I am on archlinux
> --
> Best regards,
> Marek Vasut

Re: [PATCH] u-boot: Upgrade to 2018.03 release

[Marek Vasut]

On 04/09/2018 03:48 PM, Khem Raj wrote:
> On Mon, Apr 9, 2018 at 1:25 AM, Marek Vasut <marex@denx.de> wrote:
>> On 04/09/2018 02:54 AM, Khem Raj wrote:
>>>
>>> On Sun, Apr 8, 2018 at 4:10 PM Marek Vasut <marex@denx.de
>>> <mailto:marex@denx.de>> wrote:
>>>
>>>     This upgrades the U-Boot from 2018.01 to 2018.03 release and drops
>>>     patches accepted upstream, getting the patch count to zero.
>>>
>>>
>>>
>>> It fails for me if I have libfdt installed on build host
>>> It seems build is doing the include dance which goes all the way into
>>> hosts system include directories
>>
>> Which version of libfdt and dtc do you have installed ?
>> And is it really libfdt or dtc ?
>>
> 
> its dtc probably but header it picks is libfdt.h I am on archlinux

So which version of either do you have on your host ?

-- 
Best regards,
Marek Vasut

Re: [PATCH] u-boot: Upgrade to 2018.03 release

[Martin Hundebøll]

[-- Attachment #1: Type: text/plain, Size: 6579 bytes --]

Hi,

I had to patch up our own u-boot recipe as shown in the attached patch 
to make v2018.03 compile for qemu-x86.

The thing is that the build of pylibfdt became unconditional since 
15b97f5c5e ('pylibfdt: move pylibfdt to scripts/dtc/pylibfdt and 
refactor makefile')

In my case u-boot/pylibfdt failed to find the correct (native) headers, 
because python setuptools / distutils looks into STAGING_{LIB,INC}DIR 
when compiling the native extension for libfdt. I didn't find any other 
way to specificy this in either the u-boot Makefile or some other magic 
environment variable.

// Martin

On 2018-04-09 02:54, Khem Raj wrote:
> 
> On Sun, Apr 8, 2018 at 4:10 PM Marek Vasut <marex@denx.de 
> <mailto:marex@denx.de>> wrote:
> 
>     This upgrades the U-Boot from 2018.01 to 2018.03 release and drops
>     patches accepted upstream, getting the patch count to zero.
> 
> 
> 
> It fails for me if I have libfdt installed on build host
> It seems build is doing the include dance which goes all the way into 
> hosts system include directories
> 
> 
> 
>     Signed-off-by: Marek Vasut <marex@denx.de <mailto:marex@denx.de>>
>     Cc: Otavio Salvador <otavio@ossystems.com.br
>     <mailto:otavio@ossystems.com.br>>
>     Cc: Ross Burton <ross.burton@intel.com <mailto:ross.burton@intel.com>>
>     Cc: Richard Purdie <richard.purdie@linuxfoundation.org
>     <mailto:richard.purdie@linuxfoundation.org>>
>     ---
>       .../u-boot/files/MPC8315ERDB-enable-DHCP.patch        | 19
>     -------------------
>       ...t-common_2018.01.inc => u-boot-common_2018.03.inc} |  6 ++----
>       ...fw-utils_2018.01.bb <http://fw-utils_2018.01.bb> =>
>     u-boot-fw-utils_2018.03.bb <http://u-boot-fw-utils_2018.03.bb>} |  0
>       ...t-mkimage_2018.01.bb <http://t-mkimage_2018.01.bb> =>
>     u-boot-mkimage_2018.03.bb <http://u-boot-mkimage_2018.03.bb>} |  0
>       .../u-boot/{u-boot_2018.01.bb <http://u-boot_2018.01.bb> =>
>     u-boot_2018.03.bb <http://u-boot_2018.03.bb>}   |  0
>       5 files changed, 2 insertions(+), 23 deletions(-)
>       delete mode 100644
>     meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
>       rename meta/recipes-bsp/u-boot/{u-boot-common_2018.01.inc =>
>     u-boot-common_2018.03.inc} (68%)
>       rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2018.01.bb
>     <http://u-boot-fw-utils_2018.01.bb> => u-boot-fw-utils_2018.03.bb
>     <http://u-boot-fw-utils_2018.03.bb>} (100%)
>       rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2018.01.bb
>     <http://u-boot-mkimage_2018.01.bb> => u-boot-mkimage_2018.03.bb
>     <http://u-boot-mkimage_2018.03.bb>} (100%)
>       rename meta/recipes-bsp/u-boot/{u-boot_2018.01.bb
>     <http://u-boot_2018.01.bb> => u-boot_2018.03.bb
>     <http://u-boot_2018.03.bb>} (100%)
> 
>     diff --git
>     a/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
>     b/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
>     deleted file mode 100644
>     index ecaa1796a4..0000000000
>     --- a/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
>     +++ /dev/null
>     @@ -1,19 +0,0 @@
>     -Enabled dhcp client functionality for Yocto reference
>     -hardware MPC8315E-RDB.
>     -
>     -Upstream-Status: Pending
>     -
>     -Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com
>     <mailto:ed.bartosh@linux.intel.com>>
>     -
>     -Index: git/configs/MPC8315ERDB_defconfig
>     -===================================================================
>     ---- git.orig/configs/MPC8315ERDB_defconfig
>     -+++ git/configs/MPC8315ERDB_defconfig
>     -@@ -12,6 +12,7 @@ CONFIG_CMD_PCI=y
>     - CONFIG_CMD_SATA=y
>     - CONFIG_CMD_USB=y
>     - # CONFIG_CMD_SETEXPR is not set
>     -+CONFIG_CMD_DHCP=y
>     - CONFIG_CMD_MII=y
>     - CONFIG_CMD_PING=y
>     - CONFIG_CMD_DATE=y
>     diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2018.01.inc
>     b/meta/recipes-bsp/u-boot/u-boot-common_2018.03.inc
>     similarity index 68%
>     rename from meta/recipes-bsp/u-boot/u-boot-common_2018.01.inc
>     rename to meta/recipes-bsp/u-boot/u-boot-common_2018.03.inc
>     index d2073ea0c7..8ffae365a9 100644
>     --- a/meta/recipes-bsp/u-boot/u-boot-common_2018.01.inc
>     +++ b/meta/recipes-bsp/u-boot/u-boot-common_2018.03.inc
>     @@ -7,10 +7,8 @@ PE = "1"
> 
>       # We use the revision in order to avoid having to fetch it from the
>       # repo during parse
>     -SRCREV = "f3dd87e0b98999a78e500e8c6d2b063ebadf535a"
>     +SRCREV = "f95ab1fb6e37f0601f397091bb011edf7a98b890"
> 
>     -SRC_URI = "git://git.denx.de/u-boot.git
>     <http://git.denx.de/u-boot.git> \
>     -    file://MPC8315ERDB-enable-DHCP.patch \
>     -"
>     +SRC_URI = "git://git.denx.de/u-boot.git
>     <http://git.denx.de/u-boot.git>"
> 
>       S = "${WORKDIR}/git"
>     diff --git a/meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.01.bb
>     <http://u-boot-fw-utils_2018.01.bb>
>     b/meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.03.bb
>     <http://u-boot-fw-utils_2018.03.bb>
>     similarity index 100%
>     rename from meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.01.bb
>     <http://u-boot-fw-utils_2018.01.bb>
>     rename to meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.03.bb
>     <http://u-boot-fw-utils_2018.03.bb>
>     diff --git a/meta/recipes-bsp/u-boot/u-boot-mkimage_2018.01.bb
>     <http://u-boot-mkimage_2018.01.bb>
>     b/meta/recipes-bsp/u-boot/u-boot-mkimage_2018.03.bb
>     <http://u-boot-mkimage_2018.03.bb>
>     similarity index 100%
>     rename from meta/recipes-bsp/u-boot/u-boot-mkimage_2018.01.bb
>     <http://u-boot-mkimage_2018.01.bb>
>     rename to meta/recipes-bsp/u-boot/u-boot-mkimage_2018.03.bb
>     <http://u-boot-mkimage_2018.03.bb>
>     diff --git a/meta/recipes-bsp/u-boot/u-boot_2018.01.bb
>     <http://u-boot_2018.01.bb>
>     b/meta/recipes-bsp/u-boot/u-boot_2018.03.bb <http://u-boot_2018.03.bb>
>     similarity index 100%
>     rename from meta/recipes-bsp/u-boot/u-boot_2018.01.bb
>     <http://u-boot_2018.01.bb>
>     rename to meta/recipes-bsp/u-boot/u-boot_2018.03.bb
>     <http://u-boot_2018.03.bb>
>     --
>     2.16.2
> 
>     --
>     _______________________________________________
>     Openembedded-core mailing list
>     Openembedded-core@lists.openembedded.org
>     <mailto:Openembedded-core@lists.openembedded.org>
>     http://lists.openembedded.org/mailman/listinfo/openembedded-core
> 
> 
> 

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-u-boot-pil-fix-cross-compile-for-qemux86.patch --]
[-- Type: text/x-patch; name="0001-u-boot-pil-fix-cross-compile-for-qemux86.patch", Size: 1243 bytes --]

From f037effcf106808fdb42ab84e1424e0d616104a0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Martin=20Hundeb=C3=B8ll?= <mnhu@prevas.dk>
Date: Tue, 3 Apr 2018 15:36:50 +0200
Subject: [PATCH] u-boot-pil: fix cross compile for qemux86
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Signed-off-by: Martin Hundebøll <mnhu@prevas.dk>
---
 recipes-bsp/u-boot/u-boot-pil_git.bb | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/recipes-bsp/u-boot/u-boot-pil_git.bb b/recipes-bsp/u-boot/u-boot-pil_git.bb
index e57ed8c..b5a3f09 100644
--- a/recipes-bsp/u-boot/u-boot-pil_git.bb
+++ b/recipes-bsp/u-boot/u-boot-pil_git.bb
@@ -1,5 +1,6 @@
 DESCRIPTION = "PIL U-Boot"
 
+inherit pythonnative
 require recipes-bsp/u-boot/u-boot.inc
 
 DEPENDS += "bc-native dtc-native swig-native"
@@ -13,4 +14,9 @@ LIC_FILES_CHKSUM = "file://Licenses/gpl-2.0.txt;md5=b234ee4d69f5fce4486a80fdaf4a
 SRC_URI = "git://${TOPDIR}/src/u-boot;protocol=file;nobranch=1"
 SRCREV ?= "9fa7d5863214935fe0f2aca5a4c5edfe25deb848"
 
+do_compile_prepend() {
+    export STAGING_LIBDIR="${STAGING_LIBDIR_NATIVE}"
+    export STAGING_INCDIR="${STAGING_INCDIR_NATIVE}"
+}
+
 S = "${WORKDIR}/git"
-- 
2.17.0

Re: [PATCH] u-boot: Upgrade to 2018.03 release

[Marek Vasut]

On 04/10/2018 11:49 AM, Martin Hundebøll wrote:
> Hi,

Hi,

> I had to patch up our own u-boot recipe as shown in the attached patch
> to make v2018.03 compile for qemu-x86.
> 
> The thing is that the build of pylibfdt became unconditional since
> 15b97f5c5e ('pylibfdt: move pylibfdt to scripts/dtc/pylibfdt and
> refactor makefile')
> 
> In my case u-boot/pylibfdt failed to find the correct (native) headers,
> because python setuptools / distutils looks into STAGING_{LIB,INC}DIR
> when compiling the native extension for libfdt. I didn't find any other
> way to specificy this in either the u-boot Makefile or some other magic
> environment variable.

CCing Yamada-san, maybe he has an idea.
Also, do not top post.

> // Martin
> 
> On 2018-04-09 02:54, Khem Raj wrote:
>>
>> On Sun, Apr 8, 2018 at 4:10 PM Marek Vasut <marex@denx.de
>> <mailto:marex@denx.de>> wrote:
>>
>>     This upgrades the U-Boot from 2018.01 to 2018.03 release and drops
>>     patches accepted upstream, getting the patch count to zero.
>>
>>
>>
>> It fails for me if I have libfdt installed on build host
>> It seems build is doing the include dance which goes all the way into
>> hosts system include directories
>>
>>
>>
>>     Signed-off-by: Marek Vasut <marex@denx.de <mailto:marex@denx.de>>
>>     Cc: Otavio Salvador <otavio@ossystems.com.br
>>     <mailto:otavio@ossystems.com.br>>
>>     Cc: Ross Burton <ross.burton@intel.com
>> <mailto:ross.burton@intel.com>>
>>     Cc: Richard Purdie <richard.purdie@linuxfoundation.org
>>     <mailto:richard.purdie@linuxfoundation.org>>
>>     ---
>>       .../u-boot/files/MPC8315ERDB-enable-DHCP.patch        | 19
>>     -------------------
>>       ...t-common_2018.01.inc => u-boot-common_2018.03.inc} |  6 ++----
>>       ...fw-utils_2018.01.bb <http://fw-utils_2018.01.bb> =>
>>     u-boot-fw-utils_2018.03.bb <http://u-boot-fw-utils_2018.03.bb>} |  0
>>       ...t-mkimage_2018.01.bb <http://t-mkimage_2018.01.bb> =>
>>     u-boot-mkimage_2018.03.bb <http://u-boot-mkimage_2018.03.bb>} |  0
>>       .../u-boot/{u-boot_2018.01.bb <http://u-boot_2018.01.bb> =>
>>     u-boot_2018.03.bb <http://u-boot_2018.03.bb>}   |  0
>>       5 files changed, 2 insertions(+), 23 deletions(-)
>>       delete mode 100644
>>     meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
>>       rename meta/recipes-bsp/u-boot/{u-boot-common_2018.01.inc =>
>>     u-boot-common_2018.03.inc} (68%)
>>       rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2018.01.bb
>>     <http://u-boot-fw-utils_2018.01.bb> => u-boot-fw-utils_2018.03.bb
>>     <http://u-boot-fw-utils_2018.03.bb>} (100%)
>>       rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2018.01.bb
>>     <http://u-boot-mkimage_2018.01.bb> => u-boot-mkimage_2018.03.bb
>>     <http://u-boot-mkimage_2018.03.bb>} (100%)
>>       rename meta/recipes-bsp/u-boot/{u-boot_2018.01.bb
>>     <http://u-boot_2018.01.bb> => u-boot_2018.03.bb
>>     <http://u-boot_2018.03.bb>} (100%)
>>
>>     diff --git
>>     a/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
>>     b/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
>>     deleted file mode 100644
>>     index ecaa1796a4..0000000000
>>     --- a/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
>>     +++ /dev/null
>>     @@ -1,19 +0,0 @@
>>     -Enabled dhcp client functionality for Yocto reference
>>     -hardware MPC8315E-RDB.
>>     -
>>     -Upstream-Status: Pending
>>     -
>>     -Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com
>>     <mailto:ed.bartosh@linux.intel.com>>
>>     -
>>     -Index: git/configs/MPC8315ERDB_defconfig
>>     -===================================================================
>>     ---- git.orig/configs/MPC8315ERDB_defconfig
>>     -+++ git/configs/MPC8315ERDB_defconfig
>>     -@@ -12,6 +12,7 @@ CONFIG_CMD_PCI=y
>>     - CONFIG_CMD_SATA=y
>>     - CONFIG_CMD_USB=y
>>     - # CONFIG_CMD_SETEXPR is not set
>>     -+CONFIG_CMD_DHCP=y
>>     - CONFIG_CMD_MII=y
>>     - CONFIG_CMD_PING=y
>>     - CONFIG_CMD_DATE=y
>>     diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2018.01.inc
>>     b/meta/recipes-bsp/u-boot/u-boot-common_2018.03.inc
>>     similarity index 68%
>>     rename from meta/recipes-bsp/u-boot/u-boot-common_2018.01.inc
>>     rename to meta/recipes-bsp/u-boot/u-boot-common_2018.03.inc
>>     index d2073ea0c7..8ffae365a9 100644
>>     --- a/meta/recipes-bsp/u-boot/u-boot-common_2018.01.inc
>>     +++ b/meta/recipes-bsp/u-boot/u-boot-common_2018.03.inc
>>     @@ -7,10 +7,8 @@ PE = "1"
>>
>>       # We use the revision in order to avoid having to fetch it from the
>>       # repo during parse
>>     -SRCREV = "f3dd87e0b98999a78e500e8c6d2b063ebadf535a"
>>     +SRCREV = "f95ab1fb6e37f0601f397091bb011edf7a98b890"
>>
>>     -SRC_URI = "git://git.denx.de/u-boot.git
>>     <http://git.denx.de/u-boot.git> \
>>     -    file://MPC8315ERDB-enable-DHCP.patch \
>>     -"
>>     +SRC_URI = "git://git.denx.de/u-boot.git
>>     <http://git.denx.de/u-boot.git>"
>>
>>       S = "${WORKDIR}/git"
>>     diff --git a/meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.01.bb
>>     <http://u-boot-fw-utils_2018.01.bb>
>>     b/meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.03.bb
>>     <http://u-boot-fw-utils_2018.03.bb>
>>     similarity index 100%
>>     rename from meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.01.bb
>>     <http://u-boot-fw-utils_2018.01.bb>
>>     rename to meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.03.bb
>>     <http://u-boot-fw-utils_2018.03.bb>
>>     diff --git a/meta/recipes-bsp/u-boot/u-boot-mkimage_2018.01.bb
>>     <http://u-boot-mkimage_2018.01.bb>
>>     b/meta/recipes-bsp/u-boot/u-boot-mkimage_2018.03.bb
>>     <http://u-boot-mkimage_2018.03.bb>
>>     similarity index 100%
>>     rename from meta/recipes-bsp/u-boot/u-boot-mkimage_2018.01.bb
>>     <http://u-boot-mkimage_2018.01.bb>
>>     rename to meta/recipes-bsp/u-boot/u-boot-mkimage_2018.03.bb
>>     <http://u-boot-mkimage_2018.03.bb>
>>     diff --git a/meta/recipes-bsp/u-boot/u-boot_2018.01.bb
>>     <http://u-boot_2018.01.bb>
>>     b/meta/recipes-bsp/u-boot/u-boot_2018.03.bb
>> <http://u-boot_2018.03.bb>
>>     similarity index 100%
>>     rename from meta/recipes-bsp/u-boot/u-boot_2018.01.bb
>>     <http://u-boot_2018.01.bb>
>>     rename to meta/recipes-bsp/u-boot/u-boot_2018.03.bb
>>     <http://u-boot_2018.03.bb>
>>     --
>>     2.16.2
>>
>>     --
>>     _______________________________________________
>>     Openembedded-core mailing list
>>     Openembedded-core@lists.openembedded.org
>>     <mailto:Openembedded-core@lists.openembedded.org>
>>     http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>
>>
>>


-- 
Best regards,
Marek Vasut

Re: [PATCH] u-boot: Upgrade to 2018.03 release

[Martin Hundebøll]

Hi,

On 2018-04-11 04:28, yamada.masahiro@socionext.com wrote:
> Hi.
> 
>>> I had to patch up our own u-boot recipe as shown in the attached patch
>>> to make v2018.03 compile for qemu-x86.
>>>
>>> The thing is that the build of pylibfdt became unconditional since
>>> 15b97f5c5e ('pylibfdt: move pylibfdt to scripts/dtc/pylibfdt and
>>> refactor makefile')
>>>
>>> In my case u-boot/pylibfdt failed to find the correct (native) headers,
>>> because python setuptools / distutils looks into STAGING_{LIB,INC}DIR
>>> when compiling the native extension for libfdt. I didn't find any other
>>> way to specificy this in either the u-boot Makefile or some other magic
>>> environment variable.
>>
>> CCing Yamada-san, maybe he has an idea.
>> Also, do not top post.
> 
> 
> 
> The build of pylibfdt is conditional.
> It is built only when CONFIG_PYLIBFDT=y,
> which is selected by CONFIG_DTOC.
> 
> If you really do not need pylibfdt,
> you can disable it by tweaking the configuration.
> 
> If you need pylibfdt but you cannot build it,
> it is a different problem.
> 
> Thanks.

Correct. But I was building u-boot.rom for qemu-x86, which depends on 
binman and thus pylibfdt. Before the mentioned commit, one could avoid 
the building of pylibfdt by installing it on the host, as the makerule 
checked if python could already import pylibfdt. This check is now removed.

Or am I missing something?

// Martin

> 
>> -----Original Message-----
>> From: Marek Vasut [mailto:marex@denx.de]
>> Sent: Tuesday, April 10, 2018 6:55 PM
>> To: Martin Hundebøll <mnhu@prevas.dk>; Khem Raj <raj.khem@gmail.com>
>> Cc: Otavio Salvador <otavio@ossystems.com.br>;
>> openembedded-core@lists.openembedded.org; Yamada, Masahiro/山田 真弘
>> <yamada.masahiro@socionext.com>
>> Subject: Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release
>>
>> On 04/10/2018 11:49 AM, Martin Hundebøll wrote:
>>> Hi,
>>
>> Hi,
>>
>>> I had to patch up our own u-boot recipe as shown in the attached patch
>>> to make v2018.03 compile for qemu-x86.
>>>
>>> The thing is that the build of pylibfdt became unconditional since
>>> 15b97f5c5e ('pylibfdt: move pylibfdt to scripts/dtc/pylibfdt and
>>> refactor makefile')
>>>
>>> In my case u-boot/pylibfdt failed to find the correct (native) headers,
>>> because python setuptools / distutils looks into STAGING_{LIB,INC}DIR
>>> when compiling the native extension for libfdt. I didn't find any other
>>> way to specificy this in either the u-boot Makefile or some other magic
>>> environment variable.
>>
>> CCing Yamada-san, maybe he has an idea.
>> Also, do not top post.
>>
>>> // Martin
>>>
>>> On 2018-04-09 02:54, Khem Raj wrote:
>>>>
>>>> On Sun, Apr 8, 2018 at 4:10 PM Marek Vasut <marex@denx.de
>>>> <mailto:marex@denx.de>> wrote:
>>>>
>>>>      This upgrades the U-Boot from 2018.01 to 2018.03 release and drops
>>>>      patches accepted upstream, getting the patch count to zero.
>>>>
>>>>
>>>>
>>>> It fails for me if I have libfdt installed on build host
>>>> It seems build is doing the include dance which goes all the way into
>>>> hosts system include directories
>>>>
>>>>
>>>>
>>>>      Signed-off-by: Marek Vasut <marex@denx.de <mailto:marex@denx.de>>
>>>>      Cc: Otavio Salvador <otavio@ossystems.com.br
>>>>      <mailto:otavio@ossystems.com.br>>
>>>>      Cc: Ross Burton <ross.burton@intel.com
>>>> <mailto:ross.burton@intel.com>>
>>>>      Cc: Richard Purdie <richard.purdie@linuxfoundation.org
>>>>      <mailto:richard.purdie@linuxfoundation.org>>
>>>>      ---
>>>>        .../u-boot/files/MPC8315ERDB-enable-DHCP.patch        | 19
>>>>      -------------------
>>>>        ...t-common_2018.01.inc => u-boot-common_2018.03.inc} |  6
>> ++----
>>>>        ...fw-utils_2018.01.bb <http://fw-utils_2018.01.bb> =>
>>>>      u-boot-fw-utils_2018.03.bb <http://u-boot-fw-utils_2018.03.bb>}
>> |  0
>>>>        ...t-mkimage_2018.01.bb <http://t-mkimage_2018.01.bb> =>
>>>>      u-boot-mkimage_2018.03.bb <http://u-boot-mkimage_2018.03.bb>}
>> |  0
>>>>        .../u-boot/{u-boot_2018.01.bb <http://u-boot_2018.01.bb> =>
>>>>      u-boot_2018.03.bb <http://u-boot_2018.03.bb>}   |  0
>>>>        5 files changed, 2 insertions(+), 23 deletions(-)
>>>>        delete mode 100644
>>>>      meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
>>>>        rename meta/recipes-bsp/u-boot/{u-boot-common_2018.01.inc =>
>>>>      u-boot-common_2018.03.inc} (68%)
>>>>        rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2018.01.bb
>>>>      <http://u-boot-fw-utils_2018.01.bb> =>
>> u-boot-fw-utils_2018.03.bb
>>>>      <http://u-boot-fw-utils_2018.03.bb>} (100%)
>>>>        rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2018.01.bb
>>>>      <http://u-boot-mkimage_2018.01.bb> => u-boot-mkimage_2018.03.bb
>>>>      <http://u-boot-mkimage_2018.03.bb>} (100%)
>>>>        rename meta/recipes-bsp/u-boot/{u-boot_2018.01.bb
>>>>      <http://u-boot_2018.01.bb> => u-boot_2018.03.bb
>>>>      <http://u-boot_2018.03.bb>} (100%)
>>>>
>>>>      diff --git
>>>>      a/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
>>>>      b/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
>>>>      deleted file mode 100644
>>>>      index ecaa1796a4..0000000000
>>>>      ---
>> a/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
>>>>      +++ /dev/null
>>>>      @@ -1,19 +0,0 @@
>>>>      -Enabled dhcp client functionality for Yocto reference
>>>>      -hardware MPC8315E-RDB.
>>>>      -
>>>>      -Upstream-Status: Pending
>>>>      -
>>>>      -Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com
>>>>      <mailto:ed.bartosh@linux.intel.com>>
>>>>      -
>>>>      -Index: git/configs/MPC8315ERDB_defconfig
>>>>      -==============================================================
>> =====
>>>>      ---- git.orig/configs/MPC8315ERDB_defconfig
>>>>      -+++ git/configs/MPC8315ERDB_defconfig
>>>>      -@@ -12,6 +12,7 @@ CONFIG_CMD_PCI=y
>>>>      - CONFIG_CMD_SATA=y
>>>>      - CONFIG_CMD_USB=y
>>>>      - # CONFIG_CMD_SETEXPR is not set
>>>>      -+CONFIG_CMD_DHCP=y
>>>>      - CONFIG_CMD_MII=y
>>>>      - CONFIG_CMD_PING=y
>>>>      - CONFIG_CMD_DATE=y
>>>>      diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2018.01.inc
>>>>      b/meta/recipes-bsp/u-boot/u-boot-common_2018.03.inc
>>>>      similarity index 68%
>>>>      rename from meta/recipes-bsp/u-boot/u-boot-common_2018.01.inc
>>>>      rename to meta/recipes-bsp/u-boot/u-boot-common_2018.03.inc
>>>>      index d2073ea0c7..8ffae365a9 100644
>>>>      --- a/meta/recipes-bsp/u-boot/u-boot-common_2018.01.inc
>>>>      +++ b/meta/recipes-bsp/u-boot/u-boot-common_2018.03.inc
>>>>      @@ -7,10 +7,8 @@ PE = "1"
>>>>
>>>>        # We use the revision in order to avoid having to fetch it from
>> the
>>>>        # repo during parse
>>>>      -SRCREV = "f3dd87e0b98999a78e500e8c6d2b063ebadf535a"
>>>>      +SRCREV = "f95ab1fb6e37f0601f397091bb011edf7a98b890"
>>>>
>>>>      -SRC_URI = "git://git.denx.de/u-boot.git
>>>>      <http://git.denx.de/u-boot.git> \
>>>>      -    file://MPC8315ERDB-enable-DHCP.patch \
>>>>      -"
>>>>      +SRC_URI = "git://git.denx.de/u-boot.git
>>>>      <http://git.denx.de/u-boot.git>"
>>>>
>>>>        S = "${WORKDIR}/git"
>>>>      diff --git a/meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.01.bb
>>>>      <http://u-boot-fw-utils_2018.01.bb>
>>>>      b/meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.03.bb
>>>>      <http://u-boot-fw-utils_2018.03.bb>
>>>>      similarity index 100%
>>>>      rename from meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.01.bb
>>>>      <http://u-boot-fw-utils_2018.01.bb>
>>>>      rename to meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.03.bb
>>>>      <http://u-boot-fw-utils_2018.03.bb>
>>>>      diff --git a/meta/recipes-bsp/u-boot/u-boot-mkimage_2018.01.bb
>>>>      <http://u-boot-mkimage_2018.01.bb>
>>>>      b/meta/recipes-bsp/u-boot/u-boot-mkimage_2018.03.bb
>>>>      <http://u-boot-mkimage_2018.03.bb>
>>>>      similarity index 100%
>>>>      rename from meta/recipes-bsp/u-boot/u-boot-mkimage_2018.01.bb
>>>>      <http://u-boot-mkimage_2018.01.bb>
>>>>      rename to meta/recipes-bsp/u-boot/u-boot-mkimage_2018.03.bb
>>>>      <http://u-boot-mkimage_2018.03.bb>
>>>>      diff --git a/meta/recipes-bsp/u-boot/u-boot_2018.01.bb
>>>>      <http://u-boot_2018.01.bb>
>>>>      b/meta/recipes-bsp/u-boot/u-boot_2018.03.bb
>>>> <http://u-boot_2018.03.bb>
>>>>      similarity index 100%
>>>>      rename from meta/recipes-bsp/u-boot/u-boot_2018.01.bb
>>>>      <http://u-boot_2018.01.bb>
>>>>      rename to meta/recipes-bsp/u-boot/u-boot_2018.03.bb
>>>>      <http://u-boot_2018.03.bb>
>>>>      --
>>>>      2.16.2
>>>>
>>>>      --
>>>>      _______________________________________________
>>>>      Openembedded-core mailing list
>>>>      Openembedded-core@lists.openembedded.org
>>>>      <mailto:Openembedded-core@lists.openembedded.org>
>>>>      http://lists.openembedded.org/mailman/listinfo/openembedded-cor
>> e
>>>>
>>>>
>>>>
>>
>>
>> --
>> Best regards,
>> Marek Vasut

Re: [PATCH] u-boot: Upgrade to 2018.03 release

[Burton, Ross]

On 9 April 2018 at 00:02, Marek Vasut <marex@denx.de> wrote:
> This upgrades the U-Boot from 2018.01 to 2018.03 release and drops
> patches accepted upstream, getting the patch count to zero.

Are you proposing this for 2.5/Sumo (breaking the freeze) or is it
fine to sit in master-next until 2.5 is released?

Ross

Re: [PATCH] u-boot: Upgrade to 2018.03 release

[Marek Vasut]

On 04/11/2018 04:47 PM, Burton, Ross wrote:
> On 9 April 2018 at 00:02, Marek Vasut <marex@denx.de> wrote:
>> This upgrades the U-Boot from 2018.01 to 2018.03 release and drops
>> patches accepted upstream, getting the patch count to zero.
> 
> Are you proposing this for 2.5/Sumo (breaking the freeze) or is it
> fine to sit in master-next until 2.5 is released?

master-next, for 2.6 .

-- 
Best regards,
Marek Vasut

Re: [PATCH] u-boot: Upgrade to 2018.03 release

[Marek Vasut]

On 04/16/2018 10:38 AM, yamada.masahiro@socionext.com wrote:
> Hi.
> 
>> -----Original Message-----
>> From: Martin Hundebøll [mailto:mnhu@prevas.dk]
>> Sent: Wednesday, April 11, 2018 5:42 PM
>> To: Yamada, Masahiro/山田 真弘 <yamada.masahiro@socionext.com>;
>> marex@denx.de; raj.khem@gmail.com
>> Cc: otavio@ossystems.com.br; openembedded-core@lists.openembedded.org
>> Subject: Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release
>>
>> Hi,
>>
>> On 2018-04-11 04:28, yamada.masahiro@socionext.com wrote:
>>> Hi.
>>>
>>>>> I had to patch up our own u-boot recipe as shown in the attached patch
>>>>> to make v2018.03 compile for qemu-x86.
>>>>>
>>>>> The thing is that the build of pylibfdt became unconditional since
>>>>> 15b97f5c5e ('pylibfdt: move pylibfdt to scripts/dtc/pylibfdt and
>>>>> refactor makefile')
>>>>>
>>>>> In my case u-boot/pylibfdt failed to find the correct (native) headers,
>>>>> because python setuptools / distutils looks into STAGING_{LIB,INC}DIR
>>>>> when compiling the native extension for libfdt. I didn't find any other
>>>>> way to specificy this in either the u-boot Makefile or some other magic
>>>>> environment variable.
>>>>
>>>> CCing Yamada-san, maybe he has an idea.
>>>> Also, do not top post.
>>>
>>>
>>>
>>> The build of pylibfdt is conditional.
>>> It is built only when CONFIG_PYLIBFDT=y,
>>> which is selected by CONFIG_DTOC.
>>>
>>> If you really do not need pylibfdt,
>>> you can disable it by tweaking the configuration.
>>>
>>> If you need pylibfdt but you cannot build it,
>>> it is a different problem.
>>>
>>> Thanks.
>>
>> Correct. But I was building u-boot.rom for qemu-x86, which depends on
>> binman and thus pylibfdt. Before the mentioned commit, one could avoid
>> the building of pylibfdt by installing it on the host, as the makerule
>> checked if python could already import pylibfdt. This check is now removed.
>>
>> Or am I missing something?
> 
> 
> Understood what you mean, but I do not know
> whether the previous behavior was intended, or just something
> people discovered to work.
> 
> 
> Now U-Boot bundles its own DTC (scripts/dtc/dtc),
> so compiling also pylibfdt from the source in U-boot tree makes sense.
> 
> Isn't it possible to solve your issue in the OE side?
> 

Can we NOT compile DTC alongside U-Boot somehow ? :)
That'd be the most desired solution IMO.

-- 
Best regards,
Marek Vasut

Re: [PATCH] u-boot: Upgrade to 2018.03 release

[Robert Berger]

Hi,

Please see my comments below.

On 2018-04-11 16:51, Marek Vasut wrote:
> On 04/11/2018 04:47 PM, Burton, Ross wrote:
>> On 9 April 2018 at 00:02, Marek Vasut <marex@denx.de> wrote:
>>> This upgrades the U-Boot from 2018.01 to 2018.03 release and drops
>>> patches accepted upstream, getting the patch count to zero.
>> Are you proposing this for 2.5/Sumo (breaking the freeze) or is it
>> fine to sit in master-next until 2.5 is released?
> master-next, for 2.6 .
>
I think we have also problem with u-boot and rocko 2.4.x

I observed with 2.4.x for i.mx6 and sitara that u-boot 2017.01 does not 
function anymore properly (networking is broken due to compiler upgrade 
with 2.4.x [1]).

So I built u-boot 2017.03 (a pre-release version) with 2.4.1 and 2.4.2 
and it was fixed.

Please note, that I did not do this via bitbake, but using the SDK.

So I think it would be a good idea to get u-boot 2017.03 to build with a 
recent version of rocko as well.

[1] https://www.mail-archive.com/yocto@yoctoproject.org/msg39605.html

Regards,

Robert

Re: [PATCH] u-boot: Upgrade to 2018.03 release

[Robert Berger]

Hi,

Update:

This rocko 2.4/u-boot combination still seems to work[1]:

Note that this is before rocko 2.4.1 and before U-Boot 2018.01.

=> version
U-Boot 2017.09 (Nov 04 2017 - 20:32:29 +0000)

arm-poky-linux-gnueabi-gcc (GCC) 7.2.0
GNU ld (GNU Binutils) 2.29.0.20170912

[1] 
https://github.com/RobertBerger/meta-mainline/blob/rocko-training-v4.9.x/u-boot-wic-bsp/yocto-autobuilder/res-custom-rocko-multi-v7-core-image-minimal-uboot-vic.conf

Regards,

Robert

Re: [PATCH] u-boot: Upgrade to 2018.03 release

[Alexander Kanavin]

On 04/16/2018 11:40 AM, Marek Vasut wrote:
>> Isn't it possible to solve your issue in the OE side?
>>
> 
> Can we NOT compile DTC alongside U-Boot somehow ? :)
> That'd be the most desired solution IMO.

Yes please. Can you adjust the recipes and classes in oe-core, and 
remove the dtc recipe altogether?

Alex

Re: [PATCH] u-boot: Upgrade to 2018.03 release

[Marek Vasut]

On 04/30/2018 02:17 PM, Alexander Kanavin wrote:
> On 04/16/2018 11:40 AM, Marek Vasut wrote:
>>> Isn't it possible to solve your issue in the OE side?
>>>
>>
>> Can we NOT compile DTC alongside U-Boot somehow ? :)
>> That'd be the most desired solution IMO.
> 
> Yes please. Can you adjust the recipes and classes in oe-core, and
> remove the dtc recipe altogether?

Remove dtc recipe ? Not sure I understand what you're implying.

-- 
Best regards,
Marek Vasut

Re: [PATCH] u-boot: Upgrade to 2018.03 release

[Martin Hundebøll]

On April 30, 2018 7:25:10 PM GMT+02:00, Marek Vasut <marex@denx.de> wrote:
>On 04/30/2018 02:17 PM, Alexander Kanavin wrote:
>> On 04/16/2018 11:40 AM, Marek Vasut wrote:
>>>> Isn't it possible to solve your issue in the OE side?
>>>>
>>>
>>> Can we NOT compile DTC alongside U-Boot somehow ? :)
>>> That'd be the most desired solution IMO.
>> 
>> Yes please. Can you adjust the recipes and classes in oe-core, and
>> remove the dtc recipe altogether?
>
>Remove dtc recipe ? Not sure I understand what you're implying.

I guess Alexander misunderstood the "alongside U-Boot" part of your suggestion.

I agree that building dtc/libfdt in the U-Boot build instead of just using whatever is already available on the host/OE is undesirable.

But please elaborate if I am mistaken.

// Martin

Re: [PATCH] u-boot: Upgrade to 2018.03 release

[Alexander Kanavin]

On 04/30/2018 08:25 PM, Marek Vasut wrote:
>>>> Isn't it possible to solve your issue in the OE side?
>>>>
>>>
>>> Can we NOT compile DTC alongside U-Boot somehow ? :)
>>> That'd be the most desired solution IMO.
>>
>> Yes please. Can you adjust the recipes and classes in oe-core, and
>> remove the dtc recipe altogether?
> 
> Remove dtc recipe ? Not sure I understand what you're implying.

If u-boot bundles dtc in its source tree, can we use that, and remove 
the external dtc recipe?

Alex

Re: [PATCH] u-boot: Upgrade to 2018.03 release

[Otavio Salvador]

On Mon, Apr 30, 2018 at 4:53 PM Alexander Kanavin <
alexander.kanavin@linux.intel.com> wrote:

> On 04/30/2018 08:25 PM, Marek Vasut wrote:
> >>>> Isn't it possible to solve your issue in the OE side?
> >>>>
> >>>
> >>> Can we NOT compile DTC alongside U-Boot somehow ? :)
> >>> That'd be the most desired solution IMO.
> >>
> >> Yes please. Can you adjust the recipes and classes in oe-core, and
> >> remove the dtc recipe altogether?
> >
> > Remove dtc recipe ? Not sure I understand what you're implying.

> If u-boot bundles dtc in its source tree, can we use that, and remove
> the external dtc recipe?

We shouldn't. The point in use the recipes inside OE-Core is because our
bugfixes, patches and etc are used everywhere. If we use the bundled copy
how we'd fix a host issue for example? Duplicate patches?

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: [PATCH] u-boot: Upgrade to 2018.03 release

[Tom Rini]

[-- Attachment #1: Type: text/plain, Size: 994 bytes --]

On Mon, Apr 30, 2018 at 07:57:18PM +0000, Otavio Salvador wrote:
> On Mon, Apr 30, 2018 at 4:53 PM Alexander Kanavin <
> alexander.kanavin@linux.intel.com> wrote:
> 
> > On 04/30/2018 08:25 PM, Marek Vasut wrote:
> > >>>> Isn't it possible to solve your issue in the OE side?
> > >>>>
> > >>>
> > >>> Can we NOT compile DTC alongside U-Boot somehow ? :)
> > >>> That'd be the most desired solution IMO.
> > >>
> > >> Yes please. Can you adjust the recipes and classes in oe-core, and
> > >> remove the dtc recipe altogether?
> > >
> > > Remove dtc recipe ? Not sure I understand what you're implying.
> 
> > If u-boot bundles dtc in its source tree, can we use that, and remove
> > the external dtc recipe?
> 
> We shouldn't. The point in use the recipes inside OE-Core is because our
> bugfixes, patches and etc are used everywhere. If we use the bundled copy
> how we'd fix a host issue for example? Duplicate patches?

What do you do for the kernel here?

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: [PATCH] u-boot: Upgrade to 2018.03 release

[Otavio Salvador]

On Mon, Apr 30, 2018 at 5:25 PM Tom Rini <trini@konsulko.com> wrote:

> On Mon, Apr 30, 2018 at 07:57:18PM +0000, Otavio Salvador wrote:
> > On Mon, Apr 30, 2018 at 4:53 PM Alexander Kanavin <
> > alexander.kanavin@linux.intel.com> wrote:
> >
> > > On 04/30/2018 08:25 PM, Marek Vasut wrote:
> > > >>>> Isn't it possible to solve your issue in the OE side?
> > > >>>>
> > > >>>
> > > >>> Can we NOT compile DTC alongside U-Boot somehow ? :)
> > > >>> That'd be the most desired solution IMO.
> > > >>
> > > >> Yes please. Can you adjust the recipes and classes in oe-core, and
> > > >> remove the dtc recipe altogether?
> > > >
> > > > Remove dtc recipe ? Not sure I understand what you're implying.
> >
> > > If u-boot bundles dtc in its source tree, can we use that, and remove
> > > the external dtc recipe?
> >
> > We shouldn't. The point in use the recipes inside OE-Core is because our
> > bugfixes, patches and etc are used everywhere. If we use the bundled
copy
> > how we'd fix a host issue for example? Duplicate patches?

> What do you do for the kernel here?

We use our dtc-native. As we do for all other recipes (but few exceptions)


-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: [PATCH] u-boot: Upgrade to 2018.03 release

[Marek Vasut]

On 04/30/2018 10:29 PM, Otavio Salvador wrote:
> On Mon, Apr 30, 2018 at 5:25 PM Tom Rini <trini@konsulko.com> wrote:
> 
>> On Mon, Apr 30, 2018 at 07:57:18PM +0000, Otavio Salvador wrote:
>>> On Mon, Apr 30, 2018 at 4:53 PM Alexander Kanavin <
>>> alexander.kanavin@linux.intel.com> wrote:
>>>
>>>> On 04/30/2018 08:25 PM, Marek Vasut wrote:
>>>>>>>> Isn't it possible to solve your issue in the OE side?
>>>>>>>>
>>>>>>>
>>>>>>> Can we NOT compile DTC alongside U-Boot somehow ? :)
>>>>>>> That'd be the most desired solution IMO.
>>>>>>
>>>>>> Yes please. Can you adjust the recipes and classes in oe-core, and
>>>>>> remove the dtc recipe altogether?
>>>>>
>>>>> Remove dtc recipe ? Not sure I understand what you're implying.
>>>
>>>> If u-boot bundles dtc in its source tree, can we use that, and remove
>>>> the external dtc recipe?
>>>
>>> We shouldn't. The point in use the recipes inside OE-Core is because our
>>> bugfixes, patches and etc are used everywhere. If we use the bundled
> copy
>>> how we'd fix a host issue for example? Duplicate patches?
> 
>> What do you do for the kernel here?
> 
> We use our dtc-native. As we do for all other recipes (but few exceptions)

Yeah, we should use the DTC from OE , not the DTC from U-Boot.

-- 
Best regards,
Marek Vasut

Re: [PATCH] u-boot: Upgrade to 2018.03 release

[Tom Rini]

[-- Attachment #1: Type: text/plain, Size: 1433 bytes --]

On Mon, Apr 30, 2018 at 08:29:56PM +0000, Otavio Salvador wrote:
> On Mon, Apr 30, 2018 at 5:25 PM Tom Rini <trini@konsulko.com> wrote:
> 
> > On Mon, Apr 30, 2018 at 07:57:18PM +0000, Otavio Salvador wrote:
> > > On Mon, Apr 30, 2018 at 4:53 PM Alexander Kanavin <
> > > alexander.kanavin@linux.intel.com> wrote:
> > >
> > > > On 04/30/2018 08:25 PM, Marek Vasut wrote:
> > > > >>>> Isn't it possible to solve your issue in the OE side?
> > > > >>>>
> > > > >>>
> > > > >>> Can we NOT compile DTC alongside U-Boot somehow ? :)
> > > > >>> That'd be the most desired solution IMO.
> > > > >>
> > > > >> Yes please. Can you adjust the recipes and classes in oe-core, and
> > > > >> remove the dtc recipe altogether?
> > > > >
> > > > > Remove dtc recipe ? Not sure I understand what you're implying.
> > >
> > > > If u-boot bundles dtc in its source tree, can we use that, and remove
> > > > the external dtc recipe?
> > >
> > > We shouldn't. The point in use the recipes inside OE-Core is because our
> > > bugfixes, patches and etc are used everywhere. If we use the bundled
> copy
> > > how we'd fix a host issue for example? Duplicate patches?
> 
> > What do you do for the kernel here?
> 
> We use our dtc-native. As we do for all other recipes (but few exceptions)

Then you should also be doing swig-native, if I recall the other parts
of this thread (or the other one?) correctly.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: [PATCH] u-boot: Upgrade to 2018.03 release

[Otavio Salvador]

On Mon, Apr 30, 2018 at 9:25 PM Tom Rini <trini@konsulko.com> wrote:

> On Mon, Apr 30, 2018 at 08:29:56PM +0000, Otavio Salvador wrote:
> > On Mon, Apr 30, 2018 at 5:25 PM Tom Rini <trini@konsulko.com> wrote:
> > We use our dtc-native. As we do for all other recipes (but few
exceptions)

> Then you should also be doing swig-native, if I recall the other parts
> of this thread (or the other one?) correctly.

Yes, we should ...

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750