| /openbmc/docs/designs/mctp/ |
| H A D | mctp.md | 61 packets by the transmit implementation, and reassembled at the receive
|
| /openbmc/linux/Documentation/userspace-api/media/rc/ |
| H A D | lirc-dev-intro.rst | 36 - ir-ctl: can receive raw IR and transmit IR, as well as query LIRC
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/3com/ |
| H A D | vortex.rst | 191 transmit packets in a single invocation. It does this in a loop.
202 allows you to make use of the NIC's DMA scatter/gather and transmit
|
| /openbmc/linux/Documentation/networking/ |
| H A D | checksum-offloads.rst | 29 The interface for offloading a transmit checksum to a device is explained in
|
| H A D | can_ucan_protocol.rst | 51 ``wLength`` * Host to Device - Number of bytes to transmit
|
| H A D | phy.rst | 87 for the transmit data lines (TXD[3:0]) processed by the PHY device
93 both transmit AND receive data lines from/to the PHY device
112 configured correctly in order to provide the required transmit and/or receive
|
| H A D | tls.rst | 30 the transmit and the receive into the kernel.
|
| H A D | rxrpc.rst | 828 tx_total_len is the amount of data the caller is intending to transmit
886 other than MSG_MORE. len is the total amount of data to transmit.
1023 (#) Set the total transmit data size on a call::
1029 This sets the amount of data that the caller is intending to transmit on a
1130 transmit it again, assuming no ACK is received from the receiver telling
|
| /openbmc/linux/Documentation/devicetree/bindings/soc/ti/ |
| H A D | keystone-navigator-qmss.txt | 54 transmit DMA queues.
|
| /openbmc/u-boot/doc/device-tree-bindings/net/ |
| H A D | snps,dwc-qos-ethernet.txt | 25 The EQOS transmit path clock. The HW signal name is clk_tx_i.
|
| /openbmc/linux/Documentation/devicetree/bindings/net/ |
| H A D | snps,dwc-qos-ethernet.txt | 28 The EQOS transmit path clock. The HW signal name is clk_tx_i.
|
| H A D | micrel-ksz90x1.txt | 224 was missing extended register 106 (transmit data pad skews), and
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-net-statistics | 187 Indicates the number of packets having caused a transmit
|
| /openbmc/linux/Documentation/driver-api/soundwire/ |
| H A D | summary.rst | 30 transmit or receiving mode (typically fixed direction but configurable
|
| /openbmc/u-boot/doc/ |
| H A D | README.drivers.eth | 137 The send function does what you think -- transmit the specified packet whose
|
| /openbmc/linux/Documentation/networking/device_drivers/hamradio/ |
| H A D | baycom.rst | 79 starts to send as soon as there's a packet to transmit and does not care
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | OGDL-Taiwan-1.0 | 95 …able, royalty-free copyright license to reproduce, distribute, publicly transmit, publicly broadca…
|
| H A D | IPA | 44 …d Program as is without modification and transfer such copies, publicly transmit or otherwise redi…
|
| /openbmc/linux/Documentation/fb/ |
| H A D | udlfb.rst | 127 do not transmit. Spends host memory to save USB transfers.
|
| /openbmc/linux/Documentation/admin-guide/sysctl/ |
| H A D | net.rst | 232 packet contents. If disabled, transmit timestamp requests from unprivileged
466 the remote address, the size of the transmit pending queue, the size of the
|
| /openbmc/linux/drivers/net/ppp/ |
| H A D | ppp_generic.c | 962 compat_int_t transmit; member
1011 .transmit = data32.transmit in ppp_compat_ioctl()
3040 if (data->transmit) { in ppp_set_compress()
|
| /openbmc/linux/Documentation/i2c/ |
| H A D | slave-interface.rst | 93 should transmit the first byte.
|
| /openbmc/linux/drivers/net/team/ |
| H A D | team_mode_loadbalance.c | 673 .transmit = lb_transmit,
|
| /openbmc/linux/drivers/staging/pi433/ |
| H A D | rf69.c | 75 [transmit] = OPMODE_MODE_TRANSMIT, in rf69_set_mode()
|
| /openbmc/linux/Documentation/networking/dsa/ |
| H A D | dsa.rst | 298 invoke a specific transmit routine which takes care of adding the relevant
389 the tagging protocol supported by the switch tree, and which receive/transmit
426 will not make us go through the switch tagging protocol transmit function, so
917 driver and tag protocol combinations to transmit a single skb coming from the
918 bridge device's transmit function to potentially multiple egress ports (and
926 handled in hardware and the bridge driver will transmit a single skb for each
|