FreeCommander XE文件或者文件夹无法打开右键菜单
FreeCommander XE文件或者文件夹无法打开右键菜单,一直转圈圈，然后无响应。
解决方法是在”C:\Users\yourdir\AppData\Local\FreeCommanderXE\Settings\FreeCommander.ini”文件中Language=chinese_s.lng下方增加下行即可
ShowContextMenu64Bit=0
RK3399功耗分析与优化
Voltage domain(VD) and power domain(PD)
- VD_CORE_B: including two big cores Contex-A72, the power consumption is relatively large, so separate a voltage domain.
- VD_CORE_L: including four little cores Contex-A53, the power consumption is relatively large, so separate a voltage domain.
- VD_LOGIC: including some peripherals’ controller and system bus, such as USB, EMMC, GMAC, SPI, I2C, EDP, VOP, AXI, AHB, APB, and so on.
- VD_CENTER: including vdpu, vepu, iep, rga and DDR controller.
- VD_GPU: including GPU, the power consumption is relatively large, so separate a voltage domain.
- VD_PMU: including PMU, SRAM, GPIO, PVTM and other modules relating to suspend and resume process.
EVB Power consumption
| Type | power-supply | Voltage(V) | current(mA) | Theoretical current on battery-3.8V(mA) | Remark |
|---|---|---|---|---|---|
| DC/DC | VDD_ARM | 0.96 | 10.20 | 3.23 | With 80% efficiency, conversion formula: V * I / efficiency / voltage of the battery |
| DC/DC | VDD_LOG | 0.96 | 89.30 | 28.20 | eg: Theoretical current of VDD_LOG on battery(3.8V) = 0.96 * 89.3 / 0.8 / 3.8 = 28.2 |
| DC/DC | VCC_DDR | 1.26 | 38.50 | 15.91 | |
| DC/DC | VCC_IO | 2.99 | 4.50 | 4.43 | |
| LDO | VCC_1V8 | 1.81 | 28.80 | 28.80 | Output current of LDO is equal to input current |
| LDO | VDD_1V0 | 1.00 | 10.90 | 10.90 | |
| LDO | VCC3V0_PMU | 3.01 | 1.20 | 1.20 | |
| battery | VBAT | 3.81 | 94.60 | 92.67 | Theoretical value is similar to actually measured value |
Data analysis for each path
1. VDD_CORE/VDD_CPU/VDD_ARM
- Confirm if the frequency voltage table (opp-table) is normal or not, if the actually measured voltage is consistent with the set voltage or not.
1 | /* Acquire the frequency voltage table, target column means the voltage required by some |
- Check cpu loading, analyze if there is abnormal task or interrupt.
1 | /* Use top command to check the task loading, the output of top with different versions |
2. VDD_GPU
The power consumption of VDD_GPU mainly confirms if the the frequency voltage table is normal or not, if
the measured voltage is consistent with the set voltage or not, using devfreq node.
1 | /* acquire the frequency voltage table */ |
3. VDD_LOGIC
Generally VDD_LOGIC will contain many modules, in order to manage the power consumption conveniently,
it will be divided into many PD internally. The power consumption can be analyzed mainly from the
following aspects:
- Confirm the running frequency and switch status of each module.
1 | cat /sys/kernel/debug/clk/clk_summary |
- Confirm the switch status of each PD.
1 | cat /sys/kernel/debug/pm_genpd/pm_genpd_summary |
- Generally DDR module is put in VDD_LOGIC, and the power consumption of DDR module is relatively
large, use the same devfreq strategy as GPU to optimize the power consumption, so need to confirm
the frequency voltage table and measured voltage. DDR also has some configurations with low power
consumption, such as pd_idle, sr_idle, odt switch and some other timing configurations. The debugging
process is relatively complex. Need to refer to the detailed DDR document.
1 | cat /sys/kernel/debug/opp/opp_summary |
4. VCC_DDR
VCC_DDR supplies power mainly for DDR component and DDR-IO part of SoC. The parameters affecting the
power consumption of VCC_DDR include: DDR frequency, DDR loading, DDR low power consumption
configuration, DDR component type and so on. Under the same condition, the power consumption of DDR
components from different vendors may have big difference.
5. VCC_IO
VCC_IO supplies power mainly for IO Pad of SoC and some peripherals. The power consumption can be
analyzed from the following aspects:
- Check the working status of peripheral module, if there is leakage.
- Check if IO pin status of SoC matches with the peripheral or not, for example, IO output is high, but the connected peripheral pin is low level.
Common scenario analysis
1. Static desktop
It is mainly the display module which is working, CPU, GPU, DDR should be reduced to the lowest frequency,
and enter low power consumption mode. Adjust VDD_CPU,VDD_GPU,VDD_LOGIC to the lowest voltage of
opp-table, confirm the status of clk_summary and pm_genpd_summary, confirm the peripheral modules
(WIFI, BT, etc.) are all closed. The static desktop generally is used as the basic power consumption of other
scenarios, so need to firstly optimize its power consumption to the best.
2. Video playback
It is mainly the video decoder (VPU/RKVDEC) which is working, GPU generally is closed. Especially confirm if
the running frequency of DDR and voltage of VDD_LOGIC are normal or not.
3. Game
It is mainly CPU and GPU which are working. Especially analyze the loading of CPU and GPU, frequency
change, the voltages of VDD_CPU and VDD_GPU are normal or not.
4. Deepsleep
Generally VDD_CPU and VDD_GPU will turn off the power supply, VDD_LOG only reserves the power supply
for some resume module, so need to focus on the power consumption analysis of IO, DDR components and
some peripherals.
Power consumption optimization strategy
1. CPU optimization
- Adjust cpufreq parameter.
1 | /* the default frequency scaling strategy used is interactive, relative parameters are |
- Close some cpu, limit the highest frequency of cpu.
1 | /* close cpu2，cpu3 */ |
2. DDR optimization
- Frequency scaling with scenario: configure different DDR frequencies for different scenarios, such as
4K video, video recording, dual display and so on.
1 | /* scenario definition */ |
- Frequency scaling with loading: monitor the loading, automatically adjust DDR frequency, frequency
scaling with loading may cause the reduction of the performance, you can fix DDR frequency in some
scenario considering the frequency scaling with scenario.
1 | /* configure the parameter of frequency scaling with loading in dts, need to open dfi |
- For more detailed configuration and optimization of DDR DEVFREQ, please refer to the document
《Rockchip-Developer-Guide-Linux4.4-Devfreq》.
3. Thermal control optimization
When the temperature is increasing to certain degree, the power consumption will increase dramatically,
especially in the case with high voltage.
- Improve the heat dissipation of hardware.
- Optimize the software thermal control strategy to avoid the big temperature fluctuation.
- Avoid the high voltage occurring in the case with high temperature through software limitation.
1 | &cpu0_opp_table { |
4. Power optimization
- In voltage conversion circuit, when the voltage reduction and current are relatively large, it is
recommended to use DCDC to improve the efficiency and reduce the power consumption.
For example:
Input 3.3V, output 1.0V-50mA
|Power Type | Input Current | Power Consumption |
| — | — | — |
| LDO | 50mA | 165mW |
| DCDC(with 80% efficiency) | 18.9mA | 62.4mW |
Git常用命令及操作
Git配置
Git全局配置
1
2
3
4git config --global user.name "frankieluo"
git config --global user.email "frankieluo@sina.com"
git config --global credential.helper store
git config --global push.default simple
Git基本命令
Clone项目
$ git clone http://gitlab.3bayslife.com:7777/app/alttest.gitStatus
$ git statusPull合并项目
$ git pullAdd新的或者修改后的文件
git add .提交到本地仓库
git commit -m "Initial commit"Push到服务器
git push -u origin master
Git repository 基本操作
Create a new repository
1
2
3
4
5
6git clone http://gitlab.3bayslife.com:7777/app/alttest.git
cd alttest
touch README.md
git add README.md
git commit -m "add README"
git push -u origin masterExisting folder
1
2
3
4
5
6cd existing_folder
git init
git remote add origin http://gitlab.3bayslife.com:7777/app/alttest.git
git add .
git commit -m "Initial commit"
git push -u origin masterExisting Git repository
1
2
3
4
5cd existing_repo
git remote rename origin old-origin
git remote add origin http://gitlab.3bayslife.com:7777/app/alttest.git
git push -u origin --all
git push -u origin --tags
Git进阶操作
查看远程分支
$ git branch -a切换分支
$ git checkout -b dev origin/dev切换回master分支
$ git checkout master再次切回dev分支
$ git checkout dev切换commit分支
$ git checkout 988d45bae9ceefc9a31b5aadc701f6f115ecd895服务器代码合并本地代码
1
2
3git stash //暂存当前正在进行的工作。
git pull origin master //拉取服务器的代码
git stash pop //合并暂存的代码回滚本地代码
$ git reset --hard//回滚到上一个版本$ git checkout -- .$ git checkout -- readme.mdgit rm 与 git rm –cached 的区别
git rm ： 同时从工作区和索引中删除文件。即本地的文件也被删除了。
git rm –cached ： 从索引中删除文件。但是本地文件还存在， 只是不希望这个文件被版本控制。zsh反应慢
You can add this to your git config and zsh won’t check the status anymoregit config --add oh-my-zsh.hide-status 1git config --add oh-my-zsh.hide-dirty 1git删除未跟踪文件
删除 untracked files:
git clean -f连 untracked 的目录也一起删掉:
git clean -fd连 gitignore 的untrack 文件/目录也一起删掉 （慎用，一般这个是用来删掉编译出来的 .o之类的文件用的）:
git clean -xfd在用上述 git clean 前，墙裂建议加上 -n 参数来先看看会删掉哪些文件，防止重要文件被误删:
1
2
3git clean -nxfd
git clean -nf
git clean -nfd
git创建新分支并提交到远程
创建一个本地分支
git checkout -b 名称查看现在的分支状态
git branch (星号代表当前的分支)把新建的分支push到远程，相当于创建一个远程分支
git push origin 名称:名称删除远程分支
1
2
3git push origin :名称
或者
git push origin --delete 名称删除本地分支（不能在此分支上）
git branch -d 名称
git log操作
How to have git log show filenames like svn log -v:
For full path names of changed files:
git log --name-onlyor
git log --name-only --oneline查看日期范围内的记录信息
1
2
3
4
5
6
7git log --after="2019-3-31" --before="2019-5-1"
git log --author="frankieluo" --after="2019-7-30" --before="2019-9-1" > ../usefull/work_JFF2_Aug.log
git log --author="frankieluo" --after="2019-7-30" --before="2019-9-1" > ../release/work_hardware_test_Aug.log
git log --author="frankieluo" --after="2019-7-30" --before="2019-9-1" > ../release/alt_test_Aug.logFor full path names and status of changed files:
git log --name-statusFor abbreviated pathnames and a diffstat of changed files:
git log --statThere’s a lot more options, check out the docs https://git-scm.com/docs/git-log .
From the git-diff manpage:
git log -- vendor/nxp-opensource/uboot-imx/drivers/usb/gadget/fastboot_lock_unlock.h使用git log查看单个文件改动记录
git log -- device/fsl/ax2130/overlay/frameworks/base/core/res/res/values/config.xml使用git show命令查看commit hashID的详细情况
git show b61f128ac5015a8c2b14b28c67837ebf1924a5e1
git format-patch
某一笔提交的patch
git format-patch b61f128ac5015a8c2b14b28c67837ebf1924a5e1 -1某笔提交(包含)之前的几次提交
git format-patch commitID -ngit format-patch b61f128ac5015a8c2b14b28c67837ebf1924a5e1 -2某两笔(包后不包前)提交之间的所有提交
git format-patch 1ac240c4561fab6ce400943edb38e46c792b949a..255867fabcf79246d948fadfebe307f8a848bff4某笔提交(不包含)以后所有提交
git format-patch 1ac240c4561fab6ce400943edb38e46c792b949a
git merge 解决合并的冲突
把issue2分支和issue3分支的修改合并到master。
- 切换master分支后，与issue2分支合并。
1 | git checkout master |
- 接着合并issue3分支。
1 | git merge issue3 |
- 接着合并issue3分支。
1 | git merge issue3 |
- 在发生冲突的地方，Git生成了内容的差异。请做以下修改：
1 | add 把变更录入到索引中 |
- 修改冲突的部分，重新提交
1 | git add myfile.txt |
Git 合并特定 commits 到另一个分支
git cherry-pick 1ac240
合并某个分支上的一系列commits
在一些特性情况下，合并单个 commit 并不够，你需要合并一系列相连的 commits 。这种情况下就不要选择 cherry-pick 了，rebase 更适合。还以上例为例，假设你需要合并 feature 分支的 commit 76cada ~ 62ecb3 到 dev 分支。
- 首先需要基于 feature 创建一个新的分支，并指明新分支的最后一个 commit ：
git checkout -b newbranch 62ecb3
- 然后，rebase 这个新分支的 commit 到 dev（–onto dev）。 76cada^ 指明你想从哪个特定的 commit 开始。
git rebase --onto dev 76cada^
得到的结果就是 feature 分支的 commit 76cada ~62ecb3 都被合并到了 dev 分支。
git 删除文件后如何恢复
1 | [xxx@xxx static_files]$ git status |
git reset HEAD abbr_datagit checkout -- abbr_data
git diff [–options] [–] [
For instance, to see the difference for a file “main.c” between now and two commits back, here are three equivalent commands:
1
2
3git diff HEAD^^ HEAD main.c
git diff HEAD^^..HEAD -- main.c
git diff HEAD~2 HEAD -- main.c某两笔(包前包后)提交之间的所有提交
git diff commitID1 commitID2 > patch.diff
git apply
检查patch/diff是否能正常打入
git apply –check file.patch文件
git apply –check file.diff文件打入patch/diff
git apply file.patch文件
git apply file.diff文件解决冲突
如果在合入patch的过程中报错了，可以使用下面命令：
git apply –reject file.patch
这个命令会自动合入不冲突的代码，然后保留冲突的部分，同时会生成后缀为.rej的文件，用于保存没有合并进去的部分，可以参考这个进行冲突解决。
解决完冲突后，删除后缀为.rej文件，并执行git add . 添加改动到暂存区
最后执行git am –resolved或者git am –continue
git tag
- 查看本地分支标签
git tag -l
- 查看远程所有标签
git ls-remote --tags
- 给当前分支打标签
git tag v1.1.0
- 给特定的某个commit版本打标签，比如现在某次提交的id为 039bf8b
1 | git tag v1.0.0 039bf8b |
- 删除本地某个标签
1 | git tag --delete v1.0.0 |
- 删除远程的某个标签
1 | git push -d origin v1.0.0 |
- 将本地标签一次性推送到远程
1 | git push origin --tags |
- 将本地某个特定标签推送到远程
git push origin v1.0.0
- 查看某一个标签的提交信息
git show v1.0.0
- 根据某个commit创建本地分支
例如: 当前分支的某个commit id = 12345678，我们可以基于这个id创建本地分支git checkout 12345678 -b newBranch
git submodules
With version 2.13 of Git and later, –recurse-submodules can be used instead of –recursive:
git clone --recurse-submodules -j8 git://github.com/foo/bar.gitWith version 1.9 of Git up until version 2.12 (-j flag only available in version 2.8+):
git clone --recursive -j8 git://github.com/foo/bar.gitWith version 1.6.5 of Git and later, you can use:
git clone --recursive git://github.com/foo/bar.gitFor already cloned repos, or older Git versions, use:
1
2
3git clone git://github.com/foo/bar.git
cd bar
git submodule update --init --recursive
git配置代理
添加代理，后面端口号去系统设置 -> 网络和Internet -> 代理
git config --global https.proxy http://127.0.0.1:10809去除代理
git config --global https.proxy ""查看配置信息
1 | git config --global --list |
git进阶用法
git status -s | awk '{if ($1 == "M") {print $2} }' | xargs git rm --cached
git常见错误
错误 -fatal: remote origin already exists.
1、先删除远程 Git 仓库
$ git remote rm origin2、再添加远程 Git 仓库
$ git remote add origin http://act4.myqnapcloud.com:10080/app/cappec-weather-ios.git错误 Git refusing to merge unrelated histories
git pull origin master --allow-unrelated-histories
Android NDK-JNI使用技巧
Android NDK-JNI的一些使用技巧
如何在现有项目中加入*.so共享库
- 方式一
- 在”app/src/main/“目录中新建”jniLibs”，将共享库复制到此目录
- 在android studio中sync files即可
- 方式二
- 在”app/src/main/“目录中新建”libs”，将共享库复制到此目录
- 在app/build.gradle中添加libs文件夹路径
1 | android { |
如何在现有项目中加入JNI源码
- 方式一：使用android studio添加
鼠标右击app工程，选择Add C++ to Module
选择Link an existing CMakeLists.txt or Android.mk to this module
- 方式二：直接在app/build.gradle中添加代码，其中NDK Version需要更改为android studio设置中指定NDK路径中的版本
1 | android { |
JNI源码如何生成*.so共享库
找到NDK路径中找到”ndk-build.cmd”，比如我的路径为”C:\Users\ASUS\AppData\Local\Android\Sdk\ndk-bundle\ndk-build.cmd”
在Terminal或者DOS控制到中，CD 到JNI源码位置，然后执行”C:\Users\ASUS\AppData\Local\Android\Sdk\ndk-bundle\ndk-build.cmd”
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17D:\work\App\Myjni\app\src\main\jni>"C:\Users\ASUS\AppData\Local\Android\Sdk\ndk-bundle\ndk-build.cmd"
fcntl(): Bad file descriptor
Android NDK: APP_PLATFORM not set. Defaulting to minimum supported version android-16.
Android NDK: WARNING: APP_PLATFORM android-16 is higher than android:minSdkVersion 1 in D:/work/App/Myjni/app/src/main/AndroidManifest.xml. NDK binaries will *not* be compatible with devices older than android-16. See https://android.googlesource.com/platform
/ndk/+/master/docs/user/common_problems.md for more information.
Android NDK: WARNING: Unsupported source file extensions in D:/work/App/Myjni/app/src/main/jni/Android.mk for module i2chmi
Android NDK: :
Android NDK: WARNING: Unsupported source file extensions in D:/work/App/Myjni/app/src/main/jni/Android.mk for module i2chmi
Android NDK: :
Android NDK: WARNING: Unsupported source file extensions in D:/work/App/Myjni/app/src/main/jni/Android.mk for module i2chmi
Android NDK: :
Android NDK: WARNING: Unsupported source file extensions in D:/work/App/Myjni/app/src/main/jni/Android.mk for module i2chmi
Android NDK: :
[arm64-v8a] Install : libi2chmi.so => libs/arm64-v8a/libi2chmi.so
[x86_64] Install : libi2chmi.so => libs/x86_64/libi2chmi.so
[armeabi-v7a] Install : libi2chmi.so => libs/armeabi-v7a/libi2chmi.so
[x86] Install : libi2chmi.so => libs/x86/libi2chmi.so
Reference
Docker build如何调试
前言
Docker编译dockerfile的过程中，经常会碰到构建失败，那么怎样去调试dockerfile呢？
其实Docker编译的时候为每一条编译指令会建立一个临时的镜像，当编译CMD失败时，会保留前一份镜像，我们可以进到这个镜像，然后手动运行下一条CMD，查看编译错误信息。
创建dockerfile
mkdir tmp && cd tmpvim Dockerfile1
2
3
4FROM alpine:3.9
COPY . /app
RUN make /app
CMD python /app/app.py
编译dockerfile
docker build -t docker-alpine-test:0.1 .1
2
3
4
5
6
7
8
9
10Sending build context to Docker daemon 2.048kB
Step 1/4 : FROM alpine:3.9
---> 78a2ce922f86
Step 2/4 : COPY . /app
---> 2b756be83925
Step 3/4 : RUN make /app
---> Running in 922354c938e3
/bin/sh: make: not found
The command '/bin/sh -c make /app' returned a non-zero code: 127$ docker images1
2REPOSITORY TAG IMAGE ID CREATED SIZE
<none> <none> 2b756be83925 9 minutes ago 5.55MB可以看到docker保留了前一个运行成功的镜像2b756be83925
调试镜像
docker run -it 2b756be83925 /bin/sh1
2
3
4
5
6
7
8/ # ls
app bin dev etc home lib media mnt opt proc root run sbin srv sys tmp usr var
/ # ls /app/
Dockerfile
/ # make /app
/bin/sh: make: not found
/ # python /app/app.py
/bin/sh: python: not found
Reference
Docker查看容器并安全退出容器
前言
Docker中有时候我们会想去查看容器具体内容，文件结构，配置信息等，但如何进入容器内部查看？又如何安全退出而不停止容器呢？
进入容器
- attach:
docker attach fa0b220ed5d0, 此方式只适合本身是可交互方式启动的容器. - exec:
docker exec -it fa0b220ed5d0 /bin/sh.
查看exec命令使用说明docker exec -h: “Run a command in a running container”.
退出容器（Ctrl+P+Q）
- 输入exit或Ctrl+C或Ctrl+D退出容器, 容器也会停止.
- Ctrl+P+Q, 正常退出而不关闭容器.
Final Cut Pro常用技巧
前言
Final Cut Pro 是苹果公司开发的一款专业视频剪辑软件。这里记录一些常用的技巧
基本技巧
- 基本工具
- A选择工具，移动视频会使其他视频位置改变
- P位置工具，移动视频会遮挡其他视频
- T裁剪工具，可以调整视频本身的时间
- B切割工具，可以使用Ctrl+B快捷键替代
- Z缩放工具，可以使用Ctrl+’+’, Ctril + ‘-‘快捷键替代
- 关键帧动画
- 关键帧是同过视频属性，效果设置不同的参数而成，至少需要打两帧关键帧
- 选择视频，按Ctrl+v会显示和隐藏关键帧信息
- 视频速度调整
- 所有速度调整都在视频预览窗口下方的圆圈图标按钮
- 对整段视频做变速，可以先显示速度（shift+n），然后拖动最后速度条小竖线变换视频时间长短调节
- 速度转场：需要先切割速度，然后对一段视频调整，并保留视频转场
- 即时重放：可以选中一段视频（打i,o或者用范围选择工具），然后选择即时重放
- 调色
- 色彩基本知识点
- 色彩因光线而存在。发光物体对应加色模型，三原色是RGB红绿蓝。反光物体对应减色模型，三原色是CMY青品黄。
- 红青、蓝黄、绿品是三组互补色。要增加一种颜色，可以同时增加他的相邻色，或者减少他的互补色。
- 色相（H）、饱和度（S）和亮度（L）是颜色的三个基本属性。
- 参考链接
https://zhuanlan.zhihu.com/p/27785954
- 色彩因光线而存在。发光物体对应加色模型，三原色是RGB红绿蓝。反光物体对应减色模型，三原色是CMY青品黄。
- 色彩基本知识点
横竖屏对齐背景放大效果
- 新建竖屏视频剪辑
- 导入横屏视频
- 按住option建，向上或下拖动视频Copy一份
- 点击下层视频，在属性中调节变换->缩放，放大至填充屏幕
- 可适当调节透明度
给视频添加上下黑边
使用信箱模式
- 新建项目并导入视频后，在效果中双击选信箱模式
- 在属性中，调节Aspect Ratio为2.35:1，也可以适当调节Offset和Border size
使用裁剪
- 新建项目并导入视频后，在属性中选择裁剪
- 在上下中，直接输入133.0
调节整个视频的尺寸
- 选中项目，信息栏里->修改
- 弹出对话框中，视频->自定义->尺寸改为1920x817
- 点选视频，在空间符合->类型->选择填充
视频后期制作小技巧之背景音乐
- 使用Downie下载BGM
- 使用AU让BGM时长和视频相匹配
- 拖拽音频文件到文件夹内
- 文件->新建->多轨回话
- 拖拽左边文件到右边多轨回话的轨道1中并与开始对齐
- 点选属性->重新混合->启用重新混合，调节时间为你想要的长度并回车
- 最后，点击文件->导出->多轨混音->所选剪辑
HDR剪切技巧
正确创建HDR项目
- 新建资源库，并’资源库属性’ -> ‘标准’中修改为’广色域HDR’
- 新建项目，对于iPhone12拍摄的HDR视频，’编解码器’选择’广色域HDR - Rec. 2020 HLG’
HDR项目导入SDR视频偏黑
- 添加效果->颜色->HDR工具
- 在视频属性HDR工具中模式选择’PQ 转 HLG (Rec.2100)’
- 调整’峰值亮度（尼特）’ 为 100
SDR项目导入HDR视频过暴
- 添加效果->颜色->HDR工具
- 在视频属性HDR工具中模式选择’HLG 转 Rec.709 SDR’
LUT设置
- 尽量使用效果中自定义LUT工具
- 然后在属性中输入和输出都选择为’Rec 2020 HLG’
Python scp自动下载上传文件脚本
前言
工作中我们可能经常会需要从服务器或另一台电脑复制大量文件，如果文件在不同的目录，复制就比较麻烦，这个时候用脚本就比较简单了，一键搞定。Python脚本支持多平台，可以在Windows, Mac, Linux上运行。
安装依赖库
- pip install paramiko
- pip install scp
直接上源码
1 | import paramiko |
- 根据你的需求，更改TODO标识的地方即可