Skip to contentSkip to conversation

doc: board: qemu-ppce500: Update supported and unsupported

PATCH Superseded Pali Rohár 2 participants 8 messages Dec 20, 2022 – Dec 24, 2022

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 doc: board: qemu-ppce500: Update supported and unsupported

qemu can emulate also e500v1 core but cannot emulate CPUs from Freescale PowerPC QorIQ T and P series.

---
 doc/board/emulation/qemu-ppce500.rst | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)
doc/board/emulation/qemu-ppce500.rst +5 -3
index 5de0aaf55ded..10427cc56302 100644
@@ -7,7 +7,7 @@ QEMU PPC E500
 QEMU for PPC supports a special 'ppce500' machine designed for emulation and
 virtualization purposes. This document describes how to run U-Boot under it.
 
-The QEMU ppce500 machine models a generic PowerPC E500 virtual machine with
+The QEMU ppce500 machine models a generic PowerPC e500 virtual machine with
 support for the VirtIO standard networking device connected to the built-in
 PCI host controller. Some common devices in the CCSBAR space are modeled,
 including MPIC, 16550A UART devices, GPIO, I2C and PCI host controller with
@@ -39,6 +39,7 @@ embedded DTB created by QEMU reflects the new setting.
 Both qemu-system-ppc and qemu-system-ppc64 provide emulation for the following
 32-bit PowerPC CPUs:
 
+* e500v1
 * e500v2
 * e500mc
 
@@ -61,8 +62,9 @@ When U-Boot boots, you will notice the following::
 This is because we only specified a core name to QEMU and it does not have a
 meaningful SVR value which represents an actual SoC that integrates such core.
 You can specify a real world SoC device that QEMU has built-in support but all
-these SoCs are e500v2 based MPC85xx series, hence you cannot test anything
-built for P4080 (e500mc), P5020 (e5500) and T2080 (e6500).
+these SoCs are e500v1/e500v2 based MPC85xx series, hence you cannot test anything
+built for P10xx/P2010/P2020 (e500v2), P2O4x/P304x/P40xx (e500mc), P50xx/T10xx (e5500)
+and T208x/T4080/T4160/T4240 (e6500).
 
 By default a VirtIO standard PCI networking device is connected as an ethernet
 interface at PCI address 0.1.0, but we can switch that to an e1000 NIC by::
Signature · 1 line
2.20.1
#1 lore raw
Quoted 31 lines · Pali Rohár

qemu can emulate also e500v1 core but cannot emulate CPUs from Freescale PowerPC QorIQ T and P series.

---
 doc/board/emulation/qemu-ppce500.rst | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)
doc/board/emulation/qemu-ppce500.rst +2 -1
index 5de0aaf55ded..10427cc56302 100644
@@ -7,7 +7,7 @@ QEMU PPC E500
 QEMU for PPC supports a special 'ppce500' machine designed for emulation and
 virtualization purposes. This document describes how to run U-Boot under it.
 
-The QEMU ppce500 machine models a generic PowerPC E500 virtual machine with
+The QEMU ppce500 machine models a generic PowerPC e500 virtual machine with
 support for the VirtIO standard networking device connected to the built-in
 PCI host controller. Some common devices in the CCSBAR space are modeled,
 including MPIC, 16550A UART devices, GPIO, I2C and PCI host controller with
@@ -39,6 +39,7 @@ embedded DTB created by QEMU reflects the new setting.
 Both qemu-system-ppc and qemu-system-ppc64 provide emulation for the following
 32-bit PowerPC CPUs:
 
+* e500v1
 * e500v2
 * e500mc
 

doc/board/emulation/qemu-ppce500.rst When U-Boot boots, you will notice the following:: · line 66

Quoted 7 lines
doc/board/emulation/qemu-ppce500.rst +2 -2
@@ -61,8 +62,9 @@ When U-Boot boots, you will notice the following::
 This is because we only specified a core name to QEMU and it does not have a
 meaningful SVR value which represents an actual SoC that integrates such core.
 You can specify a real world SoC device that QEMU has built-in support but all
