On Fri, 15 May 2020 at 10:05, Philippe Mathieu-Daudé wrote:
> Sphinx consumes docs/system/$arch/$machine.rst files committed to the
> repository, and we don't need to build various qemu-system-arch to
> generate the documentation.
>
> If you work on a particular board, you might end up only
On 5/15/20 10:51 AM, Peter Maydell wrote:
On Fri, 15 May 2020 at 09:03, Philippe Mathieu-Daudé wrote:
However I'd rather see the board documentation in the source code, and
extract it when building. It'd be harder to miss updating the
documentation when modifying the code.
I definitely agree
On Fri, 15 May 2020 at 09:03, Philippe Mathieu-Daudé wrote:
> However I'd rather see the board documentation in the source code, and
> extract it when building. It'd be harder to miss updating the
> documentation when modifying the code.
I definitely agree in principle; but for the moment at
Hi Peter,
+Markus
On 5/14/20 3:28 PM, Peter Maydell wrote:
Ping for review?
For the series:
Reviewed-by: Philippe Mathieu-Daudé
However I'd rather see the board documentation in the source code, and
extract it when building. It'd be harder to miss updating the
documentation when
Ping for review?
thanks
-- PMM
On Thu, 7 May 2020 at 16:18, Peter Maydell wrote:
>
> This patchset adds (minimal) documentation of these Arm board models:
>
> vexpress-a15 ARM Versatile Express for Cortex-A15
> vexpress-a9 ARM Versatile Express for Cortex-A9
> mps2-an385
This patchset adds (minimal) documentation of these Arm board models:
vexpress-a15 ARM Versatile Express for Cortex-A15
vexpress-a9 ARM Versatile Express for Cortex-A9
mps2-an385 ARM MPS2 with AN385 FPGA image for Cortex-M35
mps2-an505 ARM MPS2 with AN505 FPGA
