michaelh/zephyr
1
0
Fork 0
Code Releases Activity

doc: net: Remove net-app API references

Browse source 
As the net-app API is removed, the documentation links to it
need to be removed.

Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
This commit is contained in:
Jukka Rissanen 2019-02-01 09:04:11 +02:00
commit 941f43588a
5 changed files with 9 additions and 16 deletions
Download patch file Download diff file Expand all files Collapse all files

6
doc/api/networking.rst
View file

@ -180,12 +180,6 @@ IEEE 802.15.4 Management
Network and application libraries
*********************************
Network application
===================
.. doxygengroup:: net_app
:project: Zephyr
DHCPv4
======

4
doc/subsystems/networking/native_posix_setup.rst
View file

@ -6,7 +6,7 @@ Networking with native_posix board
This page describes how to set up a virtual network between a (Linux) host
and a Zephyr application running in a native_posix board.
In this example, the :ref:`echo-server-sample` sample application from
In this example, the :ref:`sockets-echo-server-sample` sample application from
the Zephyr source distribution is run in native_posix board. The Zephyr
native_posix board instance is connected to a Linux host using a tuntap device
which is modeled in Linux as an Ethernet network interface.
@ -62,7 +62,7 @@ Build and start the ``echo_server`` sample application.
In terminal #2, type:
.. zephyr-app-commands::
:zephyr-app: samples/net/echo_server
:zephyr-app: samples/net/sockets/echo_server
:host-os: unix
:board: native_posix
:goals: run

1
doc/subsystems/networking/networking.rst
View file

@ -17,7 +17,6 @@ operation of the stacks and how they were implemented.
secure-sockets.rst
l2-and-drivers.rst
network-management-api.rst
net-app-api.rst
buffers.rst
qemu_setup.rst
native_posix_setup.rst

12
doc/subsystems/networking/qemu_setup.rst
View file

@ -7,7 +7,7 @@ This page describes how to set up a virtual network between a (Linux) host
and a Zephyr application running in a QEMU virtual machine (built for Zephyr
targets such as qemu_x86 and qemu_cortex_m3).
In this example, the :ref:`echo-server-sample` sample application from
In this example, the :ref:`sockets-echo-server-sample` sample application from
the Zephyr source distribution is run in QEMU. The QEMU instance is
connected to a Linux host using a serial port, and SLIP is used to
transfer data between the Zephyr application and Linux (over a chain of
@ -73,7 +73,7 @@ Build and start the ``echo_server`` sample application.
In terminal #1, type:
.. zephyr-app-commands::
:zephyr-app: samples/net/echo_server
:zephyr-app: samples/net/sockets/echo_server
:host-os: unix
:board: qemu_x86
:goals: run
@ -148,10 +148,10 @@ board is connected to a dedicated router, it should not be needed.
To access the internet from a Zephyr application using IPv4,
a gateway should be set via DHCP or configured manually.
For applications using the "Settings" part of :ref:`net_app_api`
facility (with the config option :option:`CONFIG_NET_CONFIG_SETTINGS` enabled),
For applications using the "Settings" facility (with the config option
:option:`CONFIG_NET_CONFIG_SETTINGS` enabled),
set the :option:`CONFIG_NET_CONFIG_MY_IPV4_GW` option to the IP address
of the gateway. For apps not using the :ref:`net_app_api` facility, set up the
of the gateway. For apps not using the "Settings" facility, set up the
gateway by calling the :c:func:`net_if_ipv4_set_gw` at runtime.
To access the internet from a custom application running in QEMU, NAT
@ -198,7 +198,7 @@ Terminal #1:
============
.. zephyr-app-commands::
:zephyr-app: samples/net/echo_server
:zephyr-app: samples/net/sockets/echo_server
:host-os: unix
:board: qemu_x86
:goals: build

2
doc/subsystems/networking/usbnet_setup.rst
View file

@ -8,7 +8,7 @@ and a Zephyr application running on USB supported devices.
The board is connected to Linux host using USB cable
and provides an Ethernet interface to the host.
The :ref:`echo-server-sample` application from the Zephyr source
The :ref:`sockets-echo-server-sample` application from the Zephyr source
distribution is run on supported board. The board is connected to a
Linux host using a USB cable providing an Ethernet interface to the host.