-these SoCs are e500v2 based MPC85xx series, hence you cannot test anything
-built for P4080 (e500mc), P5020 (e5500) and T2080 (e6500).
+these SoCs are e500v1/e500v2 based MPC85xx series, hence you cannot test anything
+built for P10xx/P2010/P2020 (e500v2), P2O4x/P304x/P40xx (e500mc), P50xx/T10xx (e5500)

typo: P2O4x

doc/board/emulation/qemu-ppce500.rst When U-Boot boots, you will notice the following::

Quoted 5 lines
doc/board/emulation/qemu-ppce500.rst +1 -1
+and T208x/T4080/T4160/T4240 (e6500).
 
 By default a VirtIO standard PCI networking device is connected as an ethernet
 interface at PCI address 0.1.0, but we can switch that to an e1000 NIC by::
--

Regards,
Bin

#2 lore raw
Quoted 31 lines · On Wednesday 21 December 2022 09:15:41 Bin Meng wrote:
Quoted 30 lines · Pali Rohár

qemu can emulate also e500v1 core but cannot emulate CPUs from Freescale PowerPC QorIQ T and P series.

---
 doc/board/emulation/qemu-ppce500.rst | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)
doc/board/emulation/qemu-ppce500.rst +2 -1
index 5de0aaf55ded..10427cc56302 100644
@@ -7,7 +7,7 @@ QEMU PPC E500
 QEMU for PPC supports a special 'ppce500' machine designed for emulation and
 virtualization purposes. This document describes how to run U-Boot under it.
 
-The QEMU ppce500 machine models a generic PowerPC E500 virtual machine with
+The QEMU ppce500 machine models a generic PowerPC e500 virtual machine with
 support for the VirtIO standard networking device connected to the built-in
 PCI host controller. Some common devices in the CCSBAR space are modeled,
 including MPIC, 16550A UART devices, GPIO, I2C and PCI host controller with
@@ -39,6 +39,7 @@ embedded DTB created by QEMU reflects the new setting.
 Both qemu-system-ppc and qemu-system-ppc64 provide emulation for the following
 32-bit PowerPC CPUs:
 
+* e500v1
 * e500v2
 * e500mc
 
Quoted 10 lines

doc/board/emulation/qemu-ppce500.rst When U-Boot boots, you will notice the following:: · line 66

Quoted 8 lines
doc/board/emulation/qemu-ppce500.rst +2 -2
@@ -61,8 +62,9 @@ When U-Boot boots, you will notice the following::
 This is because we only specified a core name to QEMU and it does not have a
 meaningful SVR value which represents an actual SoC that integrates such core.
 You can specify a real world SoC device that QEMU has built-in support but all
-these SoCs are e500v2 based MPC85xx series, hence you cannot test anything
-built for P4080 (e500mc), P5020 (e5500) and T2080 (e6500).
+these SoCs are e500v1/e500v2 based MPC85xx series, hence you cannot test anything
+built for P10xx/P2010/P2020 (e500v2), P2O4x/P304x/P40xx (e500mc), P50xx/T10xx (e5500)

typo: P2O4x

Where is a typo? I wrote P204x (which should mean both P2040 and P2041).

Quoted 8 lines

doc/board/emulation/qemu-ppce500.rst When U-Boot boots, you will notice the following::

Quoted 5 lines
doc/board/emulation/qemu-ppce500.rst +1 -1
+and T208x/T4080/T4160/T4240 (e6500).
 
 By default a VirtIO standard PCI networking device is connected as an ethernet
 interface at PCI address 0.1.0, but we can switch that to an e1000 NIC by::
--

Regards,
Bin

#3 lore raw
Quoted 44 lines · Pali Rohár
Quoted 31 lines · On Wednesday 21 December 2022 09:15:41 Bin Meng wrote:
Quoted 30 lines · Pali Rohár

