Baud definitions (B9600 for example) are again encoded; Now supports the BOTHER settings which allows specifying the baud via c_ispeed and c_ospeed termios fields

git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4970 42af7a65-404d-4744-a932-0658087f49c3

1 files changed, 7 insertions, 4 deletions

diff --git a/apps/modbus/README.txt b/apps/modbus/README.txt
index 46b6b2b0e..c7a8ef245 100644
--- a/apps/modbus/README.txt
+++ b/apps/modbus/README.txt
@@ -60,10 +60,6 @@ The NuttX-named configuration options that are available include:
     CONFIG_MB_ASCII_ENABLED - Modbus ASCII support
     CONFIG_MB_RTU_ENABLED - Modbus RTU support
     CONFIG_MB_TCP_ENABLED - Modbus TCP support
-    CONFIG_MB_TERMIOS - Serial driver supports termios.h interfaces (tcsetattr,
-      tcflush, etc.).  If this is not defined, then the terminal settings (baud,
-      parity, etc.) are not configurable at runtime; serial streams will not be
-      flushed when closed.
     CONFIG_MB_ASCII_TIMEOUT_SEC - Character timeout value for Modbus ASCII. The
       character timeout value is not fixed for Modbus ASCII and is therefore
       a configuration option. It should be set to the maximum expected delay
@@ -106,6 +102,13 @@ The NuttX-named configuration options that are available include:
     CONFIG_MB_FUNC_READWRITE_HOLDING_ENABLED - If the Read/Write Multiple
       Registers function should be enabled.
 
+See also other serial settings, in particular:
+
+    CONFIG_SERIAL_TERMIOS - Serial driver supports termios.h interfaces (tcsetattr,
+      tcflush, etc.).  If this is not defined, then the terminal settings (baud,
+      parity, etc.) are not configurable at runtime; serial streams will not be
+      flushed when closed.
+
 Note
 ====