diff options
author | Gregory Nutt <gnutt@nuttx.org> | 2014-11-16 08:50:36 -0600 |
---|---|---|
committer | Gregory Nutt <gnutt@nuttx.org> | 2014-11-16 08:50:36 -0600 |
commit | 935e3f385d1fc9c4a5db9587ce29580e615d1a46 (patch) | |
tree | cadf335d089f721780eb1794c5c81fb2ceee4552 /nuttx/Documentation/NuttShell.html | |
parent | 0f01a4882771fb5abd708d650bbead4dd2039058 (diff) | |
download | nuttx-935e3f385d1fc9c4a5db9587ce29580e615d1a46.tar.gz nuttx-935e3f385d1fc9c4a5db9587ce29580e615d1a46.tar.bz2 nuttx-935e3f385d1fc9c4a5db9587ce29580e615d1a46.zip |
Clarify MTU/BUFSIZE in apps/ README.txt files and Documentation
Diffstat (limited to 'nuttx/Documentation/NuttShell.html')
-rw-r--r-- | nuttx/Documentation/NuttShell.html | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/nuttx/Documentation/NuttShell.html b/nuttx/Documentation/NuttShell.html index 886ae053c..939e7373c 100644 --- a/nuttx/Documentation/NuttShell.html +++ b/nuttx/Documentation/NuttShell.html @@ -2605,7 +2605,7 @@ nsh> <tr> <td><b><code>get</code></b></td> <td><code>CONFIG_NET</code> && <code>CONFIG_NET_UDP</code> && - <code>CONFIG_NFILE_DESCRIPTORS</code> > 0 && <code>CONFIG_NET_BUFSIZE</code> >= 558<sup>1</sup></td> + <code>CONFIG_NFILE_DESCRIPTORS</code> > 0 && <i>MTU</i> >= 558<sup>1</sup></td> <td><code>CONFIG_NSH_DISABLE_GET</code></td> </tr> <tr> @@ -2711,7 +2711,7 @@ nsh> <tr> <td><b><code>put</code></b></td> <td><code>CONFIG_NET</code> && <code>CONFIG_NET_UDP</code> && - <code>CONFIG_NFILE_DESCRIPTORS</code> > 0 && <code>CONFIG_NET_BUFSIZE</code> >= 558<sup>1,2</sup></td> + <code>CONFIG_NFILE_DESCRIPTORS</code> > 0 && <i>MTU</i> >= 558<sup>1,2</sup></td> <td><code>CONFIG_NSH_DISABLE_PUT</code></td> </tr> <tr> @@ -3254,10 +3254,12 @@ set FOOBAR ABC_${FOO}_${BAR} </td> </tr> <tr> - <td valign="top"><b><code>CONFIG_NET_BUFSIZE=650</code></b> (or larger)</td> + <td valign="top"><b><code>CONFIG_NET_ETH_MTU=650</code></b> (or larger)</td> <td> Per RFC2131 (p. 9), the DHCP client must be prepared to receive DHCP messages of up to 576 bytes (excluding Ethernet, IP, or UDP headers and FCS). + NOTE: Note that the actual MTU setting will depend upon the specific link protocol. + Here Ethernet is indicated. </td> </tr> </table></center> |