AD merge patch(admrgpch)合并多个Patch

AD Merge Patch(admrgpch)工具允许将多个Patch合并为一个,简化应用过程。通常,早期的patch包含c、d、g三个driver,而现在多采用unified driver。在合并patch时,建议记录所打patch版本,因为合并后无法直接查看应用过的具体patch号。运行AD Merge Patch需设置环境,指定源目录、目标目录和合并名称。在UNIX和Windows上,提供了运行命令的例子。
部署运行你感兴趣的模型镜像
AD Merge(admrgpch)将多个Patch合并为一个

如果一次需要打多个patch,为了节省时间和简化打Patch的重复步骤,可以把他们合并成一个Patch。

在早期的patch 中可能有‘c2834825.drv d2834825.drv g2834825.drv’,其实是一个patch的三个driver, 分别是copy driver, database driver和generate driver, 是要在apps和db tier分别执行的。
而现在的patch通常只有u***.drv一个unified driver, 是将这(c,d,g)三个driver整合在一起的了,所以看起来似乎只有一个*.drv文件。

建议:在merge patch的时候,做好所打patch版本的记录,因为merge patch后,在系统中查找不到你应用过的具体patch号,只有一个你merge patch的名称.

Running AD Merge Patch
AD Merge Patch is located in AD_TOP/bin. However, you run it from the parent directory of the source directory.
1. Set the environment.
You must set the environment to indicate the location of the configuration parameters that define your system. This task is common to many AD utilities.

2. Run AD Merge Patch.
From the <top> directory, run AD Merge patch as follows:

admrgpch -s <source directory> -d <destination directory> -merge_name <name> [-manifest <manifest filename>]

For example, if you have four patches called 1234561, 1234562, 1234563, and 1234564 located in the source directory /d01/patch_merge/source, and the destination directory is/d01/patch_merge/destination. To create a merged patch
named "merge99", you would use the following commands:

UNIX:
$ cd /d01/patch_merge
$ ls  ./source  
1234561   1234562   1234563   1234564 
admrgpch -s /d01/patch_merge/source -d /d01/patch_merge/destination \ 
-merge_name merge99

Windows:
C:\> cd \d01\patch_merge
C:\> admrgpch -s d:\patch_merge\source -d d:\patch_merge\destination \
-merge_name merge99




您可能感兴趣的与本文相关的镜像

Qwen3-8B

Qwen3-8B

文本生成
Qwen3

Qwen3 是 Qwen 系列中的最新一代大型语言模型,提供了一整套密集型和专家混合(MoE)模型。基于广泛的训练,Qwen3 在推理、指令执行、代理能力和多语言支持方面取得了突破性进展

duanchangxu1604@ubuntu:~/NVMP/sdk/soc/ssc37x$ git pull --rebase remote: Finding sources: 100% (141/141) remote: Total 141 (delta 47), reused 141 (delta 47) Receiving objects: 100% (141/141), 1.41 MiB | 1.39 MiB/s, done. Resolving deltas: 100% (47/47), completed with 27 local objects. From ssh://gerrit-ce.tp-link.com:29418/IPC/NVMP/MSTAR/ssc37x dda71ad..cab8573 develop_sz0519 -> origin/develop_sz0519 72819e6..7c6e464 nvmp_release_1.8_bis -> origin/nvmp_release_1.8_bis First, rewinding head to replay your work on top of it... Applying: [c212v3] Separate kernel and romfs(4/4) Using index info to reconstruct a base tree... M boot-ssc375/configs/normalboot.mk M boot-ssc375/src/Makefile M boot-ssc375/src/lib_verify/validateFirmwareWithRecover.c M linux-5.10.117/drivers/sstar/slp_flash/Kconfig M linux-5.10.117/drivers/sstar/slp_flash/slp_flash.c .git/rebase-apply/patch:115: trailing whitespace. #ifdef KER_ROM_SEPARATED .git/rebase-apply/patch:117: trailing whitespace. #else .git/rebase-apply/patch:118: trailing whitespace. #define RADIO_LEN 0x0 .git/rebase-apply/patch:119: trailing whitespace. #endif .git/rebase-apply/patch:127: trailing whitespace. #ifdef KER_ROM_SEPARATED warning: squelched 143 whitespace errors warning: 148 lines add whitespace errors. Falling back to patching base and 3-way merge... Auto-merging linux-5.10.117/drivers/sstar/slp_flash/slp_flash.c Auto-merging linux-5.10.117/drivers/sstar/slp_flash/Kconfig CONFLICT (content): Merge conflict in linux-5.10.117/drivers/sstar/slp_flash/Kconfig Auto-merging boot-ssc375/src/lib_verify/validateFirmwareWithRecover.c Auto-merging boot-ssc375/src/Makefile Auto-merging boot-ssc375/configs/normalboot.mk error: Failed to merge in the changes. Patch failed at 0001 [c212v3] Separate kernel and romfs(4/4) The copy of the patch that failed is found in: .git/rebase-apply/patch When you have resolved this problem, run "git rebase --continue". If you prefer to skip this patch, run "git rebase --skip" instead. To check out the original branch and stop rebasing, run "git rebase --abort".
11-18
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值