From b0e7e7ba6dfc727dacd165f616490d8b3963c91b Mon Sep 17 00:00:00 2001
From: Eric Kooistra <kooistra@astron.nl>
Date: Mon, 1 Mar 2021 09:46:22 +0100
Subject: [PATCH] Clarified byte / word addressing.

---
 args_next_steps.txt | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/args_next_steps.txt b/args_next_steps.txt
index df15e6a..156e3eb 100755
--- a/args_next_steps.txt
+++ b/args_next_steps.txt
@@ -107,11 +107,11 @@ The number of bytes per address and the data size can differ at the interfaces:
 
   master -- MM bus -- slave -- user
 
-The yaml files use byte addressing. Internally ARGS also use byte addressing. However only
-word addressing is supported, so the byte addresses are always a multiple of 4. This is checked
-when ARGS reads in the yaml files. For output files it depends on the application whether the
-output file assumes byte addressing or word addressing.
-
+  . The input yaml files use byte addressing.
+  . Internally ARGS also use byte addressing. However only word addressing is supported, so the
+    byte addresses are always a multiple of 4. This is checked when ARGS reads in the yaml files.
+  . For output files it depends on the application whether the output file assumes byte addressing
+    or word addressing.
 
 Master + MM bus :
   . fixed 32b data (MM word) addresses, so byte address increment 4 per 32b word
-- 
GitLab