qemu can emulate also e500v1 core but cannot emulate CPUs from Freescale PowerPC QorIQ T and P series.

---
 doc/board/emulation/qemu-ppce500.rst | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)
doc/board/emulation/qemu-ppce500.rst +2 -1
index 5de0aaf55ded..10427cc56302 100644
@@ -7,7 +7,7 @@ QEMU PPC E500
 QEMU for PPC supports a special 'ppce500' machine designed for emulation and
 virtualization purposes. This document describes how to run U-Boot under it.
 
-The QEMU ppce500 machine models a generic PowerPC E500 virtual machine with
+The QEMU ppce500 machine models a generic PowerPC e500 virtual machine with
 support for the VirtIO standard networking device connected to the built-in
 PCI host controller. Some common devices in the CCSBAR space are modeled,
 including MPIC, 16550A UART devices, GPIO, I2C and PCI host controller with
@@ -39,6 +39,7 @@ embedded DTB created by QEMU reflects the new setting.
 Both qemu-system-ppc and qemu-system-ppc64 provide emulation for the following
 32-bit PowerPC CPUs:
 
+* e500v1
 * e500v2
 * e500mc
 
Quoted 10 lines

doc/board/emulation/qemu-ppce500.rst When U-Boot boots, you will notice the following:: · line 66

Quoted 8 lines
doc/board/emulation/qemu-ppce500.rst +2 -2
@@ -61,8 +62,9 @@ When U-Boot boots, you will notice the following::
 This is because we only specified a core name to QEMU and it does not have a
 meaningful SVR value which represents an actual SoC that integrates such core.
 You can specify a real world SoC device that QEMU has built-in support but all
-these SoCs are e500v2 based MPC85xx series, hence you cannot test anything
-built for P4080 (e500mc), P5020 (e5500) and T2080 (e6500).
+these SoCs are e500v1/e500v2 based MPC85xx series, hence you cannot test anything
+built for P10xx/P2010/P2020 (e500v2), P2O4x/P304x/P40xx (e500mc), P50xx/T10xx (e5500)

typo: P2O4x

Quoted 1 line

Where is a typo? I wrote P204x (which should mean both P2040 and P2041).

Is that 0 or O? It looks like an O.

Quoted 6 lines
Quoted 6 lines

doc/board/emulation/qemu-ppce500.rst When U-Boot boots, you will notice the following::

Quoted 6 lines
doc/board/emulation/qemu-ppce500.rst +1 -1
+and T208x/T4080/T4160/T4240 (e6500).
 
 By default a VirtIO standard PCI networking device is connected as an ethernet
 interface at PCI address 0.1.0, but we can switch that to an e1000 NIC by::
--

Regards,
Bin

#4 lore raw
Quoted 45 lines · On Wednesday 21 December 2022 17:01:37 Bin Meng wrote:
Quoted 44 lines · Pali Rohár
Quoted 41 lines · On Wednesday 21 December 2022 09:15:41 Bin Meng wrote:
Quoted 31 lines · Pali Rohár

qemu can emulate also e500v1 core but cannot emulate CPUs from Freescale PowerPC QorIQ T and P series.

---
 doc/board/emulation/qemu-ppce500.rst | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)
doc/board/emulation/qemu-ppce500.rst +2 -1
index 5de0aaf55ded..10427cc56302 100644
@@ -7,7 +7,7 @@ QEMU PPC E500
 QEMU for PPC supports a special 'ppce500' machine designed for emulation and
 virtualization purposes. This document describes how to run U-Boot under it.
 
-The QEMU ppce500 machine models a generic PowerPC E500 virtual machine with
+The QEMU ppce500 machine models a generic PowerPC e500 virtual machine with
 support for the VirtIO standard networking device connected to the built-in
 PCI host controller. Some common devices in the CCSBAR space are modeled,
 including MPIC, 16550A UART devices, GPIO, I2C and PCI host controller with
@@ -39,6 +39,7 @@ embedded DTB created by QEMU reflects the new setting.
 Both qemu-system-ppc and qemu-system-ppc64 provide emulation for the following
 32-bit PowerPC CPUs:
 
+* e500v1
 * e500v2
 * e500mc
 

doc/board/emulation/qemu-ppce500.rst When U-Boot boots, you will notice the following:: · line 66

Quoted 7 lines
doc/board/emulation/qemu-ppce500.rst +2 -2
@@ -61,8 +62,9 @@ When U-Boot boots, you will notice the following::
 This is because we only specified a core name to QEMU and it does not have a
 meaningful SVR value which represents an actual SoC that integrates such core.
 You can specify a real world SoC device that QEMU has built-in support but all
-these SoCs are e500v2 based MPC85xx series, hence you cannot test anything
-built for P4080 (e500mc), P5020 (e5500) and T2080 (e6500).
+these SoCs are e500v1/e500v2 based MPC85xx series, hence you cannot test anything
+built for P10xx/P2010/P2020 (e500v2), P2O4x/P304x/P40xx (e500mc), P50xx/T10xx (e5500)

typo: P2O4x

Quoted 3 lines
Quoted 1 line

Where is a typo? I wrote P204x (which should mean both P2040 and P2041).

Is that 0 or O? It looks like an O.

Ou. Now I see what you mean. I had to look at it 3 times to see that difference is between number zero and capital letter o. I have no idea why I typed here letter instead of number... maybe because these keys are near each other.

Of course, it is zero not letter o. Sorry for this.

Would you fix it locally, or should I send a new patch version?

Quoted 9 lines
Quoted 6 lines
Quoted 6 lines

doc/board/emulation/qemu-ppce500.rst When U-Boot boots, you will notice the following::

Quoted 6 lines
doc/board/emulation/qemu-ppce500.rst +1 -1
+and T208x/T4080/T4160/T4240 (e6500).
 
 By default a VirtIO standard PCI networking device is connected as an ethernet
 interface at PCI address 0.1.0, but we can switch that to an e1000 NIC by::
--

Regards,
Bin

#5 lore raw
Quoted 51 lines · Pali Rohár
Quoted 45 lines · On Wednesday 21 December 2022 17:01:37 Bin Meng wrote:
Quoted 44 lines · Pali Rohár
Quoted 41 lines · On Wednesday 21 December 2022 09:15:41 Bin Meng wrote:
Quoted 31 lines · Pali Rohár

qemu can emulate also e500v1 core but cannot emulate CPUs from Freescale PowerPC QorIQ T and P series.

---
 doc/board/emulation/qemu-ppce500.rst | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)
doc/board/emulation/qemu-ppce500.rst +2 -1
index 5de0aaf55ded..10427cc56302 100644
@@ -7,7 +7,7 @@ QEMU PPC E500
 QEMU for PPC supports a special 'ppce500' machine designed for emulation and
 virtualization purposes. This document describes how to run U-Boot under it.
 
-The QEMU ppce500 machine models a generic PowerPC E500 virtual machine with
+The QEMU ppce500 machine models a generic PowerPC e500 virtual machine with
 support for the VirtIO standard networking device connected to the built-in
 PCI host controller. Some common devices in the CCSBAR space are modeled,
 including MPIC, 16550A UART devices, GPIO, I2C and PCI host controller with
@@ -39,6 +39,7 @@ embedded DTB created by QEMU reflects the new setting.
 Both qemu-system-ppc and qemu-system-ppc64 provide emulation for the following
 32-bit PowerPC CPUs:
 
+* e500v1
 * e500v2
 * e500mc
 

doc/board/emulation/qemu-ppce500.rst When U-Boot boots, you will notice the following:: · line 66

