Re: [OE-core] [PATCH] u-boot: Update to 2016.01 release

2016-01-14 Thread Marek Vasut
On Friday, January 15, 2016 at 12:42:18 AM, Otavio Salvador wrote: > On Thu, Jan 14, 2016 at 7:41 PM, Marek Vasut wrote: > > On Thursday, January 14, 2016 at 10:37:16 PM, Otavio Salvador wrote: > >> On Thu, Jan 14, 2016 at 7:15 PM, Marek Vasut wrote: > >> ... > >>

Re: [OE-core] [PATCH] u-boot: Update to 2016.01 release

2016-01-14 Thread Otavio Salvador
On Thu, Jan 14, 2016 at 7:41 PM, Marek Vasut wrote: > On Thursday, January 14, 2016 at 10:37:16 PM, Otavio Salvador wrote: >> On Thu, Jan 14, 2016 at 7:15 PM, Marek Vasut wrote: >> ... >> >> > Taking a look at u-boot.inc and uboot-config.bbclass makes me wonder how

Re: [OE-core] [PATCH] u-boot: Update to 2016.01 release

2016-01-14 Thread Marek Vasut
On Thursday, January 14, 2016 at 09:43:24 PM, Otavio Salvador wrote: > On Wed, Jan 13, 2016 at 8:09 PM, Tom Rini wrote: > > On Wed, Jan 13, 2016 at 01:55:56PM -0200, Otavio Salvador wrote: > >> On Wed, Jan 13, 2016 at 1:53 PM, Marek Vasut wrote: > >> > On

Re: [OE-core] [PATCH] u-boot: Update to 2016.01 release

2016-01-14 Thread Otavio Salvador
On Thu, Jan 14, 2016 at 7:15 PM, Marek Vasut wrote: ... > Taking a look at u-boot.inc and uboot-config.bbclass makes me wonder how all > that could work at all. It's either a stackpile of legacy cruft or just poor > design. I think it is a mix of both. How would you address this

Re: [OE-core] [PATCH] u-boot: Update to 2016.01 release

2016-01-14 Thread Otavio Salvador
On Wed, Jan 13, 2016 at 8:09 PM, Tom Rini wrote: > On Wed, Jan 13, 2016 at 01:55:56PM -0200, Otavio Salvador wrote: >> On Wed, Jan 13, 2016 at 1:53 PM, Marek Vasut wrote: >> > On Wednesday, January 13, 2016 at 04:39:53 PM, Otavio Salvador wrote: >> >> On Wed,

Re: [OE-core] [PATCH] u-boot: Update to 2016.01 release

2016-01-14 Thread Marek Vasut
On Thursday, January 14, 2016 at 10:37:16 PM, Otavio Salvador wrote: > On Thu, Jan 14, 2016 at 7:15 PM, Marek Vasut wrote: > ... > > > Taking a look at u-boot.inc and uboot-config.bbclass makes me wonder how > > all that could work at all. It's either a stackpile of legacy cruft

Re: [OE-core] [PATCH] u-boot: Update to 2016.01 release

2016-01-13 Thread Otavio Salvador
On Wed, Jan 13, 2016 at 1:36 AM, Marek Vasut wrote: > Upgrade U-Boot to latest version and drop upstreamed patches. > > Repair configuration of U-Boot during build. It is no longer > possible to run "make foomachine" in U-Boot. Instead, it is > necessary to do "make

Re: [OE-core] [PATCH] u-boot: Update to 2016.01 release

2016-01-13 Thread Marek Vasut
On Wednesday, January 13, 2016 at 06:56:36 PM, Otavio Salvador wrote: > On Wed, Jan 13, 2016 at 3:42 PM, Marek Vasut wrote: > > On Wednesday, January 13, 2016 at 06:16:01 PM, Otavio Salvador wrote: > >> On Wed, Jan 13, 2016 at 3:09 PM, Marek Vasut wrote: > >> > On

Re: [OE-core] [PATCH] u-boot: Update to 2016.01 release

2016-01-13 Thread Otavio Salvador
On Wed, Jan 13, 2016 at 6:35 PM, Marek Vasut wrote: > On Wednesday, January 13, 2016 at 06:56:36 PM, Otavio Salvador wrote: >> On Wed, Jan 13, 2016 at 3:42 PM, Marek Vasut wrote: >> > On Wednesday, January 13, 2016 at 06:16:01 PM, Otavio Salvador wrote: >> >> On

Re: [OE-core] [PATCH] u-boot: Update to 2016.01 release

2016-01-13 Thread Otavio Salvador
On Wed, Jan 13, 2016 at 12:34 PM, Marek Vasut wrote: > On Wednesday, January 13, 2016 at 01:04:31 PM, Otavio Salvador wrote: >> On Wed, Jan 13, 2016 at 1:36 AM, Marek Vasut wrote: >> > Upgrade U-Boot to latest version and drop upstreamed patches. >> > >> > Repair

Re: [OE-core] [PATCH] u-boot: Update to 2016.01 release

2016-01-13 Thread Otavio Salvador
On Wed, Jan 13, 2016 at 1:53 PM, Marek Vasut wrote: > On Wednesday, January 13, 2016 at 04:39:53 PM, Otavio Salvador wrote: >> On Wed, Jan 13, 2016 at 12:34 PM, Marek Vasut wrote: >> > On Wednesday, January 13, 2016 at 01:04:31 PM, Otavio Salvador wrote: >> >> On

