mvebu/x530: Difference between spl/u-boot-spl.bin and spl/u-boot-spl-dtb.bin
Hello!
I would like to ask, what is the difference between spl/u-boot-spl.bin and spl/u-boot-spl-dtb.bin binaries?
Because there is board/alliedtelesis/x530/kwbimage.cfg file which overrides global file arch/arm/mach-mvebu/kwbimage.cfg.in and the only difference between these files is that board specific file uses spl/u-boot-spl-dtb.bin instead of spl/u-boot-spl.bin.
On Thu, Oct 7, 2021 at 1:38 AM Pali Rohár pali@kernel.org wrote:
Hello!
I would like to ask, what is the difference between spl/u-boot-spl.bin and spl/u-boot-spl-dtb.bin binaries?
The latter has a dtb appended. But I can't recall the x530 specifically needing to be different to the other platforms... sure enough all the a385 boards the time the x530 was added used spl/u-boot-spl-dtb.bin.
Because there is board/alliedtelesis/x530/kwbimage.cfg file which overrides global file arch/arm/mach-mvebu/kwbimage.cfg.in and the only difference between these files is that board specific file uses spl/u-boot-spl-dtb.bin instead of spl/u-boot-spl.bin.
I think the real source of the discrepancy is that the addition of the x530 board was in flight at the same time as ca1a4c863232 ("mvebu: select boot device at SoC level"). I don't know of any reason specifically that the x530 needs to be different. If I get a chance I'll try it without a custom kwbimage.cfg.
On Thursday 07 October 2021 21:09:40 Chris Packham wrote:
On Thu, Oct 7, 2021 at 1:38 AM Pali Rohár pali@kernel.org wrote:
Hello!
I would like to ask, what is the difference between spl/u-boot-spl.bin and spl/u-boot-spl-dtb.bin binaries?
The latter has a dtb appended. But I can't recall the x530 specifically needing to be different to the other platforms... sure enough all the a385 boards the time the x530 was added used spl/u-boot-spl-dtb.bin.
I have checked that A385 Omnia board has these two files same. So seems that both files for this board have DTB appended.
Because there is board/alliedtelesis/x530/kwbimage.cfg file which overrides global file arch/arm/mach-mvebu/kwbimage.cfg.in and the only difference between these files is that board specific file uses spl/u-boot-spl-dtb.bin instead of spl/u-boot-spl.bin.
I think the real source of the discrepancy is that the addition of the x530 board was in flight at the same time as ca1a4c863232 ("mvebu: select boot device at SoC level"). I don't know of any reason specifically that the x530 needs to be different. If I get a chance I'll try it without a custom kwbimage.cfg.
Ok. If you have a time, please check if default kwbimage.cfg works. It could simplify build.
participants (2)
-
Chris Packham -
Pali Rohár