On Thursday 28 July 2016 07:14 PM, Tom Rini wrote:
On Thu, Jul 28, 2016 at 02:08:10PM +0200, Marek Vasut wrote:
On 07/27/2016 05:37 AM, Keerthy wrote:
On Wednesday 27 July 2016 09:05 AM, Keerthy wrote:
On SoCs like DRA7, OMAP5 one cannot enable hypervisor mode directly
from the
u-boot beca
On Thu, Jul 28, 2016 at 02:08:10PM +0200, Marek Vasut wrote:
> On 07/27/2016 05:37 AM, Keerthy wrote:
> >
> >
> > On Wednesday 27 July 2016 09:05 AM, Keerthy wrote:
> >> On SoCs like DRA7, OMAP5 one cannot enable hypervisor mode directly
> >> from the
> >> u-boot because the ROM code puts the chi
Hi Marek,
On Thursday 28 July 2016 05:38 PM, Marek Vasut wrote:
On 07/27/2016 05:37 AM, Keerthy wrote:
On Wednesday 27 July 2016 09:05 AM, Keerthy wrote:
On SoCs like DRA7, OMAP5 one cannot enable hypervisor mode directly
from the
u-boot because the ROM code puts the chip to supervisor mode
On 07/27/2016 05:37 AM, Keerthy wrote:
>
>
> On Wednesday 27 July 2016 09:05 AM, Keerthy wrote:
>> On SoCs like DRA7, OMAP5 one cannot enable hypervisor mode directly
>> from the
>> u-boot because the ROM code puts the chip to supervisor mode after it
>> jumps to boot loader.
>>
>> Patch 1: Intro
On Wednesday 27 July 2016 09:05 AM, Keerthy wrote:
On SoCs like DRA7, OMAP5 one cannot enable hypervisor mode directly from the
u-boot because the ROM code puts the chip to supervisor mode after it
jumps to boot loader.
Patch 1: Introduces a weak function which can be overridden specific to
So
On SoCs like DRA7, OMAP5 one cannot enable hypervisor mode directly from the
u-boot because the ROM code puts the chip to supervisor mode after it
jumps to boot loader.
Patch 1: Introduces a weak function which can be overridden specific to
SoCs to switch to hypervisor mode.
Patch 2: overrides we
6 matches
Mail list logo
