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:
> >> ...
> >>
> >> > Taking a look at u-boot.
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
>> > all that could work at all
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 or
> > just poor
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 in a clean way?
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 Wednesday, January 13, 2016 at 04:39:53 P
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, Jan 13, 2016 at 12:34 PM, Marek Vasut
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, Jan 13, 2016 at 12:34 PM, Marek Vasut wrote:
> >> > On Wednesday, January 13, 2016 at 01:04
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 Wed, Jan 13, 2016 at 3:09 PM, Mare
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 Wednesday, January 13, 2016 at 0
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 Wednesday, January 13, 2016 at 05:40:20 PM, Otavio Salvador wrote:
>> >> On Wed, Jan 13, 2016 at 2:30 PM, Mare
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 Wednesday, January 13, 2016 at 0
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 Wed, Jan 13, 2016 at 1:53 PM, Mare
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 Wednesday, January 13, 2016 at 0
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 Wed, Jan 13, 2016 at 12:34 PM, Mar
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 Wednesday, January 13, 2016 at
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:
> >> > Upgrade U-Boot to latest version a
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 Wed, Jan 13, 2016 at 1:36 AM, Mar
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 configuration of U-Boot during bu
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 "make foomachine"
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 foomachine_defconfig ; make". F
> 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 configuration of U-Boot during build. It
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 foomachine" in U-Bo
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 foomachine_defconfig ; make". F
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 .
Signed-off-by
24 matches
Mail list logo