All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH u-boot] doc: board: qemu-ppce500: Update supported and unsupported
@ 2022-12-20 20:06 Pali Rohár
  2022-12-21  1:15 ` Bin Meng
  2022-12-23 19:15 ` [PATCH v2 " Pali Rohár
  0 siblings, 2 replies; 8+ messages in thread
From: Pali Rohár @ 2022-12-20 20:06 UTC (permalink / raw)
  To: Bin Meng; +Cc: u-boot

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

Signed-off-by: Pali Rohár <pali@kernel.org>
---
 doc/board/emulation/qemu-ppce500.rst | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/doc/board/emulation/qemu-ppce500.rst b/doc/board/emulation/qemu-ppce500.rst
index 5de0aaf55ded..10427cc56302 100644
--- a/doc/board/emulation/qemu-ppce500.rst
+++ b/doc/board/emulation/qemu-ppce500.rst
@@ -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::
-- 
2.20.1


^ permalink raw reply related	[flat|nested] 8+ messages in thread

* Re: [PATCH u-boot] doc: board: qemu-ppce500: Update supported and unsupported
  2022-12-20 20:06 [PATCH u-boot] doc: board: qemu-ppce500: Update supported and unsupported Pali Rohár
@ 2022-12-21  1:15 ` Bin Meng
  2022-12-21  7:49   ` Pali Rohár
  2022-12-23 19:15 ` [PATCH v2 " Pali Rohár
  1 sibling, 1 reply; 8+ messages in thread
From: Bin Meng @ 2022-12-21  1:15 UTC (permalink / raw)
  To: Pali Rohár; +Cc: u-boot

On Wed, Dec 21, 2022 at 4:06 AM Pali Rohár <pali@kernel.org> wrote:
>
> qemu can emulate also e500v1 core but cannot emulate CPUs from Freescale
> PowerPC QorIQ T and P series.
>
> Signed-off-by: Pali Rohár <pali@kernel.org>
> ---
>  doc/board/emulation/qemu-ppce500.rst | 8 +++++---
>  1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/doc/board/emulation/qemu-ppce500.rst b/doc/board/emulation/qemu-ppce500.rst
> index 5de0aaf55ded..10427cc56302 100644
> --- a/doc/board/emulation/qemu-ppce500.rst
> +++ b/doc/board/emulation/qemu-ppce500.rst
> @@ -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)

typo: P2O4x

> +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

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH u-boot] doc: board: qemu-ppce500: Update supported and unsupported
  2022-12-21  1:15 ` Bin Meng
@ 2022-12-21  7:49   ` Pali Rohár
  2022-12-21  9:01     ` Bin Meng
  0 siblings, 1 reply; 8+ messages in thread
From: Pali Rohár @ 2022-12-21  7:49 UTC (permalink / raw)
  To: Bin Meng; +Cc: u-boot

On Wednesday 21 December 2022 09:15:41 Bin Meng wrote:
> On Wed, Dec 21, 2022 at 4:06 AM Pali Rohár <pali@kernel.org> wrote:
> >
> > qemu can emulate also e500v1 core but cannot emulate CPUs from Freescale
> > PowerPC QorIQ T and P series.
> >
> > Signed-off-by: Pali Rohár <pali@kernel.org>
> > ---
> >  doc/board/emulation/qemu-ppce500.rst | 8 +++++---
> >  1 file changed, 5 insertions(+), 3 deletions(-)
> >
> > diff --git a/doc/board/emulation/qemu-ppce500.rst b/doc/board/emulation/qemu-ppce500.rst
> > index 5de0aaf55ded..10427cc56302 100644
> > --- a/doc/board/emulation/qemu-ppce500.rst
> > +++ b/doc/board/emulation/qemu-ppce500.rst
> > @@ -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)
> 
> typo: P2O4x

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

