On Thu, Mar 12, 2015 at 09:18:01AM +0100, Thierry Reding wrote:
> On Wed, Mar 11, 2015 at 11:12:25AM -0400, Tom Rini wrote:
> > * PGP Signed by an unknown key
> >
> > On Mon, Mar 09, 2015 at 08:00:18AM +0100, Jan Kiszka wrote:
> >
> > > In this case the secure code lives in RAM, and hence the mem
On Wed, Mar 11, 2015 at 11:12:25AM -0400, Tom Rini wrote:
> * PGP Signed by an unknown key
>
> On Mon, Mar 09, 2015 at 08:00:18AM +0100, Jan Kiszka wrote:
>
> > In this case the secure code lives in RAM, and hence the memory node in
> > the device tree needs to be adjusted. This avoids that the O
Am 2015-03-11 um 16:12 schrieb Tom Rini:
> On Mon, Mar 09, 2015 at 08:00:18AM +0100, Jan Kiszka wrote:
>
>> In this case the secure code lives in RAM, and hence the memory node in
>> the device tree needs to be adjusted. This avoids that the OS will map
>> and possibly access the reservation.
>>
>
On Mon, Mar 09, 2015 at 08:00:18AM +0100, Jan Kiszka wrote:
> In this case the secure code lives in RAM, and hence the memory node in
> the device tree needs to be adjusted. This avoids that the OS will map
> and possibly access the reservation.
>
> Add support for setting CONFIG_ARMV7_SECURE_RES
In this case the secure code lives in RAM, and hence the memory node in
the device tree needs to be adjusted. This avoids that the OS will map
and possibly access the reservation.
Add support for setting CONFIG_ARMV7_SECURE_RESERVE_SIZE to carve out
such a region. We only support cutting off memor
5 matches
Mail list logo