/openbmc/openbmc/meta-openembedded/meta-oe/recipes-connectivity/transmission/ |
H A D | transmission_4.0.6.bb | 1 DESCRIPTION = "Transmission is a fast, easy, and free BitTorrent client" 11 gitsm://github.com/transmission/transmission;branch=4.0.x;protocol=https \ 12 file://transmission-daemon \ 15 # Transmission release 4.0.6 30 # Weak default values for transmission user and group 37 sed -i '/USERNAME=/c\USERNAME=${TRANSMISSION_USER}' ${UNPACKDIR}/transmission-daemon 39 install -m 0744 ${UNPACKDIR}/transmission-daemon ${D}${sysconfdir}/init.d/ 40 chown ${TRANSMISSION_USER}:${TRANSMISSION_GROUP} ${D}${sysconfdir}/init.d/transmission-daemon 44 sed -i '/User=/c\User=${TRANSMISSION_USER}' ${S}/daemon/transmission-daemon.service 46 install -m 0644 ${S}/daemon/transmission-daemon.service ${D}${systemd_unitdir}/system [all …]
|
/openbmc/linux/drivers/staging/pi433/Documentation/ |
H A D | pi433.txt | 9 (www.pi433.de). It supports transmission and reception. It can be opened 10 by multiple applications for transmission and reception. While transmit 20 a) transmission 22 Each transmission can take place with a different configuration of the rf 24 takes care, that each transmission takes place with the parameterset of the 25 application, that requests the transmission. To allow the transmission to take 33 the air, the rf module is set to standby, the parameters for transmission gets 34 set, the hardware fifo of the rf chip gets preloaded and the transmission gets 38 transmission cycle ends. 48 interrupted by the transmission thread at any time to insert a transmission cycle. [all …]
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-connectivity/transmission/files/ |
H A D | transmission-daemon | 3 # Provides: transmission-daemon 8 # Short-Description: Start the transmission BitTorrent daemon client. 19 # For the default location Transmission uses, visit: 26 # The name of the user that should run Transmission. 27 # It's RECOMENDED to run Transmission in it's own user, 28 # by default, this is set to 'transmission'. 31 USERNAME=transmission 37 # The folder where Transmission stores the config & web files. 39 #TRANSMISSION_HOME="/var/config/transmission-daemon" 40 #TRANSMISSION_WEB_HOME="/usr/share/transmission/web" [all …]
|
/openbmc/linux/Documentation/ABI/stable/ |
H A D | firewire-cdev | 20 - Asynchronous request transmission 28 - Isochronous stream transmission and reception 29 - Asynchronous stream transmission and reception 30 - Asynchronous broadcast request transmission 31 - PHY packet transmission and reception 43 an address range, asynchronous response transmission 55 - PHY packet transmission and reception 87 Allocate a DMA buffer for isochronous reception or transmission 92 for transmission, flags = MAP_SHARED, fd = the handle to the
|
/openbmc/linux/Documentation/admin-guide/media/ |
H A D | si4713.rst | 17 Basically, it has transmission and signal noise level measurement features. 19 The Si4713 integrates transmit functions for FM broadcast stereo transmission. 26 Users must comply with local regulations on radio frequency (RF) transmission. 126 - power_level - Sets the output power level for signal transmission. 132 - rds_ps_name - Sets the RDS ps name field for transmission. 133 - rds_radio_text - Sets the RDS radio text for transmission. 134 - rds_pi - Sets the RDS PI field for transmission. 135 - rds_pty - Sets the RDS PTY field for transmission. 139 - preemphasis - sets the preemphasis to be applied for transmission. 179 transmission. To do that use S/G_MODULATOR ioctl and configure txsubchans properly.
|
/openbmc/linux/drivers/net/wireless/virtual/ |
H A D | mac80211_hwsim.h | 13 * enum hwsim_tx_control_flags - flags to describe transmission info/status 30 * DOC: Frame transmission/registration support 32 * Frame transmission and registration support exists to allow userspace 62 * @HWSIM_CMD_TX_INFO_FRAME: Transmission info report from user space to 119 * @HWSIM_ATTR_FLAGS: mac80211 transmission flags, used to process 233 * @MAC80211_HWSIM_TX_RC_80_MHZ_WIDTH: Indicates 80 MHz transmission 234 * @MAC80211_HWSIM_TX_RC_160_MHZ_WIDTH: Indicates 160 MHz transmission 277 * DOC: Frame transmission support over virtio 279 * Frame transmission is also supported over virtio to allow communication 284 * enum hwsim_vqs - queues for virtio frame transmission [all …]
|
/openbmc/phosphor-logging/extensions/openpower-pels/ |
H A D | user_header.hpp | 163 * @brief Returns the host transmission state 165 * @return uint8_t - the host transmission state 173 * @brief Sets the host transmission state 184 * @brief Returns the HMC transmission state 188 * @return uint8_t - the HMC transmission state 196 * @brief Sets the HMC transmission state 306 * 0xAA = HMC transmission state 307 * 0xBB = Host transmission state
|
/openbmc/linux/Documentation/devicetree/bindings/hsi/ |
H A D | client-devices.txt | 9 - hsi-rx-mode: Receiver Bit transmission mode ("stream" or "frame") 10 - hsi-tx-mode: Transmitter Bit transmission mode ("stream" or "frame") 12 the transmission mode is the same for receiver and 14 - hsi-speed-kbps: Max bit transmission speed in kbit/s
|
/openbmc/linux/Documentation/userspace-api/media/v4l/ |
H A D | ext-ctrls-fm-tx.rst | 12 limiter, RDS transmission and tuning power features. 30 Sets the RDS Programme Identification field for transmission. 33 Sets the RDS Programme Type field for transmission. This encodes up 37 Sets the Programme Service name (PS_NAME) for transmission. It is 49 Sets the Radio Text info for transmission. It is a textual 172 Sets the output power level for signal transmission. Unit is in
|
/openbmc/qemu/include/hw/net/ |
H A D | npcm7xx_emc.h | 91 /* Frame Transmission On */ 146 /* Transmission Halted */ 193 /* Transmission paused */ 195 /* P transmission halted */ 199 /* Transmission abort */ 205 /* Transmission complete */ 207 /* Transmission deferred */
|
/openbmc/linux/include/linux/ |
H A D | mailbox_client.h | 22 * if the client receives some ACK packet for transmission. 26 * before initiating the transmission if required. 27 * @tx_done: Atomic callback to tell client of data transmission
|
/openbmc/linux/drivers/net/ethernet/mellanox/mlx4/ |
H A D | mlx4_stats.h | 102 * transmission of packets 105 /* Number of received transmission from XOFF state to XON state */ 109 /* Total time in microseconds that transmission of packets has been
|
/openbmc/openbmc-test-automation/openpower/pel/ |
H A D | test_bmc_pel.robot | 725 [Documentation] Verify host transmission state of offloaded PEL logs. 727 [Template] Verify PEL Transmission To Host 736 [Documentation] Verify host transmission state of not offloaded PEL logs. 738 [Template] Verify PEL Transmission To Host 875 # [Host Transmission]: Not Sent 929 # [Host Transmission]: Not Sent 938 Verify PEL Transmission To Host 939 [Documentation] Inject PEL log of given type and verify its host transmission state. 945 # expected_transmission_state Expected host transmission state of PEL log. 968 # Check host transmission state for the cases where PEL is [all …]
|
/openbmc/libmctp/docs/bindings/ |
H A D | vendor-ibm-astlpc.md | 26 ### BTU: Baseline Transmission Unit 64 ### MTU: Maximum Transmission Unit 66 The largest payload the link will accept for a packet. The Maximum Transmission 247 #### Negotiation of the Maximum Transmission Unit 250 transmission unit. The Rx and Tx buffers must be sized to accommodate packets up 251 to the Baseline Transmission Unit, and the implementation assumes that the MTU 312 transmission of a packet, or to complete reception of a packet. 324 The BMC sends commands to the host to begin transmission of a packet or to 362 During packet transmission, the follow sequence occurs: 382 The packet transmission sequences assume that `BMC Active` and `Channel Active` [all …]
|
/openbmc/qemu/rust/hw/char/pl011/src/ |
H A D | lib.rs | 65 /// A write to this register initiates the actual data transmission 74 /// A read of this register shows if transmission is complete 93 /// Toggle UART, transmission or reception 169 /// The write operation initiates transmission from the UART. The data is 192 /// transmission or reception, it completes the current character before 362 /// during transmission and reception: 381 /// `UARTTXD` output, after completing transmission of the 461 /// in the middle of transmission or reception, it completes the current 463 /// transmission and reception occurs for either UART signals or SIR 480 /// power, but might reduce transmission distances. [all …]
|
/openbmc/linux/Documentation/sound/cards/ |
H A D | hdspm.rst | 18 Audio transmission 21 * number of channels -- depends on transmission mode 32 (Note: Choosing the 56channel mode for transmission or as 41 transmission/receive-mode , only 28 are transmitted/received 50 transmission/receive-mode , only 14 are transmitted/received 183 MADI-transmission (0).
|
/openbmc/linux/drivers/base/regmap/ |
H A D | regmap-sccb.c | 36 * This executes the 2-phase write transmission cycle that is followed by a 37 * 2-phase read transmission cycle, returning negative errno else zero on 72 * This executes the SCCB 3-phase write transmission cycle, returning negative
|
/openbmc/linux/drivers/net/ethernet/apple/ |
H A D | mace.h | 47 #define DRTRY 0x80 /* don't retry transmission after collision */ 49 #define AUTO_PAD_XMIT 0x01 /* auto-pad short packets on transmission */ 54 #define LCOL 0x20 /* late collision (transmission aborted) */ 58 #define LCAR 0x02 /* loss of carrier (transmission aborted) */ 59 #define RTRY 0x01 /* too many retries (transmission aborted) */
|
/openbmc/libmctp/ |
H A D | libmctp.h | 46 /* Baseline Transmission Unit and packet size */ 137 * and release it when message transmission is complete or fails. 140 * a message is already pending for transmission (msg will be freed as usual). 151 * a message is already pending for transmission. 169 * a message is already pending for transmission (msg will be freed).
|
/openbmc/linux/Documentation/sound/designs/ |
H A D | tracepoints.rst | 30 In a design of ALSA PCM core, data transmission is abstracted as PCM substream. 31 Applications manage PCM substream to maintain data transmission for PCM frames. 32 Before starting the data transmission, applications need to configure PCM 111 a care of hardware design or data transmission protocol.
|
/openbmc/linux/include/linux/phy/ |
H A D | phy-mipi-dphy.h | 54 * state starting the HS transmission. 87 * state after the last payload clock bit of a HS transmission 138 * state starting the HS transmission. 175 * HS transmission burst
|
/openbmc/linux/include/uapi/linux/dvb/ |
H A D | frontend.h | 41 * @FE_CAN_TRANSMISSION_MODE_AUTO: Can auto-detect transmission mode 394 * enum fe_transmit_mode - Transmission mode 397 * Autodetect transmission mode. The hardware will try to find the 400 * Transmission mode 1K 402 * Transmission mode 2K 404 * Transmission mode 8K 406 * Transmission mode 4K 408 * Transmission mode 16K 410 * Transmission mode 32K 412 * Single Carrier (C=1) transmission mode (DTMB only) [all …]
|
/openbmc/linux/drivers/net/wireless/ath/ath5k/ |
H A D | desc.c | 61 * @tx_rate0: HW idx for transmission rate 66 * @rtscts_rate: HW idx for RTS/CTS transmission rate 227 * @tx_rate0: HW idx for transmission rate 232 * @rtscts_rate: HW idx for RTS/CTS transmission rate 365 * @tx_rate1: HW idx for rate used on transmission series 1 366 * @tx_tries1: Max number of retransmissions for transmission series 1 367 * @tx_rate2: HW idx for rate used on transmission series 2 368 * @tx_tries2: Max number of retransmissions for transmission series 2 369 * @tx_rate3: HW idx for rate used on transmission series 3 370 * @tx_tries3: Max number of retransmissions for transmission series 3
|
/openbmc/linux/include/net/iucv/ |
H A D | af_iucv.h | 89 /* transmission of skb is completed and was successful */ 97 /* transmission of skb is pending - may interleave 100 /* transmission of skb was done successfully (delayed) */
|
/openbmc/linux/include/uapi/linux/can/ |
H A D | bcm.h | 78 TX_SETUP = 1, /* create (cyclic) transmission task */ 79 TX_DELETE, /* remove (cyclic) transmission task */ 80 TX_READ, /* read properties of (cyclic) transmission task */
|