> > +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

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH u-boot] doc: board: qemu-ppce500: Update supported and unsupported
  2022-12-21  7:49   ` Pali Rohár
@ 2022-12-21  9:01     ` Bin Meng
  2022-12-21 22:43       ` Pali Rohár
  0 siblings, 1 reply; 8+ messages in thread
From: Bin Meng @ 2022-12-21  9:01 UTC (permalink / raw)
  To: Pali Rohár; +Cc: u-boot

On Wed, Dec 21, 2022 at 3:49 PM Pali Rohár <pali@kernel.org> wrote:
>
> On Wednesday 21 December 2022 09:15:41 Bin Meng wrote:
> > On Wed, Dec 21, 2022 at 4:06 AM Pali Rohár <pali@kernel.org> wrote:
> > >
> > > qemu can emulate also e500v1 core but cannot emulate CPUs from Freescale
> > > PowerPC QorIQ T and P series.
> > >
> > > Signed-off-by: Pali Rohár <pali@kernel.org>
> > > ---
> > >  doc/board/emulation/qemu-ppce500.rst | 8 +++++---
> > >  1 file changed, 5 insertions(+), 3 deletions(-)
> > >
> > > diff --git a/doc/board/emulation/qemu-ppce500.rst b/doc/board/emulation/qemu-ppce500.rst
> > > index 5de0aaf55ded..10427cc56302 100644
> > > --- a/doc/board/emulation/qemu-ppce500.rst
> > > +++ b/doc/board/emulation/qemu-ppce500.rst
> > > @@ -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)
> >
> > typo: P2O4x
>
> Where is a typo? I wrote P204x (which should mean both P2040 and P2041).

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

>
> > > +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

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH u-boot] doc: board: qemu-ppce500: Update supported and unsupported
  2022-12-21  9:01     ` Bin Meng
@ 2022-12-21 22:43       ` Pali Rohár
  2022-12-22  2:30         ` Bin Meng
  0 siblings, 1 reply; 8+ messages in thread
From: Pali Rohár @ 2022-12-21 22:43 UTC (permalink / raw)
  To: Bin Meng; +Cc: u-boot

On Wednesday 21 December 2022 17:01:37 Bin Meng wrote:
> On Wed, Dec 21, 2022 at 3:49 PM Pali Rohár <pali@kernel.org> wrote:
> >
> > On Wednesday 21 December 2022 09:15:41 Bin Meng wrote:
> > > On Wed, Dec 21, 2022 at 4:06 AM Pali Rohár <pali@kernel.org> wrote:
> > > >
> > > > qemu can emulate also e500v1 core but cannot emulate CPUs from Freescale
> > > > PowerPC QorIQ T and P series.
> > > >
> > > > Signed-off-by: Pali Rohár <pali@kernel.org>
> > > > ---
> > > >  doc/board/emulation/qemu-ppce500.rst | 8 +++++---
> > > >  1 file changed, 5 insertions(+), 3 deletions(-)
> > > >
> > > > diff --git a/doc/board/emulation/qemu-ppce500.rst b/doc/board/emulation/qemu-ppce500.rst
> > > > index 5de0aaf55ded..10427cc56302 100644
> > > > --- a/doc/board/emulation/qemu-ppce500.rst
> > > > +++ b/doc/board/emulation/qemu-ppce500.rst
> > > > @@ -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)
> > >
> > > typo: P2O4x
> >
> > 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?

> >
> > > > +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

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH u-boot] doc: board: qemu-ppce500: Update supported and unsupported
  2022-12-21 22:43       ` Pali Rohár
@ 2022-12-22  2:30         ` Bin Meng
  0 siblings, 0 replies; 8+ messages in thread
From: Bin Meng @ 2022-12-22  2:30 UTC (permalink / raw)
  To: Pali Rohár; +Cc: u-boot

