sergiotarxz/nuttx
sergiotarxz/nuttx
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update some board README files

Browse Source
This commit is contained in:
Gregory Nutt 2017-07-07 09:04:09 -06:00
parent 8d81b35c44
commit 1bddccbc3c
4 changed files with 36 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
configs/dk-tm4c129x/README.txt
View File

@ -757,7 +757,8 @@ Where <subdir> is one of the following:
configuration other than using IPv6. So all of the notes above configuration other than using IPv6. So all of the notes above
regarding the nsh configuration apply. regarding the nsh configuration apply.
Telnet does not work with IPv6. Telnet does work with IPv6 but is not enabled in this
configuration (but could be).
2. This configuration can be modified to that both IPv4 and IPv6 2. This configuration can be modified to that both IPv4 and IPv6
are support. Here is a summary of the additional configuration are support. Here is a summary of the additional configuration
@ -788,9 +789,14 @@ Where <subdir> is one of the following:
ping6 fc00::2 (Linux) ping6 fc00::2 (Linux)
ping -6 fc00::2 (Windows cmd) ping -6 fc00::2 (Windows cmd)
and Telnet again works from the host: and Telnet is now enabled and works from the host... but only using
IPv6 addressing:
telnet 10.0.0.2 telnet fc00::2
That is because the Telnet daemon will default to IPv6 and there is
no Telnet option to let you select which if both IPv4 and IPv6 are
enabled.
3. You can enable IPv6 autonomous address configuration with the 3. You can enable IPv6 autonomous address configuration with the
following changes to the configuration: following changes to the configuration:

12
configs/sama5d4-ek/README.txt
View File

@ -3948,7 +3948,8 @@ Configurations
configuration other than using IPv6. So all of the notes below configuration other than using IPv6. So all of the notes below
regarding the nsh configuration apply. regarding the nsh configuration apply.
Telnet does not work with IPv6. Telnet does work with IPv6 but is not enabled in this
configuration (but could be).
2. This configuration can be modified to that both IPv4 and IPv6 2. This configuration can be modified to that both IPv4 and IPv6
are support. Here is a summary of the additional configuration are support. Here is a summary of the additional configuration
@ -3979,9 +3980,14 @@ Configurations
ping6 fc00::2 (Linux) ping6 fc00::2 (Linux)
ping -6 fc00::2 (Windows cmd) ping -6 fc00::2 (Windows cmd)
and Telnet again works from the host: and Telnet is now enabled and works from the host... but only using
IPv6 addressing:
telent 10.0.0.2 telnet fc00::2
That is because the Telnet daemon will default to IPv6 and there is
no Telnet option to let you select which if both IPv4 and IPv6 are
enabled.
3. You can enable IPv6 autonomous address configuration with the 3. You can enable IPv6 autonomous address configuration with the
following changes to the configuration: following changes to the configuration:

12
configs/stm32f4discovery/README.txt
View File

@ -1349,7 +1349,8 @@ Where <subdir> is one of the following:
configuration other than using IPv6. So all of the notes above configuration other than using IPv6. So all of the notes above
regarding the netnsh configuration apply. regarding the netnsh configuration apply.
a. Telnet does not work with IPv6. a. Telnet does work with IPv6 but is not enabled in this
configuration (but could be).
b. The network initialization thread was enabed in the netnsh b. The network initialization thread was enabed in the netnsh
configuration on 2015-09-28, but not in the ipv6 configuration. configuration on 2015-09-28, but not in the ipv6 configuration.
@ -1382,9 +1383,14 @@ Where <subdir> is one of the following:
ping6 fc00::2 (Linux) ping6 fc00::2 (Linux)
ping -6 fc00::2 (Windows cmd) ping -6 fc00::2 (Windows cmd)
and Telnet again works from the host: and Telnet is now enabled and works from the host... but only using
IPv6 addressing:
telent 10.0.0.2 telnet fc00::2
That is because the Telnet daemon will default to IPv6 and there is
no Telnet option to let you select which if both IPv4 and IPv6 are
enabled.
3. I have used this configuration to serve up IP address prefixes 3. I have used this configuration to serve up IP address prefixes
in a local network with these modifications to the configuration: in a local network with these modifications to the configuration:

12
configs/tm4c1294-launchpad/README.txt
View File

@ -112,7 +112,8 @@ Where <subdir> is one of the following:
configuration other than using IPv6. So all of the notes above configuration other than using IPv6. So all of the notes above
regarding the nsh configuration apply. regarding the nsh configuration apply.
Telnet does not work with IPv6. Telnet does work with IPv6 but is not enabled in this
configuration (but could be).
2. This configuration can be modified to that both IPv4 and IPv6 2. This configuration can be modified to that both IPv4 and IPv6
are support. Here is a summary of the additional configuration are support. Here is a summary of the additional configuration
@ -143,9 +144,14 @@ Where <subdir> is one of the following:
ping6 fc00::2 (Linux) ping6 fc00::2 (Linux)
ping -6 fc00::2 (Windows cmd) ping -6 fc00::2 (Windows cmd)
and Telnet again works from the host: and Telnet is now enabled and works from the host... but only using
IPv6 addressing:
telnet 10.0.0.2 telnet fc00::2
That is because the Telnet daemon will default to IPv6 and there is
no Telnet option to let you select which if both IPv4 and IPv6 are
enabled.
3. You can enable IPv6 autonomous address configuration with the 3. You can enable IPv6 autonomous address configuration with the
following changes to the configuration: following changes to the configuration: