From: Antony Pavlov <antonynpavlov@gmail.com>
To: barebox@lists.infradead.org
Subject: [PATCH 1/3] Documentation: tplink-mr3020: fix 'Could not lex literal_block as "c"' warning
Date: Fri, 12 Aug 2016 17:32:02 +0300 [thread overview]
Message-ID: <1471012324-3881-2-git-send-email-antonynpavlov@gmail.com> (raw)
In-Reply-To: <1471012324-3881-1-git-send-email-antonynpavlov@gmail.com>
The patch fixes these sphinx warnings:
barebox/Documentation/boards/mips/tplink-mr3020.rst:31: WARNING: Could not lex literal_block as "c". Highlighting skipped.
barebox/Documentation/boards/mips/tplink-mr3020.rst:40: WARNING: Could not lex literal_block as "c". Highlighting skipped.
Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com>
---
Documentation/boards/mips/tplink-mr3020.rst | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/Documentation/boards/mips/tplink-mr3020.rst b/Documentation/boards/mips/tplink-mr3020.rst
index 8a95e11..99101c3 100644
--- a/Documentation/boards/mips/tplink-mr3020.rst
+++ b/Documentation/boards/mips/tplink-mr3020.rst
@@ -26,7 +26,9 @@ The ``lzma`` utility can be obtained in Debian/Ubuntu
distro by installing lzma package
(lzma from xz-utils package is unusable).
-The ``mktplinkfw`` utility can be obtained from openwrt, e.g.::
+The ``mktplinkfw`` utility can be obtained from openwrt, e.g.:
+
+.. code-block:: sh
$ OWRTPREF=https://raw.githubusercontent.com/mirrors/openwrt/master
$ curl -OL $OWRTPREF/tools/firmware-utils/src/mktplinkfw.c \
@@ -35,7 +37,9 @@ The ``mktplinkfw`` utility can be obtained from openwrt, e.g.::
$ cc -o mktplinkfw mktplinkfw.c md5.c
To convert your barebox.bin to U-Boot-loadable image (``6F01A8C0.img``)
-use this command sequence::
+use this command sequence:
+
+.. code-block:: sh
$ lzma -c -k barebox-flash-image > barebox.lzma
$ ./mktplinkfw -c -H 0x07200103 -W 1 -N TL-WR720N-v3 \
@@ -47,7 +51,9 @@ Put your ``6F01A8C0.img`` to tftp-server directory
Connect your board to your tftp-server network via Ethernet.
-Next, setup network on MR3020 and run ``6F01A8C0.img``, e.g.::
+Next, setup network on MR3020 and run ``6F01A8C0.img``, e.g.:
+
+.. code-block:: console
hornet> set ipaddr 192.168.0.2
hornet> set serverip 192.168.0.1
--
2.8.1
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-08-12 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 14:32 [PATCH 0/3] Documentation: fix sphinx warnings Antony Pavlov
2016-08-12 14:32 ` Antony Pavlov [this message]
2016-08-12 14:32 ` [PATCH 2/3] Documentation: barebox: fix 'Could not lex literal_block as "c"' warning Antony Pavlov
2016-08-12 14:32 ` [PATCH 3/3] Documentation: variables: fix error in "code-block" directive Antony Pavlov
2016-08-15 9:17 ` [PATCH 0/3] Documentation: fix sphinx warnings Sascha Hauer
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=1471012324-3881-2-git-send-email-antonynpavlov@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox