| /linux/drivers/tty/ipwireless/ |
| H A D | network.c | 69 struct ipw_network *network = callback_data; in notify_packet_sent() local
72 spin_lock_irqsave(&network->lock, flags); in notify_packet_sent()
73 network->outgoing_packets_queued--; in notify_packet_sent()
74 if (network->ppp_channel != NULL) { in notify_packet_sent()
75 if (network->ppp_blocked) { in notify_packet_sent()
76 network->ppp_blocked = 0; in notify_packet_sent()
77 spin_unlock_irqrestore(&network->lock, flags); in notify_packet_sent()
78 ppp_output_wakeup(network->ppp_channel); in notify_packet_sent()
83 spin_unlock_irqrestore(&network->lock, flags); in notify_packet_sent()
85 spin_unlock_irqrestore(&network->lock, flags); in notify_packet_sent()
[all …]
|
| H A D | tty.c | 53 struct ipw_network *network; member
105 ipwireless_ppp_open(tty->network); in ipw_open()
124 ipwireless_ppp_close(tty->network); in do_ipw_close()
399 tty->network); in ipw_ioctl()
411 tty->network); in ipw_ioctl()
437 struct ipw_network *network, int channel_idx, in add_tty() argument
447 ttys[j]->network = network; in add_tty()
453 ipwireless_associate_network_tty(network, channel_idx, ttys[j]); in add_tty()
456 ipwireless_associate_network_tty(network, in add_tty()
469 struct ipw_network *network) in ipwireless_tty_create() argument
[all …]
|
| /linux/drivers/net/wireless/intel/ipw2x00/ |
| H A D | libipw_wx.c | 44 struct libipw_network *network, in libipw_translate_scan() argument
57 memcpy(iwe.u.ap_addr.sa_data, network->bssid, ETH_ALEN); in libipw_translate_scan()
65 iwe.u.data.length = min(network->ssid_len, (u8) 32); in libipw_translate_scan()
67 &iwe, network->ssid); in libipw_translate_scan()
72 libipw_modes[network->mode]); in libipw_translate_scan()
77 if (network->capability & (WLAN_CAPABILITY_ESS | WLAN_CAPABILITY_IBSS)) { in libipw_translate_scan()
78 if (network->capability & WLAN_CAPABILITY_ESS) in libipw_translate_scan()
90 iwe.u.freq.m = libipw_channel_to_freq(ieee, network->channel); in libipw_translate_scan()
97 if (network->capability & WLAN_CAPABILITY_PRIVACY) in libipw_translate_scan()
103 &iwe, network->ssid); in libipw_translate_scan()
[all …]
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-led-trigger-netdev | 6 Specifies the network device name to monitor.
26 Signal the link state of the named network device.
31 of the named network device.
40 Signal transmission of data on the named network device.
55 Signal reception of data on the named network device.
83 Signal the link speed state of 10Mbps of the named network device.
88 speed of 10MBps of the named network device.
91 Present only if the named network device supports 10Mbps link speed.
98 Signal the link speed state of 100Mbps of the named network device.
103 speed of 100Mbps of the named network device.
[all …]
|
| H A D | sysfs-class-net-statistics | 6 Indicates the number of collisions seen by this network device.
15 network device.
22 Indicates the number of bytes received by this network device.
23 See the network driver for the exact meaning of when this
32 network device. This value might only be relevant for interfaces
41 by this network device. Note that the specific meaning might
49 Indicates the number of packets received by the network device
51 packet processing. See the network driver for the exact
59 Indicates the number of receive errors on this network device.
60 See the network driver for the exact meaning of this value.
[all …]
|
| H A D | sysfs-class-net-queues | 8 network device queue. Possible values depend on the number
17 processed by this particular network device receive queue.
25 network interface transmit queue.
42 network device transmit queue. Possible values depend on the
52 network device transmit queue. Possible values depend on the
53 number of available receive queue(s) in the network device.
62 of this particular network device transmit queue.
71 network device transmit queue.
79 on this network device transmit queue. This value is clamped
88 queued on this network device transmit queue. See
[all …]
|
| H A D | sysfs-class-net-qmi | 8 Set this to 'Y' to change the network device link
33 based network device, supported by recent Qualcomm based
36 The network device will be called qmimux.
38 Userspace is in charge of managing the qmux network device
50 created qmap mux based network device.
59 Indicates the mux id associated to the qmimux network interface
|
| /linux/drivers/net/wireless/realtek/rtlwifi/ |
| H A D | Kconfig | 22 wireless network adapters.
33 wireless network adapters.
45 wireless network adapters.
58 wireless network adapters.
71 wireless network adapters.
82 wireless network adapters.
94 wireless network adapters.
106 wireless network adapters.
118 wireless network adapters.
130 wireless network adapters.
|
| /linux/drivers/net/hippi/ |
| H A D | Kconfig | 3 # HIPPI network device configuration
11 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
14 connect to super computers. If you are connected to a HIPPI network
15 and have a HIPPI network card in your computer that you want to use
25 Say Y here if this is your PCI HIPPI network card.
|
| /linux/Documentation/networking/ |
| H A D | gtp.rst | 19 and the interconnection between an external packet data network (such
24 such a tunnel between that external data network and the phone. The
32 At some network element inside the cellular operator infrastructure
40 and forwards it onto an external packet data network. This can be
41 public internet, but can also be any private IP network (or even
42 theoretically some non-IP network like X.25).
56 packet network in downlink towards the phone.
205 The GTP-U driver creates a Linux network device for each Gi/SGi
223 2. each private network manages its own addressing. In general this
227 and each private network.
[all …]
|
| H A D | bridge.rst | 12 standard, is a device that connects two or more network segments and operates
56 bridge context, STP is crucial for network stability and availability.
76 network topology.
90 is a designated switch in a bridged network that serves as a reference point
100 in the network. The Bridge ID is used to compare the priorities of
102 3. Bridge Election: When the network starts, all bridges initially assume
112 network. This information is used by other bridges to calculate the
126 it to actively forward network traffic.
131 Blocking state to prevent network loops.
133 STP ensures network convergence by calculating the shortest path and disabling
[all …]
|
| H A D | tuntap.rst | 28 corresponding ioctl() to register a network device with the kernel. A network
30 the program closes the file descriptor, the network device and all
39 two network interfaces.
57 since CAP_NET_ADMIN is required for creating network devices or for
58 connecting to network devices which aren't owned by the user in question.
86 "tun%d"), but (as far as I can see) this can be any valid network device name.
229 3. How does Virtual network device actually work ?
231 Virtual network device can be viewed as a simple Point-to-Point or
253 network interface. It does not provide a virtual network interface.
254 A TUN/TAP driver does provide a virtual network interface and it is possible
|
| /linux/net/x25/ |
| H A D | Kconfig | 9 X.25 is a set of standardized network protocols, similar in scope to
10 frame relay; the one physical line from your box to the X.25 network
13 network. Governments, banks, and other organizations tend to use it
24 One connects to an X.25 network either with a dedicated network card
|
| /linux/drivers/net/fddi/ |
| H A D | Kconfig | 3 # FDDI network device configuration
10 Fiber Distributed Data Interface is a high speed local area network
12 run over copper or fiber. If you are connected to such a network and
24 and 700-C (DEFZA-CA, copper) TURBOchannel network cards which
25 can connect you to a local FDDI network.
36 to a local FDDI network.
|
| /linux/arch/um/drivers/ |
| H A D | Kconfig | 129 bool "Virtual network device"
133 provide one or more virtual network devices through which the UML
150 The Ethertap User-Mode Linux network transport allows a single
155 Ethernet network, it's in fact communicating over a point-to-point
176 The UML TUN/TAP network transport allows a UML instance to exchange
193 The slip User-Mode Linux network transport allows a running UML to
194 network with its host over a point-to-point link. Unlike Ethertap,
214 This User-Mode Linux network transport allows one or more running
240 bool "Vector I/O high performance network devices"
244 This User-Mode Linux network driver uses multi-message send
[all …]
|
| /linux/drivers/net/ethernet/sun/ |
| H A D | Kconfig | 3 # Sun network device configuration
11 If you have a network (Ethernet) card belonging to this class, say Y.
15 the questions about Sun network interfaces. If you say Y, you will be
85 Support for virtual network devices under Sun Logical Domains.
94 This driver adds a network interface for every vsw-port node
97 guest domain network interconnectivity or guest domain
98 connection to a physical network on a service domain.
|
| /linux/Documentation/networking/device_drivers/wwan/ |
| H A D | iosm.rst | 30 - configure network connection settings
31 - connect to network
32 - configure IP network interface
67 wwan0-X network device
70 traffic. Iproute network utility is used for creating "wwan0-X" network
81 The driver will automatically map the "wwan0-1" network device to MBIM IP
|
| /linux/drivers/net/ethernet/marvell/ |
| H A D | Kconfig | 11 If you have a network (Ethernet) card belonging to this class, say Y.
40 This driver supports the MDIO interface found in the network
47 tristate "Marvell Armada 38x/XP network interface BM support"
51 This driver supports auxiliary block of the network
56 driver and is common for all network ports of the devices,
61 tristate "Marvell Armada 370/38x/XP/37xx network interface support"
68 This driver supports the network interface units in the
88 tristate "Marvell Armada 375/7K/8K network interface support"
94 This driver supports the network interface units in the
122 It does not support the link failover and network management
|
| /linux/drivers/net/wwan/ |
| H A D | Kconfig | 53 tristate "MHI WWAN MBIM network driver for QCOM-based PCIe modems"
56 MHI WWAN MBIM is a WWAN network driver for QCOM-based PCIe modems.
58 A default wwan0 network interface is created for MBIM data session
65 tristate "Qualcomm BAM-DMUX WWAN network driver"
68 The BAM Data Multiplexer provides access to the network data channels
72 (CONFIG_RPMSG_WWAN_CTRL) or QRTR network sockets (CONFIG_QRTR).
90 QRTR network sockets (CONFIG_QRTR).
114 Adapts WWAN framework and provides network interface like wwan0
|
| /linux/Documentation/userspace-api/media/dvb/ |
| H A D | net.rst | 10 of a transport stream to be mapped into a virtual network interface,
11 visible through the standard Linux network protocol stack.
19 In order to create the Linux virtual network interfaces, an application
23 virtual ``dvb?_?`` network interfaces, and will be controlled/routed via
|
| /linux/drivers/net/ethernet/vertexcom/ |
| H A D | Kconfig | 3 # Vertexcom network device configuration
10 If you have a network (Ethernet) card belonging to this class, say Y.
23 SPI driver for Vertexcom MSE102x SPI attached network chip.
|
| /linux/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
| H A D | overview.rst | 16 DPAA2 is a hardware architecture designed for high-speeed network
26 network ports to create functional objects/devices such as network
58 | -network interface -DPNI |
78 in creating a network interfaces.
140 Ethernet network interface functionality. This approach provides
145 network interface configuration on a system with 2 CPUs.
187 Contains TX/RX queues, network interface configuration, and RX buffer pool
254 A network interface requires a 'buffer pool' (DPBP
258 the network interface.
359 - DPMCPs to send MC commands, to configure network interfaces
[all …]
|
| H A D | ethernet-driver.rst | 21 representing network interfaces; instead, several separate hardware resources
24 - network interfaces
68 The DPNIs are network interfaces without a direct one-on-one mapping to PHYs.
119 Each network interface can have multiple Rx, Tx and confirmation queues affined
124 The role of hardware buffer pools is storage of ingress frame data. Each network
158 a number of properties which determine the network interface configuration
161 DPNI objects (and the other DPAA2 objects needed for a network interface) can be
185 Hardware specific statistics for the network interface as well as some
|
| /linux/arch/powerpc/boot/dts/ |
| H A D | mpc885ads.dts | 97 device_type = "network";
105 linux,network-index = <0>;
109 device_type = "network";
117 linux,network-index = <1>;
200 device_type = "network";
209 linux,network-index = <2>;
|
| /linux/net/batman-adv/ |
| H A D | Kconfig | 30 network, as well as a throughput based metric.
53 mesh networks. If you think that your network does not need
60 This option enables network coding, a mechanism that aims to
61 increase the overall network throughput by fusing multiple
65 network coding work.
66 If you think that your network does not need this feature you
|