Lines Matching +full:directory +full:- +full:based

1 # Patch<a name="EN-US_TOPIC_0000001078264110"></a>
3 -   [Introduction](#section11660541593)
4 -   [Driver Patches for a Specific Chip Architecture (such as Hi3516D V300)](#section1521510717399)
5 -   [Directory Structure](#section21571344112)
6 -   [Usage](#section1393789267)
7 -   [Build](#section19369206113115)
8 -   [Repositories Involved](#section27639463106)
12 Evolved from the open-source Linux kernel LTS 4.19.y and 5.10.y, the OpenHarmony Linux kernel has i…
14 …nel website](https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=linux-4.19.y).
16 …nel website](https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=linux-5.10.y).
18 During the build process, you can merge the driver code based on the chip platform and build the ke…
26 ## Directory Structure<a name="section21571344112"></a>
30 ├── linux-4.19				# linux-4.19 patches
32 │   │		└── hdf.patch		# linux-4.19 HDF patches
34 │   		└── hi3516dv300.patch	# linux-4.19 Hi3516D V300 SOC patches
35 └── linux-5.10
37     │		└── hdf.patch		# linux-5.10 HDF patches
39     │		└── hi3516dv300.patch	# linux-5.10 Hi3516D V300 SOC patches
41     		├── kernel.patch		# linux-5.10 rk3568 SOC patches
42     		└── hdf.patch		# linux-5.10 rk3568 customized HDF patches
59 …Place the patches for the chip component in the corresponding path based on the path and naming ru…
68 …Place the **config** file for the chip component in the corresponding path based on the path and n…
77 …ernel/linux/linux-\*\.\*** is copied. Before using the version-level build command of OpenHarmony,…
79 …nel built is generated in the **kernel** directory under the **out** directory. Modify the **confi…
89 ./build.sh --product-name Hi3516DV300              # Build the Hi3516D V300 image.
90     --build-target build_kernel                    # Build the uImage kernel image of Hi3516D V300.
91     --gn-args linux_kernel_version=\"linux-5.10\"  # Build the specified kernel version.