Re: [U-Boot] [PATCH 2/2] image: fit: Show information about OS type in firwmare case too

2018-04-03 Thread Michal Simek
On 30.3.2018 10:40, Simon Glass wrote: > On 26 March 2018 at 22:31, Michal Simek wrote: >> SPL ATF implementation requires FIT image with partitions where the one >> is Firmware/ATF and another one Firmware/U-Boot. OS field is used for >> recording that difference that's

Re: [U-Boot] [PATCH 2/2] image: fit: Show information about OS type in firwmare case too

2018-04-02 Thread Jun Nie
2018-03-26 22:31 GMT+08:00 Michal Simek : > SPL ATF implementation requires FIT image with partitions where the one > is Firmware/ATF and another one Firmware/U-Boot. OS field is used for > recording that difference that's why make sense to show values there for > Firmware

Re: [U-Boot] [PATCH 2/2] image: fit: Show information about OS type in firwmare case too

2018-03-30 Thread Simon Glass
On 26 March 2018 at 22:31, Michal Simek wrote: > SPL ATF implementation requires FIT image with partitions where the one > is Firmware/ATF and another one Firmware/U-Boot. OS field is used for > recording that difference that's why make sense to show values there for >

[U-Boot] [PATCH 2/2] image: fit: Show information about OS type in firwmare case too

2018-03-26 Thread Michal Simek
SPL ATF implementation requires FIT image with partitions where the one is Firmware/ATF and another one Firmware/U-Boot. OS field is used for recording that difference that's why make sense to show values there for Firmware types. For example: Image 0 (atf) Description: ATF bl31.bin