Re: [PATCH] arm: K3: Increase default SYSFW image size allocation

2020-05-11 Thread Lokesh Vutla
On 01/05/20 12:42 AM, Andrew F. Davis wrote: > The memory allocated to store the FIT image containing SYSFW and board > configuration data is statically defined to the largest size expected. > Some additions to the board configuration data has pushed us slightly > over the current defined size

[PATCH] arm: K3: Increase default SYSFW image size allocation

2020-04-30 Thread Andrew F. Davis
The memory allocated to store the FIT image containing SYSFW and board configuration data is statically defined to the largest size expected. Some additions to the board configuration data has pushed us slightly over the current defined size on some HS devices, expand to 278000. Signed-off-by:

Re: [U-Boot] [PATCH] arm: K3: Increase default SYSFW image size allocation

2019-10-05 Thread Tom Rini
On Tue, Oct 01, 2019 at 10:33:43AM -0400, Andrew F. Davis wrote: > The memory allocated to store the FIT image containing SYSFW and board > configuration data is statically defined to the largest size expected. > This was 269000 bytes but now needs to be grown to 276000 to make room > for the

[U-Boot] [PATCH] arm: K3: Increase default SYSFW image size allocation

2019-10-01 Thread Andrew F. Davis
The memory allocated to store the FIT image containing SYSFW and board configuration data is statically defined to the largest size expected. This was 269000 bytes but now needs to be grown to 276000 to make room for the signatures attached to the board configuration data on High Security devices.