openharmony/kernel_linux_build
1
0
Fork 0
mirror of https://github.com/openharmony/kernel_linux_build.git synced 2026-08-25 12:50:27 -04:00
Code Issues Packages Projects Releases Wiki Activity

修复 README_zh.md/README.md文档中路径错误和描述模糊问题

Browse Source 
Signed-off-by: Ywenrui <yaowenrui2@huawei.com>
This commit is contained in:
Ywenrui
2023-09-14 21:02:29 +08:00
parent 5cf260d140
commit 3f05524b0b
2 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+6 -6
View File
@@ -30,14 +30,14 @@ kernel/linux/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
│   └── hispark_taurus_patch
│   └── hispark_taurus.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
└── rkrk3568_patch
└── hispark_taurus_patch
│ └── hispark_taurus.patch # linux-5.10 Hi3516D V300 SOC patches
└── rk3568_patch
├── kernel.patch # linux-5.10 rk3568 SOC patches
└── hdf.patch # linux-5.10 rk3568 customized HDF patches
```
@@ -74,7 +74,7 @@ kernel/linux/patches
> **Note**:
>
>In the OpenHarmony project build process, patches are installed after **kernel/linux/linux-\*\.\*** is copied. Before using the version-level build command of OpenHarmony, ensure that the **kernel/linux/linux-\*\.\*** source code is available.
>In the OpenHarmony project build process, patches are installed after **kernel/linux/linux-5.10** is copied. Before using the version-level build command of OpenHarmony, ensure that the **kernel/linux/linux-5.10** source code is available.
>
>The kernel built is generated in the **kernel** directory under the **out** directory. Modify the **config** file based on the kernel built, and copy the generated **.config** file to the corresponding path in the **config** repository. Then, the configuration takes effect.
README_zh.md
+6 -6
View File
@@ -30,14 +30,14 @@ kernel/linux/patches
├── linux-4.19 # linux-4.19 相关patch
│   ├── common_patch
│   │ └── hdf.patch # linux-4.19 HDF patches
│   └── hi3516dv300_patch
│   └── hi3516dv300.patch # linux-4.19 Hi3516D V300 SOC patches
│   └── hispark_taurus_patch
│   └── hispark_taurus.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
└── rkrk3568_patch
└── hispark_taurus_patch
│ └── hispark_taurus.patch # linux-5.10 Hi3516D V300 SOC patches
└── rk3568_patch
├── kernel.patch # linux-5.10 rk3568 SOC patches
└── hdf.patch # linux-5.10 rk3568 定制 HDF patches
```
@@ -74,7 +74,7 @@ kernel/linux/patches
> **须知：**
>
>由于OpenHarmony工程的编译构建流程中会拷贝kernel/linux/linux-\*\.\*的代码环境后进行打补丁动作，在使用OpenHarmony的版本级编译命令前，需要kernel/linux/linux-\*\.\*原代码环境。
>由于OpenHarmony工程的编译构建流程中会拷贝kernel/linux/linux-5.10的代码环境后进行打补丁动作，在使用OpenHarmony的版本级编译命令前，需要kernel/linux/linux-5.10原代码环境。
>
>根据不同系统工程，编译完成后会在out目录下的kernel目录中生成对应实际编译的内核，基于此目录的内核，进行对应的config修改，将最后生成的\.config文件cp到config仓对应的路径文件里，即可生效。