We support booting both from SD/MMC images and SPI images on the
RK3399-Q7 for different use-cases (e.g. external boot in development
from the SD card, internal boot from MMC or SPI depending on whether
the SPI flash is populated on any given configuration option).
In getting the SPI image suppor
Hi Philipp,
This patch makes all the Rockchip SoCs with BACK_TO_BROM enabled can not
work,
does the size correct for the SPL correct?
Thanks,
- Kever
On 04/17/2017 11:47 PM, Philipp Tomsich wrote:
We support booting both from SD/MMC images and SPI images on the
RK3399-Q7 for different use-ca
Kever,
What are the requirements for BACK_TO_BROM?
All I can see about how BACK_TO_BROM works is that it needs to save the register
context on the stack for returning to the ROM, but that seems to be only half
the story.
Assuming that the header0 structure plays into this, the only significant
Hi Philipp,
Am Mittwoch, 17. Mai 2017, 12:12:51 CEST schrieb Dr. Philipp Tomsich:
> What are the requirements for BACK_TO_BROM?
> All I can see about how BACK_TO_BROM works is that it needs to save the
> register
> context on the stack for returning to the ROM, but that seems to be only half
> t
Heiko,
thanks for the insight into the BROM.
I’ll respin this with part of the change reverted and have Kever test.
Regards,
Philipp.
> On 19 May 2017, at 20:39, Heiko Stuebner wrote:
>
> Hi Philipp,
>
> Am Mittwoch, 17. Mai 2017, 12:12:51 CEST schrieb Dr. Philipp Tomsich:
>> What are the req
Am Freitag, 19. Mai 2017, 20:44:07 CEST schrieb Dr. Philipp Tomsich:
> Heiko,
>
> thanks for the insight into the BROM.
> I’ll respin this with part of the change reverted and have Kever test.
The patch is already in Simon's next branch [0],
so a fixup might be better :-)
Heiko
[0]
http://git
6 matches
Mail list logo
