On Tue, Sep 29, 2020 at 06:13:09PM +0100, André Przywara wrote:
> On 29/09/2020 14:23, Tom Rini wrote:
>
> Hi Tom,
>
> > On Thu, Sep 24, 2020 at 01:17:14AM +0100, Andre Przywara wrote:
> >
> >> CONFIG_ARCH_SUPPORT_TFABOOT seems to be a guard option to enable various
> >> platform specific hacks,
On 29/09/2020 14:23, Tom Rini wrote:
Hi Tom,
> On Thu, Sep 24, 2020 at 01:17:14AM +0100, Andre Przywara wrote:
>
>> CONFIG_ARCH_SUPPORT_TFABOOT seems to be a guard option to enable various
>> platform specific hacks, when U-Boot is run under TF-A.
>> Now that the QEMU port does not need to diffe
On Thu, Sep 24, 2020 at 01:17:14AM +0100, Andre Przywara wrote:
> CONFIG_ARCH_SUPPORT_TFABOOT seems to be a guard option to enable various
> platform specific hacks, when U-Boot is run under TF-A.
> Now that the QEMU port does not need to differentiate between secure
> vs. non-secure anymore (this
CONFIG_ARCH_SUPPORT_TFABOOT seems to be a guard option to enable various
platform specific hacks, when U-Boot is run under TF-A.
Now that the QEMU port does not need to differentiate between secure
vs. non-secure anymore (this is taken care of by the DTB), there is
no need for a build-time option a
4 matches
Mail list logo