Searched refs:SCP (Results 1 – 25 of 65) sorted by relevance
123
23 export SCP # used in scp-ssh-wrapper.scp33 $SCP $scpopts ${DATA} ${COPY} || fail "copy failed"38 $SCP $scpopts ${DATA} somehost:${COPY} || fail "copy failed"43 $SCP $scpopts somehost:${DATA} ${COPY} || fail "copy failed"49 $SCP $scpopts ${COPY} somehost:${DIR} || fail "copy failed"55 $SCP $scpopts ${COPY} ${DIR} || fail "copy failed"61 $SCP $scpopts somehost:${COPY} ${DIR} || fail "copy failed"68 $SCP $scpopts -r ${DIR} somehost:${DIR2} || fail "copy failed"75 $SCP $scpopts -r ${DIR} ${DIR2} || fail "copy failed"82 $SCP $scpopts -r somehost:${DIR} ${DIR2} || fail "copy failed"[all …]
16 export SCP # used in scp-ssh-wrapper.scp29 $SCP $scpopts ${DATA} "scp://${USER}@somehost:${PORT}/${COPY}" || fail "copy failed"34 $SCP $scpopts "scp://${USER}@somehost:${PORT}/${DATA}" ${COPY} || fail "copy failed"40 $SCP $scpopts ${COPY} "scp://${USER}@somehost:${PORT}/${DIR}" || fail "copy failed"46 $SCP $scpopts "scp://${USER}@somehost:${PORT}/${COPY}" ${DIR} || fail "copy failed"53 $SCP $scpopts -r ${DIR} "scp://${USER}@somehost:${PORT}/${DIR2}" || fail "copy failed"62 $SCP $scpopts -r "scp://${USER}@somehost:${PORT}/${DIR}" ${DIR2} || fail "copy failed"
83 SCP=scp121 SCP="${TEST_SSH_SCP}"171 SCP_BIN=${SCP}215 SCP="$VG --log-file=${VG_LOG}scp.%p $SCP"274 export SSH SSHD SSHAGENT SSHADD SSHKEYGEN SSHKEYSCAN SFTP SFTPSERVER SCP
69 exec $SCP "$@"
6 - A `System Control Processor <https://github.com/ARM-software/SCP-firmware>`_8 processors. The RAM firmware for SCP is included in the TF-A FIP and is9 loaded by AP BL2 from FIP in flash to SRAM for copying by SCP (SCP has access21 FIP to SRAM. The SCP has access to AP SRAM. The address and size of SCP_BL222 is communicated to SCP using SDS. SCP copies SCP_BL2 from SRAM to its own
95 SCP Boot ROM: ``SCP_BL1`` (previously ``BL0``)98 Typically, this is the first code to execute on the SCP and cannot be modified.100 and authenticate an updateable SCP firmware image into an executable RAM105 This image was previously abbreviated as ``BL0`` but in some systems, the SCP107 make sense to interleave the image terminology for AP and SCP; both AP and SCP110 SCP RAM Firmware: ``SCP_BL2`` (previously ``BL3-0``)113 This is the 2nd stage SCP firmware. It is currently also known as the "SCP115 SCP needs to load/authenticate multiple 3rd level images in future.117 This image was previously abbreviated as BL3-0 but from the SCP's point of view,147 SCP Firmware Update Config: ``SCP_BL2U`` (previously ``BL2-U0``)[all …]
4 SCP5 SCP upload21 SCP upload
4 SCP5 SCP upload22 SCP upload failure
4 SCP16 SCP invalid user login (password authentication)
4 SCP16 SCP invalid user login
4 SCP16 SCP retrieval of nonexistent file
4 SCP17 SCP incorrect host key
4 SCP23 SCP retrieval of empty file
4 SCP24 SCP retrieval
4 SCP24 SCP correct host key
4 SCP23 SCP --head retrieval
4 SCP15 SCP retrieval of two files
4 SCP16 SCP retrieval of missing file followed by good file
8 SCP30 TFTP RRQ followed by SFTP retrieval followed by FILE followed by SCP retrieval then again in revers…
90 - System Control Processor (SCP)92 If desired, FIP can include an SCP BL2 image. If BL2 finds an SCP BL2 image93 in FIP, BL2 loads it into DRAM and kicks the SCP. Most of UniPhier boards94 still work without SCP, but SCP provides better power management support.96 To include SCP BL2, add the following option to the build command::98 SCP_BL2=<path-to-SCP>
109 - ``CSS_DETECT_PRE_1_7_0_SCP``: Boolean flag to detect SCP version110 incompatibility. Version 1.7.0 of the SCP firmware made a non-backwards111 compatible change to the MTL protocol, used for AP/SCP communication.112 TF-A no longer supports earlier SCP versions. If this option is set to 1120 instead of SCPI/BOM driver for communicating with the SCP during power121 management operations and for SCP RAM Firmware transfer. If this option
38 .. |SCP| replace:: :term:`SCP`
3 Protocols: SCP SFTP
4 Protocols: SFTP SCP
3 Protocols: SFTP SCP