未验证 提交 c0f67a56 编写于 作者: O openharmony_ci 提交者: Gitee

!6093 kernel common patch

Merge pull request !6093 from 朱佳鑫/myfeature
上级 9aefa849 b7106f29
master OpenHarmony-3.2-Beta2 OpenHarmony-3.2-Beta3 OpenHarmony-3.2-Beta4 OpenHarmony-3.2-Beta5 OpenHarmony-3.2-Release OpenHarmony-4.0-Beta1 OpenHarmony-4.0-Beta2 bak_OpenHarmony-4.0-Beta1_20230529 docs-modify feature_IDL_20220811 monthly_20220816 monthly_20221018 monthly_20230815 revert-merge-17651-master revert-merge-19334-OpenHarmony-4.0-Beta1 revert-merge-19586-master revert-merge-20613-master revert-merge-21757-OpenHarmony-4.0-Beta2 revert-merge-21765-OpenHarmony-4.0-Beta2 revert-merge-23766-master weekly_20220719 weekly_20220726 weekly_20220802 weekly_20220809 weekly_20220816 weekly_20220823 weekly_20220830 weekly_20220906 weekly_20220913 weekly_20220920 weekly_20220927 weekly_20221004 weekly_20221011 weekly_20221018 weekly_20221025 weekly_20221101 weekly_20221108 weekly_20221115 weekly_20221122 weekly_20221129 weekly_20221206 weekly_20221213 weekly_20221220 weekly_20221227 weekly_20230103 weekly_20230110 weekly_20230117 weekly_20230124 weekly_20230131 weekly_20230207 weekly_20230214 weekly_20230221 weekly_20230228 weekly_20230307 weekly_20230314 weekly_20230321 weekly_20230328 weekly_20230404 weekly_20230411 weekly_20230418 weekly_20230425 weekly_20230502 weekly_20230509 weekly_20230516 weekly_20230523 weekly_20230530 weekly_20230606 weekly_20230613 weekly_20230619 weekly_20230626 weekly_20230627 weekly_20230704 weekly_20230712 weekly_20230725 weekly_20230801 weekly_20230808 weekly_20230815 weekly_20230822 weekly_20230829 weekly_20230905 OpenHarmony-v4.0-Beta2 OpenHarmony-v4.0-Beta1 OpenHarmony-v3.2.3-Release OpenHarmony-v3.2.2-Release OpenHarmony-v3.2.1-Release OpenHarmony-v3.2-Release OpenHarmony-v3.2-Beta5 OpenHarmony-v3.2-Beta4 OpenHarmony-v3.2-Beta3 OpenHarmony-v3.2-Beta2
无相关合并请求
......@@ -5,7 +5,7 @@
Apply the HDF patches based on the kernel version in the **kernel/linux/build** repository. For details, see the method for applying the HDF patch in **kernel.mk**.
```
$(OHOS_BUILD_HOME)/drivers/adapter/khdf/linux/patch_hdf.sh $(OHOS_BUILD_HOME) $(KERNEL_SRC_TMP_PATH) $(HDF_PATCH_FILE)
$(OHOS_BUILD_HOME)/drivers/hdf_core/adapter/khdf/linux/patch_hdf.sh $(OHOS_BUILD_HOME) $(KERNEL_SRC_TMP_PATH) $(KERNEL_PATCH_PATH) $(DEVICE_NAME)
```
2. Apply the chip driver patches.
......
......@@ -131,14 +131,14 @@ For details about how to use the logs, see [Hilog\_lite](https://gitee.com/openh
Run the shell script to apply HDF patches.
1. Set the three variables in the **patch\_hdf.sh** script.
1. Set the four variables in the **patch\_hdf.sh** script.
2. Obtain the **patch\_hdf.sh** script.
3. Run the **patch\_hdf.sh** script to pass the three variables in sequence.
3. Run the **patch\_hdf.sh** script to pass the four variables in sequence.
Run the following command:
```
./patch_hdf.sh [Project root directory path] [Kernel directory path] [HDF patch file]
./patch_hdf.sh [Project root directory path] [Kernel directory path] [Kernel patch path] [Device name]
```
The following uses Raspberry Pi 3b as an example:
......@@ -148,7 +148,8 @@ For details about how to use the logs, see [Hilog\_lite](https://gitee.com/openh
PROJ_ROOT/drivers/adapter/khdf/linux/patch_hdf.sh \
PROJ_ROOT # Specify the path of the project root directory.\
PROJ_ROOT/out/KERNEL_OBJ/kernel/src_tmp/linux-rpi3b # Specify the kernel directory for applying the patch.\
PROJ_ROOT/kernel/linux/patches/linux-4.19/hi3516dv300_patch/hdf.patch # HDF patch file.
PROJ_ROOT/kernel/linux/patches/linux-4.19 # Kernel patch patch.\
hi3516dv300 # Device name.
```
2. Configure the **config** file.
......
......@@ -64,18 +64,23 @@ kernel/
│ ├── linux-4.19 # OpenHarmony linux-4.19 common kernel
│ ├── linux-5.10 # OpenHarmony linux-5.10 common kernel
│ ├── build
│ │ ├── BUILD.gn # GN file of the build framework
│ │ ├── BUILD.gn # GN file of the build framework
│ │ ├── kernel.mk # Kernel build file
│ │ └── ohos.build # Kernel build component file
│ ├── patches
│ │ ├── linux-4.19 # linux-4.19 patches
│ │ │   ├── common_patch
│ │ │   │ └── hdf.patch # linux-4.19 HDF patches
│ │ │   └── hi3516dv300_patch
│ │ │   ├── hi3516dv300.patch # linux-4.19 Hi3516D V300 SOC patches
│ │ │   └── hdf.patch # linux-4.19 Hi3516D V300 HDF patches
│ │ │   └── hi3516dv300.patch # linux-4.19 Hi3516D V300 SOC patches
│ │ └── linux-5.10
│ │    ├── common_patch
│ │    │ └── hdf.patch # linux-5.10 HDF patches
│ │    └── hi3516dv300_patch
│ │    ├── hi3516dv300.patch # linux-5.10 Hi3516D V300 SOC patches
│ │    └── hdf.patch # linux-5.10 Hi3516D V300 HDF patches
│ │    │ └── hi3516dv300.patch # linux-5.10 Hi3516D V300 SOC patches
│ │    └── rkrk3568_patch
│ │    ├── kernel.patch # linux-5.10 rk3568 SOC patches
│ │    └── hdf.patch # linux-5.10 rk3568 customized HDF patches
│ └── config
│ ├── linux-4.19
│ │   └── arch
......@@ -151,7 +156,7 @@ For details, see "Usage" in LiteOS-A Kernel [README](https://gitee.com/openharmo
Apply the HDF kernel patches matching your kernel version. For details, see the method in **kernel.mk** in the **kernel/linux/build** repository.
```
$(OHOS_BUILD_HOME)/drivers/adapter/khdf/linux/patch_hdf.sh $(OHOS_BUILD_HOME) $(KERNEL_SRC_TMP_PATH) $(HDF_PATCH_FILE)
$(OHOS_BUILD_HOME)/drivers/hdf_core/adapter/khdf/linux/patch_hdf.sh $(OHOS_BUILD_HOME) $(KERNEL_SRC_TMP_PATH) $(KERNEL_PATCH_PATH) $(DEVICE_NAME)
```
2. Apply the chip driver patches.
......
......@@ -3,7 +3,7 @@
1. 合入HDF补丁
在kernel/linux/build仓中,按照kernel.mk中HDF的补丁合入方法,合入不同内核版本对应的HDF内核补丁:
```
$(OHOS_BUILD_HOME)/drivers/adapter/khdf/linux/patch_hdf.sh $(OHOS_BUILD_HOME) $(KERNEL_SRC_TMP_PATH) $(HDF_PATCH_FILE)
$(OHOS_BUILD_HOME)/drivers/hdf_core/adapter/khdf/linux/patch_hdf.sh $(OHOS_BUILD_HOME) $(KERNEL_SRC_TMP_PATH) $(KERNEL_PATCH_PATH) $(DEVICE_NAME)
```
2. 合入芯片平台驱动补丁
......
......@@ -144,15 +144,15 @@ obj-$(CONFIG_HIEVENT) += hievent/
1. 打HDF补丁。
在Linux内核打HDF补丁时,执行补丁shell脚本合入HDF补丁。
1. 配置HDF补丁脚本的个变量参数。
1. 配置HDF补丁脚本的个变量参数。
2. 获取patch_hdf.sh脚本。
3. 执行patch_hdf.sh脚本依次传入个变量参数。
3. 执行patch_hdf.sh脚本依次传入个变量参数。
patch_hdf.sh脚本三个参数含义为:第一个入参为工程根目录路径,第二入参为内核目录路径,第三个入参为hdf补丁文件
patch_hdf.sh脚本四个参数含义为:第一个入参为工程根目录路径,第二入参为内核目录路径,第三个入参为内核版本路径,第四个参数是当前设备名
```
./patch_hdf.sh [工程根目录路径] [内核目录路径] [hdf补丁文件]
./patch_hdf.sh [工程根目录路径] [内核目录路径] [内核补丁路径] [设备名]
```
以树莓派3b为示例介绍:
......@@ -163,7 +163,8 @@ obj-$(CONFIG_HIEVENT) += hievent/
PROJ_ROOT/drivers/adapter/khdf/linux/patch_hdf.sh \
PROJ_ROOT # 指定工程根目录路径 \
PROJ_ROOT/out/KERNEL_OBJ/kernel/src_tmp/linux-rpi3b # 打补丁的内核目录路径 \
PROJ_ROOT/kernel/linux/patches/linux-4.19/hi3516dv300_patch/hdf.patch # HDF补丁文件
PROJ_ROOT/kernel/linux/patches/linux-4.19 # 内核补丁路径.\
hi3516dv300 # 设备名.
```
2. 配置config。
......
......@@ -75,18 +75,23 @@ kernel/
│ ├── linux-4.19 # OpenHarmony linux-4.19 Common kernel
│ ├── linux-5.10 # OpenHarmony linux-5.10 Common kernel
│ ├── build
│ │ ├── BUILD.gn # 编译框架GN文件
│ │ ├── BUILD.gn # 编译框架GN文件
│ │ ├── kernel.mk # 内核编译文件
│ │ └── ohos.build # 内核编译组件文件
│ ├── patches
│ │ ├── linux-4.19 # linux-4.19 相关patch
│ │ │   ├── common_patch
│ │ │   │ └── hdf.patch # linux-4.19 HDF patches
│ │ │   └── hi3516dv300_patch
│ │ │   ├── hi3516dv300.patch # linux-4.19 hi3516dv300 SOC patch
│ │ │   └── hdf.patch # linux-4.19 hi3516dv300 hdf patch
│ │ │   └── hi3516dv300.patch # linux-4.19 Hi3516D V300 SOC patches
│ │ └── linux-5.10
│ │    ├── common_patch
│ │    │ └── hdf.patch # linux-5.10 HDF patches
│ │    └── hi3516dv300_patch
│ │    ├── hi3516dv300.patch # linux-5.10 hi3516dv300 SOC patch
│ │    └── hdf.patch # linux-5.10 hi3516dv300 hdf patch
│ │    │ └── hi3516dv300.patch # linux-5.10 Hi3516D V300 SOC patches
│ │    └── rkrk3568_patch
│ │    ├── kernel.patch # linux-5.10 rk3568 SOC patches
│ │    └── hdf.patch # linux-5.10 rk3568 定制 HDF patches
│ └── config
│ ├── linux-4.19
│ │   └── arch
......@@ -162,7 +167,7 @@ Hi3518EV300默认使用jffs2文件系统,Hi3516DV300默认使用FAT文件系
在kernel/linux/build仓中,按照kernel.mk中HDF的补丁合入方法,合入不同内核版本对应的HDF内核补丁:
```
$(OHOS_BUILD_HOME)/drivers/adapter/khdf/linux/patch_hdf.sh $(OHOS_BUILD_HOME) $(KERNEL_SRC_TMP_PATH) $(HDF_PATCH_FILE)
$(OHOS_BUILD_HOME)/drivers/hdf_core/adapter/khdf/linux/patch_hdf.sh $(OHOS_BUILD_HOME) $(KERNEL_SRC_TMP_PATH) $(KERNEL_PATCH_PATH) $(DEVICE_NAME)
```
2. 合入芯片平台驱动补丁
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册
反馈
建议
客服 返回
顶部