From: yegorslists@googlemail.com
To: linux-can@vger.kernel.org
Cc: mkl@pengutronix.de, netdev@vger.kernel.org,
Yegor Yefremov <yegorslists@googlemail.com>
Subject: [PATCH] can: j1939: convert PGN structure to a table
Date: Thu, 22 Oct 2020 12:29:46 +0200 [thread overview]
Message-ID: <20201022102946.18916-1-yegorslists@googlemail.com> (raw)
From: Yegor Yefremov <yegorslists@googlemail.com>
Use table markup to show the PGN structure.
Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
---
Documentation/networking/j1939.rst | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/Documentation/networking/j1939.rst b/Documentation/networking/j1939.rst
index faf2eb5c5052..f3fb9d880910 100644
--- a/Documentation/networking/j1939.rst
+++ b/Documentation/networking/j1939.rst
@@ -71,10 +71,14 @@ PGN
The PGN (Parameter Group Number) is a number to identify a packet. The PGN
is composed as follows:
-1 bit : Reserved Bit
-1 bit : Data Page
-8 bits : PF (PDU Format)
-8 bits : PS (PDU Specific)
+
+ ============ ============== =============== =================
+ PGN
+ ----------------------------------------------------------------
+ 25 24 23 ... 16 15 ... 8
+ ============ ============== =============== =================
+ R (Reserved) DP (Data Page) PF (PDU Format) PS (PDU Specific)
+ ============ ============== =============== =================
In J1939-21 distinction is made between PDU1 format (where PF < 240) and PDU2
format (where PF >= 240). Furthermore, when using the PDU2 format, the PS-field
--
2.17.0
next reply other threads:[~2020-10-22 10:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 10:29 yegorslists [this message]
2020-10-22 10:33 ` [PATCH] can: j1939: convert PGN structure to a table Marc Kleine-Budde
2020-10-22 12:24 ` Kurt Van Dijck
2020-10-27 11:27 ` Yegor Yefremov
2020-10-27 12:15 ` Marc Kleine-Budde
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=20201022102946.18916-1-yegorslists@googlemail.com \
--to=yegorslists@googlemail.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.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