Re: [U-Boot] FIT Image with same kernel but different load/entry point

2018-04-09 Thread Clément Péron
> I think what you want is to use kernel_noload and then load/entry values > are ignored and we use the kernel in-place. Yes, I will try that Thanks, Clement ___ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot

Re: [U-Boot] FIT Image with same kernel but different load/entry point

2018-04-08 Thread Tom Rini
On Tue, Apr 03, 2018 at 07:17:13PM +0200, Clément Péron wrote: > Hi, > > Is it possible to have one kernel entry in a FIT image with two > different load/entry point. > > I have 2 boards which share the same kernel but doesn't have the same > entry/load point. I think what you want is to use ker

Re: [U-Boot] FIT Image with same kernel but different load/entry point

2018-04-04 Thread Clément Péron
Hi Peter, > Not sure if it does exactly what you need but the pine64 board supports > multiple boards with different device trees for each board in the fit image. > > Peter No it's not why I need, I was looking to do something like this but without doubling the size : kernel-bcm {

Re: [U-Boot] FIT Image with same kernel but different load/entry point

2018-04-04 Thread Peter Robinson
On Tue, 3 Apr 2018, 19:17 Clément Péron, wrote: > Hi, > > Is it possible to have one kernel entry in a FIT image with two > different load/entry point. > > I have 2 boards which share the same kernel but doesn't have the same > entry/load point. > Not sure if it does exactly what you need but th

[U-Boot] FIT Image with same kernel but different load/entry point

2018-04-03 Thread Clément Péron
Hi, Is it possible to have one kernel entry in a FIT image with two different load/entry point. I have 2 boards which share the same kernel but doesn't have the same entry/load point. Thanks, Clement ___ U-Boot mailing list U-Boot@lists.denx.de https:/