Re: [OE-core] [PATCH] u-boot: Update to 2016.01 release

2016-01-13 Thread Marek Vasut
On Wednesday, January 13, 2016 at 04:39:53 PM, Otavio Salvador wrote: > On Wed, Jan 13, 2016 at 12:34 PM, Marek Vasut wrote: > > On Wednesday, January 13, 2016 at 01:04:31 PM, Otavio Salvador wrote: > >> On Wed, Jan 13, 2016 at 1:36 AM, Marek Vasut wrote: > >> >

Re: [OE-core] [PATCH] u-boot: Update to 2016.01 release

2016-01-13 Thread Marek Vasut
On Wednesday, January 13, 2016 at 01:04:31 PM, Otavio Salvador wrote: > On Wed, Jan 13, 2016 at 1:36 AM, Marek Vasut wrote: > > Upgrade U-Boot to latest version and drop upstreamed patches. > > > > Repair configuration of U-Boot during build. It is no longer > > possible to run

Re: [OE-core] [PATCH] u-boot: Update to 2016.01 release

2016-01-13 Thread Otavio Salvador
On Wed, Jan 13, 2016 at 2:30 PM, Marek Vasut wrote: > On Wednesday, January 13, 2016 at 04:55:56 PM, Otavio Salvador wrote: >> On Wed, Jan 13, 2016 at 1:53 PM, Marek Vasut wrote: >> > On Wednesday, January 13, 2016 at 04:39:53 PM, Otavio Salvador wrote: >> >> On

Re: [OE-core] [PATCH] u-boot: Update to 2016.01 release

2016-01-13 Thread Marek Vasut
On Wednesday, January 13, 2016 at 04:55:56 PM, Otavio Salvador wrote: > On Wed, Jan 13, 2016 at 1:53 PM, Marek Vasut wrote: > > On Wednesday, January 13, 2016 at 04:39:53 PM, Otavio Salvador wrote: > >> On Wed, Jan 13, 2016 at 12:34 PM, Marek Vasut wrote: > >> > On

Re: [OE-core] [PATCH] u-boot: Update to 2016.01 release

2016-01-13 Thread Marek Vasut
On Wednesday, January 13, 2016 at 05:40:20 PM, Otavio Salvador wrote: > On Wed, Jan 13, 2016 at 2:30 PM, Marek Vasut wrote: > > On Wednesday, January 13, 2016 at 04:55:56 PM, Otavio Salvador wrote: > >> On Wed, Jan 13, 2016 at 1:53 PM, Marek Vasut wrote: > >> > On

Re: [OE-core] [PATCH] u-boot: Update to 2016.01 release

2016-01-13 Thread Otavio Salvador
On Wed, Jan 13, 2016 at 3:09 PM, Marek Vasut wrote: > On Wednesday, January 13, 2016 at 05:40:20 PM, Otavio Salvador wrote: >> On Wed, Jan 13, 2016 at 2:30 PM, Marek Vasut wrote: >> > On Wednesday, January 13, 2016 at 04:55:56 PM, Otavio Salvador wrote: >> >> On

Re: [OE-core] [PATCH] u-boot: Update to 2016.01 release

2016-01-13 Thread Marek Vasut
On Wednesday, January 13, 2016 at 06:16:01 PM, Otavio Salvador wrote: > On Wed, Jan 13, 2016 at 3:09 PM, Marek Vasut wrote: > > On Wednesday, January 13, 2016 at 05:40:20 PM, Otavio Salvador wrote: > >> On Wed, Jan 13, 2016 at 2:30 PM, Marek Vasut wrote: > >> > On

Re: [OE-core] [PATCH] u-boot: Update to 2016.01 release

2016-01-12 Thread Khem Raj
> On Jan 12, 2016, at 9:01 PM, Marek Vasut wrote: > > On Wednesday, January 13, 2016 at 05:49:08 AM, Khem Raj wrote: >> On Tue, Jan 12, 2016 at 7:36 PM, Marek Vasut wrote: >>> Upgrade U-Boot to latest version and drop upstreamed patches. >>> >>> Repair

Re: [OE-core] [PATCH] u-boot: Update to 2016.01 release

2016-01-12 Thread Marek Vasut
On Wednesday, January 13, 2016 at 05:49:08 AM, Khem Raj wrote: > On Tue, Jan 12, 2016 at 7:36 PM, Marek Vasut wrote: > > Upgrade U-Boot to latest version and drop upstreamed patches. > > > > Repair configuration of U-Boot during build. It is no longer > > possible to run "make

Re: [OE-core] [PATCH] u-boot: Update to 2016.01 release

2016-01-12 Thread Khem Raj
On Tue, Jan 12, 2016 at 7:36 PM, Marek Vasut wrote: > Upgrade U-Boot to latest version and drop upstreamed patches. > > Repair configuration of U-Boot during build. It is no longer > possible to run "make foomachine" in U-Boot. Instead, it is > necessary to do "make

[OE-core] [PATCH] u-boot: Update to 2016.01 release

2016-01-12 Thread Marek Vasut
Upgrade U-Boot to latest version and drop upstreamed patches. Repair configuration of U-Boot during build. It is no longer possible to run "make foomachine" in U-Boot. Instead, it is necessary to do "make foomachine_defconfig ; make". Fix this in u-boot.inc and u-boot-fw-utils*.bb .