On 02/08/2017 06:43 PM, Prabhakar Kushwaha wrote:
-----Original Message----- From: york sun Sent: Thursday, February 09, 2017 4:43 AM To: Peter Newton peter.newton@nxp.com; Stuart Yoder stuart.yoder@nxp.com; agraf@suse.de; Prabhakar Kushwaha prabhakar.kushwaha@nxp.com Cc: u-boot@lists.denx.de Subject: Re: distro boot on ls2085ardb
On 02/08/2017 03:08 PM, Peter Newton wrote:
From: york sun
<snip>
It was for backward compatibility. Even I have pointed out numerous times
(internally) that cp.b should not be used for this case, and
even pointed out how to make a FIT image with load address, the board maintainer(s) didn't act. One change I can propose is to drop the "cp.b
$kernel_start $kernel_load $kernel_size" and run "bootm
$kernel_start" directly. If it fails, then falls to distro_bootcmd.
I wondered why we needed the cp.b at all. How do you add the load address
to fit?
FIT image header has load address and entry address. Our SDK didn't fill in load address before (not sure now). If the load address exists, the image(s) would be copied accordingly.
Our SDK provide load address for Kernel and device tree. But it don’t provide load address for file system. This means, "its" file should be updated to provide load address of filesystem also?
I think so. I have verified this before and sent email to internal team.
There was an issue before concerning loading to high region. It was fixed by commit c1913cb7897f77a26791765ef9c3c02b3588f3c1 in Feb 2016. We have been using low region for kernel and ramdisk, so this bug didn't block us.
Let's take this to internal team for further discussion.
York