Am Fr., 2. Nov. 2018, 01:08 hat Marek Vasut geschrieben:
> On 11/01/2018 08:26 PM, Simon Goldschmidt wrote:
> > On 31.10.2018 11:00, Marek Vasut wrote:
> >> On 10/31/2018 06:44 AM, Simon Goldschmidt wrote:
> >>> On Tue, Oct 30, 2018 at 11:02 PM Marek Vasut
> >>> wrote:
> On 10/30/2018 10:30
On 11/01/2018 08:26 PM, Simon Goldschmidt wrote:
> On 31.10.2018 11:00, Marek Vasut wrote:
>> On 10/31/2018 06:44 AM, Simon Goldschmidt wrote:
>>> On Tue, Oct 30, 2018 at 11:02 PM Marek Vasut
>>> wrote:
On 10/30/2018 10:30 PM, Simon Goldschmidt wrote:
> On 30.10.2018 22:26, Marek Vasut wr
On 11/01/2018 10:13 PM, Simon Goldschmidt wrote:
> On 01.11.2018 21:59, Marek Vasut wrote:
>> On 11/01/2018 09:31 PM, Simon Goldschmidt wrote:
>>> On Thu, Nov 1, 2018 at 8:26 PM Simon Goldschmidt
>>> wrote:
On 31.10.2018 11:00, Marek Vasut wrote:
> On 10/31/2018 06:44 AM, Simon Goldschmid
On 01.11.2018 21:59, Marek Vasut wrote:
On 11/01/2018 09:31 PM, Simon Goldschmidt wrote:
On Thu, Nov 1, 2018 at 8:26 PM Simon Goldschmidt
wrote:
On 31.10.2018 11:00, Marek Vasut wrote:
On 10/31/2018 06:44 AM, Simon Goldschmidt wrote:
On Tue, Oct 30, 2018 at 11:02 PM Marek Vasut wrote:
On 1
On 11/01/2018 09:31 PM, Simon Goldschmidt wrote:
> On Thu, Nov 1, 2018 at 8:26 PM Simon Goldschmidt
> wrote:
>>
>> On 31.10.2018 11:00, Marek Vasut wrote:
>>> On 10/31/2018 06:44 AM, Simon Goldschmidt wrote:
On Tue, Oct 30, 2018 at 11:02 PM Marek Vasut wrote:
> On 10/30/2018 10:30 PM, Si
On Thu, Nov 1, 2018 at 8:26 PM Simon Goldschmidt
wrote:
>
> On 31.10.2018 11:00, Marek Vasut wrote:
> > On 10/31/2018 06:44 AM, Simon Goldschmidt wrote:
> >> On Tue, Oct 30, 2018 at 11:02 PM Marek Vasut wrote:
> >>> On 10/30/2018 10:30 PM, Simon Goldschmidt wrote:
> On 30.10.2018 22:26, Mare
On 31.10.2018 11:00, Marek Vasut wrote:
On 10/31/2018 06:44 AM, Simon Goldschmidt wrote:
On Tue, Oct 30, 2018 at 11:02 PM Marek Vasut wrote:
On 10/30/2018 10:30 PM, Simon Goldschmidt wrote:
On 30.10.2018 22:26, Marek Vasut wrote:
On 10/30/2018 10:23 PM, Simon Goldschmidt wrote:
Correctly de
On 10/31/2018 06:44 AM, Simon Goldschmidt wrote:
> On Tue, Oct 30, 2018 at 11:02 PM Marek Vasut wrote:
>>
>> On 10/30/2018 10:30 PM, Simon Goldschmidt wrote:
>>> On 30.10.2018 22:26, Marek Vasut wrote:
On 10/30/2018 10:23 PM, Simon Goldschmidt wrote:
> Correctly define CONFIG_SPL_MAX_FOOT
On Tue, Oct 30, 2018 at 11:02 PM Marek Vasut wrote:
>
> On 10/30/2018 10:30 PM, Simon Goldschmidt wrote:
> > On 30.10.2018 22:26, Marek Vasut wrote:
> >> On 10/30/2018 10:23 PM, Simon Goldschmidt wrote:
> >>> Correctly define CONFIG_SPL_MAX_FOOTPRINT to make the default arm
> >>> linker script for
On 10/30/2018 10:30 PM, Simon Goldschmidt wrote:
> On 30.10.2018 22:26, Marek Vasut wrote:
>> On 10/30/2018 10:23 PM, Simon Goldschmidt wrote:
>>> Correctly define CONFIG_SPL_MAX_FOOTPRINT to make the default arm
>>> linker script for SPL check the total SRAM size available for SPL
>>> (code, data,
On 30.10.2018 22:26, Marek Vasut wrote:
On 10/30/2018 10:23 PM, Simon Goldschmidt wrote:
Correctly define CONFIG_SPL_MAX_FOOTPRINT to make the default arm
linker script for SPL check the total SRAM size available for SPL
(code, data, bss, heap, global data).
The previously existing define CONFI
On 10/30/2018 10:23 PM, Simon Goldschmidt wrote:
> Correctly define CONFIG_SPL_MAX_FOOTPRINT to make the default arm
> linker script for SPL check the total SRAM size available for SPL
> (code, data, bss, heap, global data).
>
> The previously existing define CONFIG_SPL_MAX_SIZE seems to only
> ch
Correctly define CONFIG_SPL_MAX_FOOTPRINT to make the default arm
linker script for SPL check the total SRAM size available for SPL
(code, data, bss, heap, global data).
The previously existing define CONFIG_SPL_MAX_SIZE seems to only
check the binary size (which is without bss, heap and gd).
Sig
13 matches
Mail list logo