On 2017-06-13 00:42, Tom Rini wrote:
> On Wed, May 10, 2017 at 03:41:32PM +0200, Manfred Schlaegl wrote:
>
>> Using u-boot-2017.05 on i.MX6UL we ran into following problem:
>> Initially U-Boot could be started normally.
>> If we added one random command in configurat
On 2017-05-18 17:37, Jagan Teki wrote:
> On Thu, May 18, 2017 at 9:04 PM, Manfred Schlaegl
> <manfred.schla...@ginzinger.com> wrote:
>> On 2017-05-18 16:59, Lothar Waßmann wrote:
>>> Manfred Schlaegl <manfred.schla...@ginzinger.com> wrote:
>>>
&g
On 2017-05-18 16:59, Lothar Waßmann wrote:
> Manfred Schlaegl <manfred.schla...@ginzinger.com> wrote:
>
>> On 2017-05-17 06:13, Lokesh Vutla wrote:
>>>
>>>
>>> On Tuesday 16 May 2017 07:59 PM, Manfred Schlaegl wrote:
>>>> On 2017-05-11 08:
On 2017-05-17 06:13, Lokesh Vutla wrote:
>
>
> On Tuesday 16 May 2017 07:59 PM, Manfred Schlaegl wrote:
>> On 2017-05-11 08:53, Lokesh Vutla wrote:
>>>
>>>
>>> On Wednesday 10 May 2017 07:11 PM, Manfred Schlaegl wrote:
>>>> Using u
On 2017-05-11 14:12, Jagan Teki wrote:
> On Wed, May 10, 2017 at 7:11 PM, Manfred Schlaegl
> <manfred.schla...@ginzinger.com> wrote:
>> Using u-boot-2017.05 on i.MX6UL we ran into following problem:
>> Initially U-Boot could be started normally.
>> If we added one r
On 2017-05-11 08:53, Lokesh Vutla wrote:
>
>
> On Wednesday 10 May 2017 07:11 PM, Manfred Schlaegl wrote:
>> Using u-boot-2017.05 on i.MX6UL we ran into following problem:
>> Initially U-Boot could be started normally.
>> If we added one random command in configu
Using u-boot-2017.05 on i.MX6UL we ran into following problem:
Initially U-Boot could be started normally.
If we added one random command in configuration, the newly generated
image hung at startup (last output was DRAM: 256 MiB).
We tracked this down to a data abort within relocation
7 matches
Mail list logo