On 10 October 2018 at 00:28, Andy Yan wrote:
> Hi Simon:
>
> Simon Glass 于2018年8月30日周四 上午8:42写道:
>>
>> On 7 August 2018 at 05:44, Andy Yan wrote:
>> > Memory region for fdt should be reserved, or they
>> > may be allocated by other module via lmb_alloc.
>> > Then the fdt data will be destroy.
>>
Hi Simon:
Simon Glass 于2018年8月30日周四 上午8:42写道:
> On 7 August 2018 at 05:44, Andy Yan wrote:
> > Memory region for fdt should be reserved, or they
> > may be allocated by other module via lmb_alloc.
> > Then the fdt data will be destroy.
> >
> > We found a case on a board with 64MB DRAM like bell
On 7 August 2018 at 05:44, Andy Yan wrote:
> Memory region for fdt should be reserved, or they
> may be allocated by other module via lmb_alloc.
> Then the fdt data will be destroy.
>
> We found a case on a board with 64MB DRAM like bellow:
>
> No ethernet found.
> Hit any key to stop autoboot: 0
ping
Andy Yan 于2018年8月7日周二 下午7:43写道:
> Memory region for fdt should be reserved, or they
> may be allocated by other module via lmb_alloc.
> Then the fdt data will be destroy.
>
> We found a case on a board with 64MB DRAM like bellow:
>
> No ethernet found.
> Hit any key to stop autoboot: 0
> A
Memory region for fdt should be reserved, or they
may be allocated by other module via lmb_alloc.
Then the fdt data will be destroy.
We found a case on a board with 64MB DRAM like bellow:
No ethernet found.
Hit any key to stop autoboot: 0
ANDROID: reboot reason: "recovery"
FDT load addr 0x10f000
5 matches
Mail list logo