35599f9a66
Recommonmark has been deprecated since 2021 [1] and the last release was
over 3 years ago [2]. As per their announcement, Markedly Structured
Text (MyST) Parser [3] is the recommended replacement.
For the most part, the existing documentation is compatible with MyST,
as both parsers are built around the CommonMark flavor of Markdown. The
main difference that affects coreboot is how the Sphinx toctree is
generated. Recommonmark has a feature called auto_toc_tree, which
converts single level lists of references into a toctree:
* [Part 1: Starting from scratch](part1.md)
* [Part 2: Submitting a patch to coreboot.org](part2.md)
* [Part 3: Writing unit tests](part3.md)
* [Managing local additions](managing_local_additions.md)
* [Flashing firmware](flashing_firmware/index.md)
MyST Parser does not provide a replacement for this feature, meaning the
toctree must be defined manually. This is done using MyST's syntax for
Sphinx directives:
```{toctree}
:maxdepth: 1
Part 1: Starting from scratch <part1.md>
Part 2: Submitting a patch to coreboot.org <part2.md>
Part 3: Writing unit tests <part3.md>
Managing local additions <managing_local_additions.md>
Flashing firmware <flashing_firmware/index.md>
```
Internally, auto_toc_tree essentially converts lists of references into
the Sphinx toctree structure that the MyST syntax above more directly
represents.
The toctrees were converted to the MyST syntax using the following
command and Python script:
`find ./ -iname "*.md" | xargs -n 1 python conv_toctree.py`
```
import re
import sys
in_list = False
f = open(sys.argv[1])
lines = f.readlines()
f.close()
with open(sys.argv[1], "w") as f:
for line in lines:
match = re.match(r"^[-*+] \[(.*)\]\((.*)\)$", line)
if match is not None:
if not in_list:
in_list = True
f.write("```{toctree}\n")
f.write(":maxdepth: 1\n\n")
f.write(match.group(1) + " <" + match.group(2) + ">\n")
else:
if in_list:
f.write("```\n")
f.write(line)
in_list = False
if in_list:
f.write("```\n")
```
While this does add a little more work for creating the toctree, this
does give more control over exactly what goes into the toctree. For
instance, lists of links to external resources currently end up in the
toctree, but we may want to limit it to pages within coreboot.
This change does break rendering and navigation of the documentation in
applications that can render Markdown, such as Okular, Gitiles, or the
GitHub mirror. Assuming the docs are mainly intended to be viewed after
being rendered to doc.coreboot.org, this is probably not an issue in
practice.
Another difference is that MyST natively supports Markdown tables,
whereas with Recommonmark, tables had to be written in embedded rST [4].
However, MyST also supports embedded rST, so the existing tables can be
easily converted as the syntax is nearly identical.
These were converted using
`find ./ -iname "*.md" | xargs -n 1 sed -i "s/eval_rst/{eval-rst}/"`
Makefile.sphinx and conf.py were regenerated from scratch by running
`sphinx-quickstart` using the updated version of Sphinx, which removes a
lot of old commented out boilerplate. Any relevant changes coreboot had
made on top of the previous autogenerated versions of these files were
ported over to the newly generated file.
From some initial testing the generated webpages appear and function
identically to the existing documentation built with Recommonmark.
TEST: `make -C util/docker docker-build-docs` builds the documentation
successfully and the generated output renders properly when viewed in
a web browser.
[1] https://github.com/readthedocs/recommonmark/issues/221
[2] https://pypi.org/project/recommonmark/
[3] https://myst-parser.readthedocs.io/en/latest/
[4] https://doc.coreboot.org/getting_started/writing_documentation.html
Change-Id: I0837c1722fa56d25c9441ea218e943d8f3d9b804
Signed-off-by: Nicholas Chin <nic.c3.14@gmail.com>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/73158
Reviewed-by: Matt DeVillier <matt.devillier@gmail.com>
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
3.0 KiB
coreboot Console
coreboot supports multiple ways to access its console. https://www.coreboot.org/Console_and_outputs
SMBus Console
SMBus is a two-wire interface which is based on the principles of operation of I2C. SMBus, was first was designed to allow a battery to communicate with the charger, the system host, and/or other power-related components in the system.
Enable the SMBus console with CONSOLE_I2C_SMBUS Kconfig. Set
CONSOLE_I2C_SMBUS_SLAVE_ADDRESS and
CONSOLE_I2C_SMBUS_SLAVE_DATA_REGISTER configuration values of the
slave I2C device which you will use to capture I2C packets.
Modern computer Random Access Memory (RAM) slot has SMBus in it according to the JEDEC standards. We can use a breakout-board to expose those SMBus pins. Some mainboard have SMBus pins in the PCIe slot as well.
This feature has been tested on the following platforms:
+------------------------------------+
| Tested platforms |
+====================================+
| GA-H61M-S2PV + Intel Ivy Bridge |
+------------------------------------+
A minimal DDR3 DIMM breakout board PCB design with only the SDA(Data line) and SCL(Clock line) pins of I2C/SMBus can be found here. See the PCB layout here
NOTE: To capture the I2C packets, an I2C slave device is required. The easiest way to capture the log message is to use a I2C to UART converter chip with a UART to USB converter chip. The setup would be as follows.
+---------+ +-------------+ +-------------+
+ PC +----+ UART to USB +----+ I2C to UART |
+---------+ +-------------+ +-------------+
| |
------------------------------------------------+-- System Management
----------------------------------------------+---- Bus
Watch this video to see how it is set up. A backup of the video is available here
If you are using any of the SC16IS740/750/760 I2C to UART converter
chip, you can enable the SC16IS7XX_INIT option to initialize the chip.
If not we can use other I2C slave devices like an Arduino or a Beagleboard.
:maxdepth: 1
Linux I2C Slave interface <https://web.archive.org/web/20220926173943/https://www.kernel.org/doc/html/latest/i2c/slave-interface.html>
BeagleBone Black I2C Slave <https://web.archive.org/web/20220926171211/https://forum.beagleboard.org/t/beaglebone-black-and-arduino-uno-i2c-communication-using-c/29990/8>
This feature was added as part of a GSoC 2022 project. Checkout the following blog posts for more details.
:maxdepth: 1
coreboot Console via SMBus — Part I <https://medium.com/@husnifaiz/coreboot-console-via-smbus-introduction-38273691a8ac>
coreboot Console via SMBus — Part II <https://medium.com/@husnifaiz/coreboot-console-via-smbus-part-ii-bc324fdd2f24>