Hi Romain,
On 21 January 2017 at 00:51, Romain Perier romain.perier@collabora.com wrote:
Hi,
Le 21/01/2017 à 04:51, Simon Glass a écrit :
On 17 January 2017 at 02:32, Romain Perier romain.perier@collabora.com wrote:
Like the rock2, this board has been tested with back to brom feature. This commits adjusts environment offset regarding if back_to_brom is enabled or not and uses this feature by default.
Signed-off-by: Romain Perier romain.perier@collabora.com
configs/firefly-rk3288_defconfig | 2 ++ include/configs/firefly-rk3288.h | 9 +++++++++ 2 files changed, 11 insertions(+)
We need at least one board that does not use this option. Also, doesn't this mean that we need to change how the image is written to the board?
Should we use binman to create a suitable image?
Regards, Simon
Why do you want at least one board without this option ? for testing that it's still working without back_to_brom ? That's weird because all rk3288-based board has the same limitations regarding the SPL, no ?
Yes, but remember this is a non-standard booting mechanism, and one that I hope we can move away from in future. Also firefly does not *need* this mechanism. If we don't have one board that uses the standard mechanism then it might stop working.
Regards, Simon