On Thu, Dec 22, 2022 at 6:43 AM Pali Rohár <pali@kernel.org> wrote:
>
> On Wednesday 21 December 2022 17:01:37 Bin Meng wrote:
> > On Wed, Dec 21, 2022 at 3:49 PM Pali Rohár <pali@kernel.org> wrote:
> > >
> > > On Wednesday 21 December 2022 09:15:41 Bin Meng wrote:
> > > > On Wed, Dec 21, 2022 at 4:06 AM Pali Rohár <pali@kernel.org> wrote:
> > > > >
> > > > > qemu can emulate also e500v1 core but cannot emulate CPUs from Freescale
> > > > > PowerPC QorIQ T and P series.
> > > > >
> > > > > Signed-off-by: Pali Rohár <pali@kernel.org>
> > > > > ---
> > > > >  doc/board/emulation/qemu-ppce500.rst | 8 +++++---
> > > > >  1 file changed, 5 insertions(+), 3 deletions(-)
> > > > >
> > > > > diff --git a/doc/board/emulation/qemu-ppce500.rst b/doc/board/emulation/qemu-ppce500.rst
> > > > > index 5de0aaf55ded..10427cc56302 100644
> > > > > --- a/doc/board/emulation/qemu-ppce500.rst
> > > > > +++ b/doc/board/emulation/qemu-ppce500.rst
> > > > > @@ -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)
> > > >
> > > > typo: P2O4x
> > >
> > > 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?
>

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

Regards,
Bin

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [PATCH v2 u-boot] doc: board: qemu-ppce500: Update supported and unsupported
  2022-12-20 20:06 [PATCH u-boot] doc: board: qemu-ppce500: Update supported and unsupported Pali Rohár
  2022-12-21  1:15 ` Bin Meng
@ 2022-12-23 19:15 ` Pali Rohár
  2022-12-24  1:13   ` Bin Meng
  1 sibling, 1 reply; 8+ messages in thread
From: Pali Rohár @ 2022-12-23 19:15 UTC (permalink / raw)
  To: Bin Meng; +Cc: u-boot

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

Signed-off-by: Pali Rohár <pali@kernel.org>

---
Changes in v2:
* sed 's/P2O4x/P204x/'
---
 doc/board/emulation/qemu-ppce500.rst | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/doc/board/emulation/qemu-ppce500.rst b/doc/board/emulation/qemu-ppce500.rst
index 5de0aaf55ded..82b50a01de7e 100644
--- a/doc/board/emulation/qemu-ppce500.rst
+++ b/doc/board/emulation/qemu-ppce500.rst
@@ -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::
-- 
2.20.1


^ permalink raw reply related	[flat|nested] 8+ messages in thread

* Re: [PATCH v2 u-boot] doc: board: qemu-ppce500: Update supported and unsupported
  2022-12-23 19:15 ` [PATCH v2 " Pali Rohár
@ 2022-12-24  1:13   ` Bin Meng
  0 siblings, 0 replies; 8+ messages in thread
From: Bin Meng @ 2022-12-24  1:13 UTC (permalink / raw)
  To: Pali Rohár; +Cc: u-boot

On Sat, Dec 24, 2022 at 3:15 AM Pali Rohár <pali@kernel.org> wrote:
>
> qemu can emulate also e500v1 core but cannot emulate CPUs from Freescale
> PowerPC QorIQ T and P series.
>
> Signed-off-by: Pali Rohár <pali@kernel.org>
>
> ---
> Changes in v2:
> * sed 's/P2O4x/P204x/'
> ---
>  doc/board/emulation/qemu-ppce500.rst | 8 +++++---
>  1 file changed, 5 insertions(+), 3 deletions(-)
>

Reviewed-by: Bin Meng <bmeng.cn@gmail.com>

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2022-12-24  1:13 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-12-20 20:06 [PATCH u-boot] doc: board: qemu-ppce500: Update supported and unsupported Pali Rohár
2022-12-21  1:15 ` Bin Meng
2022-12-21  7:49   ` Pali Rohár
2022-12-21  9:01     ` Bin Meng
2022-12-21 22:43       ` Pali Rohár
2022-12-22  2:30         ` Bin Meng
2022-12-23 19:15 ` [PATCH v2 " Pali Rohár
2022-12-24  1:13   ` Bin Meng

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.