Quoted 7 lines
doc/board/emulation/qemu-ppce500.rst +2 -2
@@ -61,8 +62,9 @@ When U-Boot boots, you will notice the following::
 This is because we only specified a core name to QEMU and it does not have a
 meaningful SVR value which represents an actual SoC that integrates such core.
 You can specify a real world SoC device that QEMU has built-in support but all
-these SoCs are e500v2 based MPC85xx series, hence you cannot test anything
-built for P4080 (e500mc), P5020 (e5500) and T2080 (e6500).
+these SoCs are e500v1/e500v2 based MPC85xx series, hence you cannot test anything
+built for P10xx/P2010/P2020 (e500v2), P2O4x/P304x/P40xx (e500mc), P50xx/T10xx (e5500)

typo: P2O4x

Quoted 3 lines
Quoted 1 line

Where is a typo? I wrote P204x (which should mean both P2040 and P2041).

Is that 0 or O? It looks like an O.

Quoted 9 lines

Ou. Now I see what you mean. I had to look at it 3 times to see that difference is between number zero and capital letter o. I have no idea why I typed here letter instead of number... maybe because these keys are near each other.

Of course, it is zero not letter o. Sorry for this.

Would you fix it locally, or should I send a new patch version?

Please send a new patch as I assume I am not the one to pick up this patch.

Regards,
Bin

#6 lore raw

PATCH v2 1/1 doc: board: qemu-ppce500: Update supported and unsupported

In reply to Pali Rohár

qemu can emulate also e500v1 core but cannot emulate CPUs from Freescale PowerPC QorIQ T and P series.

---
Changes in v2:
* sed 's/P2O4x/P204x/'

---
 doc/board/emulation/qemu-ppce500.rst | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)
doc/board/emulation/qemu-ppce500.rst +5 -3
index 5de0aaf55ded..82b50a01de7e 100644
@@ -7,7 +7,7 @@ QEMU PPC E500
 QEMU for PPC supports a special 'ppce500' machine designed for emulation and
 virtualization purposes. This document describes how to run U-Boot under it.
 
-The QEMU ppce500 machine models a generic PowerPC E500 virtual machine with
+The QEMU ppce500 machine models a generic PowerPC e500 virtual machine with
 support for the VirtIO standard networking device connected to the built-in
 PCI host controller. Some common devices in the CCSBAR space are modeled,
 including MPIC, 16550A UART devices, GPIO, I2C and PCI host controller with
@@ -39,6 +39,7 @@ embedded DTB created by QEMU reflects the new setting.
 Both qemu-system-ppc and qemu-system-ppc64 provide emulation for the following
 32-bit PowerPC CPUs:
 
+* e500v1
 * e500v2
 * e500mc
 
@@ -61,8 +62,9 @@ When U-Boot boots, you will notice the following::
 This is because we only specified a core name to QEMU and it does not have a
 meaningful SVR value which represents an actual SoC that integrates such core.
 You can specify a real world SoC device that QEMU has built-in support but all
-these SoCs are e500v2 based MPC85xx series, hence you cannot test anything
-built for P4080 (e500mc), P5020 (e5500) and T2080 (e6500).
+these SoCs are e500v1/e500v2 based MPC85xx series, hence you cannot test anything
+built for P10xx/P2010/P2020 (e500v2), P204x/P304x/P40xx (e500mc), P50xx/T10xx (e5500)
+and T208x/T4080/T4160/T4240 (e6500).
 
 By default a VirtIO standard PCI networking device is connected as an ethernet
 interface at PCI address 0.1.0, but we can switch that to an e1000 NIC by::
Signature · 1 line
2.20.1
Reviewed-by on v2 1/1
#7 lore raw
Quoted 4 lines · Pali Rohár

qemu can emulate also e500v1 core but cannot emulate CPUs from Freescale PowerPC QorIQ T and P series.

Quoted 9 lines

---
Changes in v2:
* sed 's/P2O4x/P204x/'

---
 doc/board/emulation/qemu-ppce500.rst | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)