> -----Original Message----- > From: york sun > Sent: Thursday, February 09, 2017 4:43 AM > To: Peter Newton <peter.new...@nxp.com>; Stuart Yoder > <stuart.yo...@nxp.com>; ag...@suse.de; Prabhakar Kushwaha > <prabhakar.kushw...@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? --prabhakar _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
