| /Zephyr-Core-3.4.0/samples/subsys/ipc/openamp_rsc_table/ |
| D | README.rst | 12 * `Linux rpmsg client sample <https://elixir.bootlin.com/linux/latest/source/samples/rpmsg/rpmsg_cl…
13 * `Linux rpmsg tty driver <https://elixir.bootlin.com/linux/latest/source/drivers/tty/rpmsg_tty.c>`_
16 a Linux kernel OS on the main processor and a Zephyr application on
29 Linux subsection
51 Linux console
54 Open a Linux shell (minicom, ssh, etc.) and insert a module into the Linux Kernel
79 rpmsg TTY demo on Linux console
82 On the Linux console send a message to Zephyr which answers with the "TTY <add>" prefix.
|
| /Zephyr-Core-3.4.0/samples/net/wpanusb/ |
| D | README.rst | 10 other OSes such as Linux. For Linux, the ieee802154 stack would be
11 implemented using the Linux SoftMAC driver.
20 connected via USB to a Linux host
21 - wpanusb Linux kernel driver (in the process of being open sourced)
22 - wpan-tools (available for all Linux distributions)
54 When connected to Linux with wpanusb kernel driver, it is recognized as:
66 The following script enables the network interface in Linux
|
| D | wpan-radio-spec.txt | 6 The document describes protocol between 802.15.4 physical radio and Linux
7 kernel driver over USB. Protocol is based on atusb Linux driver protocol
8 found inside Linux kernel: drivers/net/ieee802154/atusb.h
|
| /Zephyr-Core-3.4.0/doc/connectivity/networking/ |
| D | usbnet_setup.rst | 10 This page describes how to set up networking between a Linux host
13 The board is connected to Linux host using USB cable
17 Linux host using a USB cable providing an Ethernet interface to the host.
24 the Linux host.
25 After plugging a USB cable from the board to the Linux host, the
30 running dmesg from the Linux host.
43 for the interface on the Linux host.
70 Next step is to assign IP addresses to the new Linux host interface, in
72 Linux system.
|
| /Zephyr-Core-3.4.0/dts/bindings/can/ |
| D | zephyr,native-posix-linux-can.yaml | 4 description: Zephyr CAN driver using Linux SocketCAN
6 compatible: "zephyr,native-posix-linux-can"
14 description: Linux host interface name (e.g. zcan0, vcan0, can0, ...)
|
| /Zephyr-Core-3.4.0/samples/net/vlan/ |
| D | README.rst | 25 file when running *net-setup.sh* script in Linux like this:
49 Setting up Linux Host
52 The :zephyr_file:`samples/net/vlan/vlan-setup-linux.sh` provides a script that
53 can be executed on the Linux host. It creates two VLAN interfaces *vlan.100*
54 and *vlan.200* on the Linux host and creates routes to Zephyr.
57 the following commands on the Linux host.
|
| /Zephyr-Core-3.4.0/drivers/can/ |
| D | Kconfig.native_posix_linux | 1 # Native Linux SocketCAN configuration options
7 bool "Native Linux SocketCAN Driver"
11 Enable native Linux SocketCAN Driver
|
| D | can_native_posix_linux_socketcan.c | 22 /* Linux host include files. */
30 #include <linux/can.h>
31 #include <linux/can/raw.h>
33 #error "This driver can only be built on Linux systems"
39 /* Linux kernels before v5.14 do not define CANFD_FDF */
133 /* Make sure to set the flags for all frames received via the Linux API. in linux_socketcan_read_data()
136 * frames. In Linux the flags field is undefined for legacy frames. in linux_socketcan_read_data()
|
| /Zephyr-Core-3.4.0/samples/net/lldp/ |
| D | README.rst | 37 Setting up Linux Host
41 :zephyr_file:`samples/net/vlan/vlan-setup-linux.sh` provides a script that can be
42 executed on the Linux host. It creates two VLANs on the Linux host and creates
|
| /Zephyr-Core-3.4.0/samples/drivers/ethernet/eth_ivshmem/ |
| D | README.rst | 13 Building Jailhouse Linux for QEMU
45 This should boot Linux and drop into a shell.
58 Copy the generated zephyr.bin to the Jailhouse Linux root cell:
67 Back in Jailhouse Linux shell, create the Zephyr cell:
75 You may see a quirk here where the Linux shell stops taking input...
89 Now you can run Zephyr and Linux shell commands to communicate between
92 Ping Linux from Zephyr
104 Ping Zephyr from Linux
131 In Linux:
154 Linux output:
|
| /Zephyr-Core-3.4.0/doc/develop/getting_started/ |
| D | installation_linux.rst | 3 Install Linux Host Dependencies
6 Documentation is available for these Linux distributions:
10 * Clear Linux
11 * Arch Linux
45 .. group-tab:: Clear Linux
51 .. group-tab:: Arch Linux
93 .. group-tab:: Clear Linux
100 The Clear Linux focus is on *native* performance and security and not
112 system*. Each Linux distribution has a unique, relatively complex and
114 other and Clear Linux is no exception. If you need a more flexible
[all …]
|
| D | installation_win.rst | 8 Windows 10 WSL (Windows Subsystem for Linux)
21 #. `Install the Windows Subsystem for Linux (WSL)`_.
35 .. _Install the Windows Subsystem for Linux (WSL): https://msdn.microsoft.com/en-us/commandline/wsl… argument
|
| /Zephyr-Core-3.4.0/samples/subsys/usb/testusb/ |
| D | README.rst | 7 to test USB device drivers and the device stack connected to a Linux host
8 and has a similar interface to "Gadget Zero" of the Linux kernel.
21 #. Load the ``usbtest`` Linux kernel module on the Linux Host.
41 #. Use the ``testusb`` tool in ``linux/tools/usb`` inside Linux kernel source directory
62 #. Use the ``testusb`` tool in ``linux/tools/usb`` inside Linux kernel source directory
|
| /Zephyr-Core-3.4.0/doc/develop/toolchains/ |
| D | designware_arc_mwdt.rst | 15 :envvar:`ARCMWDT_TOOLCHAIN_PATH` to ``$METAWARE_ROOT/../`` (Linux)
24 * objcopy binaries: ``arc-elf32-objcopy`` or ``arc-linux-objcopy`` or ``objcopy``
25 * gcc binaries: ``arc-elf32-gcc`` or ``arc-linux-gcc`` or ``gcc``
35 # Linux:
|
| D | other_x_compilers.rst | 6 This toolchain variant is borrowed from the Linux kernel build system's
10 Examples of such "other cross compilers" are cross toolchains that your Linux
22 Debian-based Linux systems, or ``arm-none-eabi-newlib`` on Fedora or Red
45 # Linux, macOS:
|
| /Zephyr-Core-3.4.0/doc/ |
| D | LICENSING.rst | 17 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/COPYING
20 *Origin:* Linux Kernel
|
| /Zephyr-Core-3.4.0/samples/net/sockets/echo_client/ |
| D | README.rst | 119 same host as the echo-server in Linux host.
149 Running echo-server in Linux Host
152 There is one useful testing scenario that can be used with Linux host.
153 Here echo-client is run in QEMU and echo-server is run in Linux host.
169 :conf: "prj.conf overlay-linux.conf"
173 Note that echo-server must be running in the Linux host terminal window
177 You can verify TLS communication with a Linux host as well. See
179 on how to test TLS with Linux host samples.
182 way of running, with the echo-client on the Linux host and the echo-server
|
| /Zephyr-Core-3.4.0/include/zephyr/net/ |
| D | socketcan.h | 42 /* SocketCAN MTU size compatible with Linux */
52 /* CAN-FD specific flags from Linux Kernel (include/uapi/linux/can.h) */
67 * @name Linux SocketCAN compatibility
70 * frame and CAN filter formats used by Linux SocketCAN.
76 * CAN Identifier structure for Linux SocketCAN compatibility.
99 * @brief CAN frame for Linux SocketCAN compatibility.
118 * @brief CAN filter for Linux SocketCAN compatibility.
|
| /Zephyr-Core-3.4.0/samples/net/ipv4_autoconf/ |
| D | README.rst | 24 connect to a Linux host.
26 Connect ethernet cable from a :ref:`Freedom-K64F board <frdm_k64f>` to a Linux
29 Running Avahi client in Linux Host
32 Assign a IPv4 link local address to the interface in the Linux system
|
| /Zephyr-Core-3.4.0/samples/net/sockets/big_http_download/ |
| D | Makefile.posix | 1 # This makefile builds the sample for a POSIX system, like Linux
3 # libmbedtls-dev package on Debian/Ubuntu Linux.
|
| /Zephyr-Core-3.4.0/samples/net/dhcpv4_client/ |
| D | README.rst | 21 Running DHCPv4 client in Linux Host
25 QEMU on a Linux host to negotiate IP address from DHCPv4 server running
26 on Linux host.
43 Use another terminal window to start up a DHCPv4 server on the Linux host,
84 Linux host.
86 Connect ethernet cable from :ref:`Freedom-K64F board <frdm_k64f>` to Linux host
113 Use another terminal window to start up a DHCPv4 server on the Linux host,
|
| /Zephyr-Core-3.4.0/samples/net/sockets/echo_server/ |
| D | README.rst | 116 Running echo-client in Linux Host
119 There is one useful testing scenario that can be used with Linux host.
120 Here echo-server is run in QEMU and echo-client is run in Linux host.
142 You can verify TLS communication with a Linux host as well. See
144 on how to test TLS with Linux host samples.
147 way of running, with the echo-server on the Linux host and the echo-client
|
| /Zephyr-Core-3.4.0/boards/posix/native_posix/ |
| D | Kconfig.board | 8 Will produce a console Linux process which can be executed natively
20 Will produce a console Linux process which can be executed natively
|
| /Zephyr-Core-3.4.0/lib/open-amp/ |
| D | resource_table.h | 20 #define VRING0_ID 0 /* (master to remote) fixed to 0 for Linux compatibility */
21 #define VRING1_ID 1 /* (remote to master) fixed to 1 for Linux compatibility */
29 #define VRING_ALIGNMENT 16 /* fixed to match with Linux constraint */
|
| /Zephyr-Core-3.4.0/include/zephyr/dt-bindings/gpio/ |
| D | numicro-gpio.h | 13 * specified by the Linux GPIO binding. Only applicable for Nuvoton NuMicro SoCs.
21 * specified by the Linux GPIO binding. Only applicable for Nuvoton NuMicro SoCs.
|
