On 07.02.2014, at 01:51, Scott Wood scottw...@freescale.com wrote:
On Thu, 2014-02-06 at 12:40 +0100, Alexander Graf wrote:
On 04.02.2014, at 02:59, Scott Wood scottw...@freescale.com wrote:
On Fri, 2014-01-31 at 12:16 +0100, Alexander Graf wrote:
With the qemu-ppce500 machine type we can
On Fri, 2014-02-07 at 12:52 +0100, Alexander Graf wrote:
On 07.02.2014, at 01:51, Scott Wood scottw...@freescale.com wrote:
On Thu, 2014-02-06 at 12:40 +0100, Alexander Graf wrote:
On 04.02.2014, at 02:59, Scott Wood scottw...@freescale.com wrote:
On Fri, 2014-01-31 at 12:16 +0100,
On 04.02.2014, at 02:59, Scott Wood scottw...@freescale.com wrote:
On Fri, 2014-01-31 at 12:16 +0100, Alexander Graf wrote:
With the qemu-ppce500 machine type we can run the same board with
either an e500v2 or an e500mc core plugged in.
This means that the IVOR setup can't be based on
On Thu, 2014-02-06 at 12:40 +0100, Alexander Graf wrote:
On 04.02.2014, at 02:59, Scott Wood scottw...@freescale.com wrote:
On Fri, 2014-01-31 at 12:16 +0100, Alexander Graf wrote:
With the qemu-ppce500 machine type we can run the same board with
either an e500v2 or an e500mc core plugged
On Fri, 2014-01-31 at 12:16 +0100, Alexander Graf wrote:
With the qemu-ppce500 machine type we can run the same board with
either an e500v2 or an e500mc core plugged in.
This means that the IVOR setup can't be based on compile time decisions,
so instead we have to do a runtime check which
With the qemu-ppce500 machine type we can run the same board with
either an e500v2 or an e500mc core plugged in.
This means that the IVOR setup can't be based on compile time decisions,
so instead we have to do a runtime check which CPU generation we're
running on.
Signed-off-by: Alexander Graf
On 01/31/2014 03:16 AM, Alexander Graf wrote:
With the qemu-ppce500 machine type we can run the same board with
either an e500v2 or an e500mc core plugged in.
This means that the IVOR setup can't be based on compile time decisions,
so instead we have to do a runtime check which CPU
7 matches
Mail list logo