[PATCH u-boot] doc: board: qemu-ppce500: Update supported and unsupported

[Bin Meng]

On Thu, Dec 22, 2022 at 6:43 AM Pali Rohár <pali at 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 at 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 at 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 at 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