From: Tom Rini <trini@konsulko.com>
To: Nishanth Menon <nm@ti.com>
Cc: u-boot@lists.denx.de, Wadim Egorov <w.egorov@phytec.de>,
Francesco Dolcini <francesco@dolcini.it>,
Sjoerd Simons <sjoerd@collabora.com>,
Neha Malcom Francis <n-francis@ti.com>,
Bryan Brattlof <bb@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Marcel Ziswiler <marcel.ziswiler@toradex.com>,
Nikhil Jain <n-jain1@ti.com>
Subject: Re: [PATCH 00/16] doc: board: ti: Cleanup documentation
Date: Thu, 27 Jul 2023 10:08:08 -0400 [thread overview]
Message-ID: <20230727140808.GF3630934@bill-the-cat> (raw)
In-Reply-To: <20230727080027.2817701-1-nm@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]
On Thu, Jul 27, 2023 at 03:00:11AM -0500, Nishanth Menon wrote:
> Hi,
>
> As requested in the thread[1] and irc[2], this series cleansup board/ti
> documentation a bit.
>
> Highlights:
> * Reuse from k3.rst sources and build instructions at the same time
> satisfy needs of users to have a single page documentation on all the
> steps needed to build for a given platform.
> * Replace ascii diagrams with actual svg diagrams (I have used a mix of
> drawio and inkscape to develop these, though inkscape should be
> sufficient to keep it updated). This also allows reuse based on common
> patterns.
> * Convert all pending tables into list-tables
> * Add information for folks who are looking for board information
> incontext of the documentation itself. (ever wondered what board is
> this documentation talking about?)
I'm very happy overall. One small thing is that the boot flow diagrams
on the main K3 page aren't converted (and so don't read well).
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2023-07-27 14:10 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 8:00 [PATCH 00/16] doc: board: ti: Cleanup documentation Nishanth Menon
2023-07-27 8:00 ` [PATCH 01/16] doc: board: ti: Optimize sources references Nishanth Menon
2023-07-27 9:38 ` Neha Malcom Francis
2023-07-27 14:07 ` Tom Rini
2023-07-27 8:00 ` [PATCH 02/16] doc: board: ti: am62x/j7200: Update with common boot flow diagram Nishanth Menon
2023-07-27 9:40 ` Neha Malcom Francis
2023-07-27 10:02 ` Neha Malcom Francis
2023-07-27 10:04 ` Neha Malcom Francis
2023-07-27 13:12 ` Nishanth Menon
2023-07-28 7:31 ` Heinrich Schuchardt
2023-07-28 12:40 ` Nishanth Menon
2023-07-27 14:08 ` Tom Rini
2023-07-27 8:00 ` [PATCH 03/16] doc: board: ti: am65x: Update with " Nishanth Menon
2023-07-27 9:41 ` Neha Malcom Francis
2023-07-27 8:00 ` [PATCH 04/16] doc: board: ti: j721e: " Nishanth Menon
2023-07-27 9:41 ` Neha Malcom Francis
2023-07-27 8:00 ` [PATCH 05/16] doc: board: ti: k3: Reuse build instructions Nishanth Menon
2023-07-27 9:47 ` Neha Malcom Francis
2023-07-27 14:08 ` Tom Rini
2023-07-27 8:00 ` [PATCH 06/16] doc: board: ti: j7200: Convert the image format to svg Nishanth Menon
2023-07-27 9:52 ` Neha Malcom Francis
2023-07-27 13:12 ` Nishanth Menon
2023-07-27 11:25 ` Neha Malcom Francis
2023-07-27 8:00 ` [PATCH 07/16] doc: board: ti: j721e: " Nishanth Menon
2023-07-27 8:00 ` [PATCH 08/16] doc: board: ti: am65x: " Nishanth Menon
2023-07-27 8:00 ` [PATCH 09/16] doc: board: ti: am62x: " Nishanth Menon
2023-07-27 8:00 ` [PATCH 10/16] doc: board: ti: am62x_sk: Convert switch settings to list tables Nishanth Menon
2023-07-27 8:00 ` [PATCH 11/16] doc: board: ti: j7200_evm: " Nishanth Menon
2023-07-27 8:00 ` [PATCH 12/16] doc: board: ti: am65x_evm: Convert the UART boot responsibility to list table Nishanth Menon
2023-07-27 8:00 ` [PATCH 13/16] doc: board: ti: am65/j721e: Convert OSPI memory map to svg Nishanth Menon
2023-07-27 8:00 ` [PATCH 14/16] doc: board: ti: am65x_evm: Convert the emmc layout " Nishanth Menon
2023-07-27 8:00 ` [PATCH 15/16] doc: board: ti: j7200_evm: " Nishanth Menon
2023-07-27 8:00 ` [PATCH 16/16] doc: board: ti: *: Add platform information Nishanth Menon
2023-07-27 13:43 ` [PATCH 00/16] doc: board: ti: Cleanup documentation Nishanth Menon
2023-07-27 14:08 ` Tom Rini [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230727140808.GF3630934@bill-the-cat \
--to=trini@konsulko.com \
--cc=bb@ti.com \
--cc=francesco@dolcini.it \
--cc=marcel.ziswiler@toradex.com \
--cc=n-francis@ti.com \
--cc=n-jain1@ti.com \
--cc=nm@ti.com \
--cc=sjoerd@collabora.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
--cc=w.egorov@phytec.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.