On Wed, Aug 26, 2015 at 12:39 PM, Dave Martin wrote:
> Shouldn't the bootloader or firmware be doing this stuff, and if not,
> why not?
Firmware yes, bootloader no, or maybe.
Bootloaders IMO loads in images, checksum, even public key check or
whatever, then sets up the basics and boot them.
On Wed, Aug 26, 2015 at 12:39 PM, Dave Martin wrote:
> Shouldn't the bootloader or firmware be doing this stuff, and if not,
> why not?
Firmware yes, bootloader no, or maybe.
Bootloaders IMO loads in images, checksum, even public key check or
whatever, then sets up the
On 24/08/15 14:55, Christopher Covington wrote:
ARM Linux appears to have never been made aware of the ARMv7 security
extensions. When CONFIG_ARM_SEC_EXT=y, have it probe for its security
state by checking whether CNTFRQ is writeable and potentially make
mode changes based on the information.
On Wed, Aug 26, 2015 at 10:19:39AM -0400, Christopher Covington wrote:
> Hi,
>
> Thank you for the feedback.
>
> On 08/26/2015 06:48 AM, Russell King - ARM Linux wrote:
> > On Wed, Aug 26, 2015 at 11:39:42AM +0100, Dave Martin wrote:
> >> On Mon, Aug 24, 2015 at 09:55:26AM -0400, Christopher
On Wed, Aug 26, 2015 at 10:19:39AM -0400, Christopher Covington wrote:
Hi,
Thank you for the feedback.
On 08/26/2015 06:48 AM, Russell King - ARM Linux wrote:
On Wed, Aug 26, 2015 at 11:39:42AM +0100, Dave Martin wrote:
On Mon, Aug 24, 2015 at 09:55:26AM -0400, Christopher Covington
On 24/08/15 14:55, Christopher Covington wrote:
ARM Linux appears to have never been made aware of the ARMv7 security
extensions. When CONFIG_ARM_SEC_EXT=y, have it probe for its security
state by checking whether CNTFRQ is writeable and potentially make
mode changes based on the information.
Hi,
Thank you for the feedback.
On 08/26/2015 06:48 AM, Russell King - ARM Linux wrote:
> On Wed, Aug 26, 2015 at 11:39:42AM +0100, Dave Martin wrote:
>> On Mon, Aug 24, 2015 at 09:55:26AM -0400, Christopher Covington wrote:
>>> ARM Linux appears to have never been made aware of the ARMv7
On Wed, Aug 26, 2015 at 11:39:42AM +0100, Dave Martin wrote:
> On Mon, Aug 24, 2015 at 09:55:26AM -0400, Christopher Covington wrote:
> > ARM Linux appears to have never been made aware of the ARMv7 security
> > extensions. When CONFIG_ARM_SEC_EXT=y, have it probe for its security
> > state by
On Mon, Aug 24, 2015 at 09:55:26AM -0400, Christopher Covington wrote:
> +/*
> + * ARM Linux has the most features available in hypervisor mode and
> + * running in non-secure mode is recommended. Thus, try to get into
> + * hypervisor mode if we're not already there, or failing that, try
> + * to
On Mon, Aug 24, 2015 at 09:55:26AM -0400, Christopher Covington wrote:
> ARM Linux appears to have never been made aware of the ARMv7 security
> extensions. When CONFIG_ARM_SEC_EXT=y, have it probe for its security
> state by checking whether CNTFRQ is writeable and potentially make
> mode changes
On 24 August 2015 at 15:55, Christopher Covington wrote:
> ARM Linux appears to have never been made aware of the ARMv7 security
> extensions. When CONFIG_ARM_SEC_EXT=y, have it probe for its security
> state by checking whether CNTFRQ is writeable and potentially make
> mode changes based on the
On 24 August 2015 at 15:55, Christopher Covington c...@codeaurora.org wrote:
ARM Linux appears to have never been made aware of the ARMv7 security
extensions. When CONFIG_ARM_SEC_EXT=y, have it probe for its security
state by checking whether CNTFRQ is writeable and potentially make
mode
On Mon, Aug 24, 2015 at 09:55:26AM -0400, Christopher Covington wrote:
ARM Linux appears to have never been made aware of the ARMv7 security
extensions. When CONFIG_ARM_SEC_EXT=y, have it probe for its security
state by checking whether CNTFRQ is writeable and potentially make
mode changes
On Wed, Aug 26, 2015 at 11:39:42AM +0100, Dave Martin wrote:
On Mon, Aug 24, 2015 at 09:55:26AM -0400, Christopher Covington wrote:
ARM Linux appears to have never been made aware of the ARMv7 security
extensions. When CONFIG_ARM_SEC_EXT=y, have it probe for its security
state by checking
On Mon, Aug 24, 2015 at 09:55:26AM -0400, Christopher Covington wrote:
+/*
+ * ARM Linux has the most features available in hypervisor mode and
+ * running in non-secure mode is recommended. Thus, try to get into
+ * hypervisor mode if we're not already there, or failing that, try
+ * to get
Hi,
Thank you for the feedback.
On 08/26/2015 06:48 AM, Russell King - ARM Linux wrote:
On Wed, Aug 26, 2015 at 11:39:42AM +0100, Dave Martin wrote:
On Mon, Aug 24, 2015 at 09:55:26AM -0400, Christopher Covington wrote:
ARM Linux appears to have never been made aware of the ARMv7 security
ARM Linux appears to have never been made aware of the ARMv7 security
extensions. When CONFIG_ARM_SEC_EXT=y, have it probe for its security
state by checking whether CNTFRQ is writeable and potentially make
mode changes based on the information. The most features are available
from hypervisor
ARM Linux appears to have never been made aware of the ARMv7 security
extensions. When CONFIG_ARM_SEC_EXT=y, have it probe for its security
state by checking whether CNTFRQ is writeable and potentially make
mode changes based on the information. The most features are available
from hypervisor
18 matches
Mail list logo