Skip to content

D
Docs

OpenHarmony / Docs
1 年多 前同步成功

通知 159
Star 292
Fork 28
D
Docs
未验证 提交 a9f36f19 编写于 作者: O openharmony_ci 提交者： Gitee
浏览文件
操作

!4203 Modify the chip name to product name 

Merge pull request !4203 from frank_bing/cherry-pick-1653040457
上级 4abcb618 3676165e
显示空白变更内容
内联 并排
Showing with 34 addition and 34 deletion
en/contribute/OpenHarmony-hdf-coding-guide.md
浏览文件 @ a9f36f19
......@@ -139,10 +139,10 @@ The driver loading information required by the HDF comes from the driver device
```bash
$openharmony_src_root/vendor/hisilicon/hispark_taurus/hdf_config # Directory for storing the kernel-mode configuration file. There are no user-mode configuration files.
$openharmony_src_root/vendor/hisilicon/Hi3516DV300/hdf_config/khdf # Directory for storing the kernel-mode configuration file.
$openharmony_src_root/vendor/hisilicon/Hi3516DV300/hdf_config/uhdf # Directory for storing the user-mode configuration file.
$openharmony_src_root/vendor/hisilicon/Hi3516DV300/hdf_config/khdf/device_info/device_info.hcs # Device description file of the kernel-mode driver.
$openharmony_src_root/vendor/hisilicon/Hi3516DV300/hdf_config/khdf/lcd/lcd_config.hcs # Private configuration file of the kernel-mode driver.
$openharmony_src_root/vendor/hisilicon/hispark_taurus_standard/hdf_config/khdf # Directory for storing the kernel-mode configuration file.
$openharmony_src_root/vendor/hisilicon/hispark_taurus_standard/hdf_config/uhdf # Directory for storing the user-mode configuration file.
$openharmony_src_root/vendor/hisilicon/hispark_taurus_standard/hdf_config/khdf/device_info/device_info.hcs # Device description file of the kernel-mode driver.
$openharmony_src_root/vendor/hisilicon/hispark_taurus_standard/hdf_config/khdf/lcd/lcd_config.hcs # Private configuration file of the kernel-mode driver.
```
#### [Rule] Use existing configuration information and inherit existing configuration templates during driver configuration.
......@@ -373,9 +373,9 @@ If a driver has private configurations, you can add a driver configuration file
[Example]
```bash
$openharmony_src_root/vendor/hisilicon/Hi3516DV300/hdf_config/khdf/sample/sample_config.hcs # Correct. The private configuration file is stored in the sample directory.
$openharmony_src_root/vendor/hisilicon/hispark_taurus_standard/hdf_config/khdf/sample/sample_config.hcs # Correct. The private configuration file is stored in the sample directory.
$openharmony_src_root/vendor/hisilicon/Hi3516DV300/hdf_config/khdf/sample_config.hcs # Incorrect. The private configuration file is placed in the root directory.
$openharmony_src_root/vendor/hisilicon/hispark_taurus_standard/hdf_config/khdf/sample_config.hcs # Incorrect. The private configuration file is placed in the root directory.
```
#### [Rule] Add the private configuration file of a driver to the hdf.hcs file in the hdf_config directory.
......
en/device-dev/driver/driver-peripherals-audio-des.md
浏览文件 @ a9f36f19
......@@ -273,7 +273,7 @@ int32_t CodecDaiHwParams(const struct AudioCard *card, const struct AudioPcmHwPa
#### Registering and Binding Codec to HDF
This process depends on the driver implementation mode of the HDF. For details, see [HDF](https://gitee.com/openharmony/docs/blob/master/en/device-dev/driver/driver-hdf.md).
This process depends on the driver implementation mode of the HDF. For details, see [HDF](https://gitee.com/openharmony/docs/blob/master/en/device-dev/driver/Readme-EN.md).
Fill in the **g_codecDriverEntry** structure. Ensure that the value of **moduleName** is the same as that in **device_info.hcs**. Implement the pointers to the **Bind**, **Init**, and **Release** functions.
......@@ -335,7 +335,7 @@ Configure the driver node, loading sequence, and service name in the .hcs file.
Path of the standard-system configuration file:
**vendor/hisilicon/Hi3516DV300/hdf_config/khdf/**
**vendor/hisilicon/hispark_taurus_standard/hdf_config/khdf/**
Path of the small-system configuration file:
......@@ -779,7 +779,7 @@ int32_t Tfa9879DaiHwParams(const struct AudioCard *card, const struct AudioPcmHw
#### Registering and Binding Accessory to HDF
This process depends on the driver implementation mode of the HDF. For details, see [HDF](https://gitee.com/openharmony/docs/blob/master/en/device-dev/driver/driver-hdf.md).
This process depends on the driver implementation mode of the HDF. For details, see [HDF](https://gitee.com/openharmony/docs/blob/master/en/device-dev/driver/Readme-EN.md).
Fill in the **g_tfa9879DriverEntry** structure. Ensure that the value of **moduleName** is the same as that in **device_info.hcs**. Implement the pointers to the **Bind**, **Init**, and **Release** functions.
......@@ -900,7 +900,7 @@ int32_t Hi3516DmaPointer(struct PlatformData *data, uint32_t *pointer);
#### Registering and Binding Platform to HDF
This process depends on the driver implementation mode of the HDF. For details, see [HDF](https://gitee.com/openharmony/docs/blob/master/en/device-dev/driver/driver-hdf.md).
This process depends on the driver implementation mode of the HDF. For details, see [HDF](https://gitee.com/openharmony/docs/blob/master/en/device-dev/driver/Readme-EN.md).
- Fill in the **g_platformDriverEntry** structure.
- Ensure that the value of **moduleName** is the same as that in **device_info.hcs**.
......@@ -1064,7 +1064,7 @@ int32_t DaiStartup(const struct AudioCard *card, const struct DaiDevice *device)
#### Registering and Binding DAI to HDF
This process depends on the driver implementation mode of the HDF. For details, see [HDF](https://gitee.com/openharmony/docs/blob/master/en/device-dev/driver/driver-hdf.md).
This process depends on the driver implementation mode of the HDF. For details, see [HDF](https://gitee.com/openharmony/docs/blob/master/en/device-dev/driver/Readme-EN.md).
- Fill in the **g_daiDriverEntry** structure.
- Ensure that the value of **moduleName** is the same as that in **device_info.hcs**.
......@@ -1215,7 +1215,7 @@ HCS Files and Directory
```
Standard system:
vendor/hisilicon/Hi3516DV300/
vendor/hisilicon/hispark_taurus_standard/
└── hdf_config
└── khdf
├── audio
......
en/device-dev/get-code/gettools-acquire.md
浏览文件 @ a9f36f19
......@@ -156,7 +156,7 @@ Run the following script to start building for standard-system devices \(referen
./build.sh --product-name {product_name} --ccache
```
**product\_name** indicates the platform supported by the current distribution, for example, Hi3516DV300 and rk3568.
**product\_name** indicates the platform supported by the current distribution, for example, hispark_taurus_standard and rk3568.
Files generated during building are stored in the **out/{device_name}/** directory, and the generated image is stored in the **out/{device_name}/packages/phone/images/** directory.
......
en/device-dev/porting/porting-linux-kernel.md
浏览文件 @ a9f36f19
......@@ -84,7 +84,7 @@ The following uses Raspberry Pi 3b \(BCM2837\) as an example to describe how to
# Configure the build environment, and use clang provided by the project to build the Raspberry Pi kernel source code.
export PATH=$PROJ_ROOT/prebuilts/clang/ohos/linux-x86_64/llvm/bin:$PROJ_ROOT/prebuilts/gcc/linux-x86/arm/gcc-linaro-7.5.0-arm-linux-gnueabi/bin/:$PATH
export MAKE_OPTIONS="ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- CC=clang HOSTCC=clang"
export PRODUCT_PATH=vendor/hisilicon/Hi3516DV300
export PRODUCT_PATH=vendor/hisilicon/hispark_taurus_standard
```
3. Comment out the flags that cannot be recognized by **clang**.
......
en/device-dev/quick-start/quickstart-lite-reference.md
浏览文件 @ a9f36f19
......@@ -11,7 +11,7 @@
```
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
> _name_ indicates the product name, for example, **Hi3516D V300** and **rk3568**.
> _name_ indicates the product name, for example, **hispark_taurus_standard** and **rk3568**.
2. Check the build result. After the build is complete, the following information is displayed in the log:
......
en/device-dev/quick-start/quickstart-standard-reference.md
浏览文件 @ a9f36f19
......@@ -11,7 +11,7 @@
```
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
> _name_ indicates the product name, for example, **Hi3516D V300** and **rk3568**.
> _name_ indicates the product name, for example, **hispark_taurus_standard** and **rk3568**.
2. Check the build result. After the build is complete, the following information is displayed in the log:
......
en/device-dev/subsystems/subsys-build-standard-large.md
浏览文件 @ a9f36f19
......@@ -87,7 +87,7 @@ The process to build OpenHarmony is as follows:
./build.sh --product-name {product_name}
```
**product\_name** indicates the product supported by the current distribution, for example, Hi3516D V300.
**product\_name** indicates the product supported by the current distribution, for example, hispark_taurus_standard.
The image generated after build is stored in the **out/{device_name}/packages/phone/images/** directory.
......
zh-cn/contribute/OpenHarmony-hdf-coding-guide.md
浏览文件 @ a9f36f19
......@@ -139,10 +139,10 @@ HDF框架加载驱动所需要的信息来源于HDF框架定义的驱动设备
```bash
$openharmony_src_root/vendor/hisilicon/hispark_taurus/hdf_config # 内核态配置文件目录，无用户态
$openharmony_src_root/vendor/hisilicon/Hi3516DV300/hdf_config/khdf # 内核态配置文件目录
$openharmony_src_root/vendor/hisilicon/Hi3516DV300/hdf_config/uhdf # 用户态配置文件目录
$openharmony_src_root/vendor/hisilicon/Hi3516DV300/hdf_config/khdf/device_info/device_info.hcs # 内核态驱动设备描述配置文件
$openharmony_src_root/vendor/hisilicon/Hi3516DV300/hdf_config/khdf/lcd/lcd_config.hcs # 内核态驱动私有配置文件
$openharmony_src_root/vendor/hisilicon/hispark_taurus_standard/hdf_config/khdf # 内核态配置文件目录
$openharmony_src_root/vendor/hisilicon/hispark_taurus_standard/hdf_config/uhdf # 用户态配置文件目录
$openharmony_src_root/vendor/hisilicon/hispark_taurus_standard/hdf_config/khdf/device_info/device_info.hcs # 内核态驱动设备描述配置文件
$openharmony_src_root/vendor/hisilicon/hispark_taurus_standard/hdf_config/khdf/lcd/lcd_config.hcs # 内核态驱动私有配置文件
```
#### 【规则】驱动设备在配置时，应当充分使用已有的配置信息，继承已有的配置模板
......@@ -373,9 +373,9 @@ root {
【样例】
```bash
$openharmony_src_root/vendor/hisilicon/Hi3516DV300/hdf_config/khdf/sample/sample_config.hcs # 正确，将私有配置文件放置在了sample目录下
$openharmony_src_root/vendor/hisilicon/hispark_taurus_standard/hdf_config/khdf/sample/sample_config.hcs # 正确，将私有配置文件放置在了sample目录下
$openharmony_src_root/vendor/hisilicon/Hi3516DV300/hdf_config/khdf/sample_config.hcs # 错误，将私有配置文件放置在了配置根目录下
$openharmony_src_root/vendor/hisilicon/hispark_taurus_standard/hdf_config/khdf/sample_config.hcs # 错误，将私有配置文件放置在了配置根目录下
```
#### 【规则】应当将驱动私有配置文件包含到hdf_config配置目录下的hdf.hcs文件中
......
zh-cn/device-dev/driver/driver-peripherals-audio-des.md
浏览文件 @ a9f36f19
......@@ -335,7 +335,7 @@ hcs中配置驱动节点、加载顺序、服务名称等。hcs语法可参考HD
标准系统配置文件路径：
vendor/hisilicon/Hi3516DV300/hdf_config/khdf/
vendor/hisilicon/hispark_taurus_standard/hdf_config/khdf/
小型系统配置文件路径：
......@@ -1215,7 +1215,7 @@ hcs文件与目录
```
标准系统：
vendor/hisilicon/Hi3516DV300/
vendor/hisilicon/hispark_taurus_standard/
└── hdf_config
└── khdf
├── audio
......
zh-cn/device-dev/get-code/gettools-acquire.md
浏览文件 @ a9f36f19
......@@ -110,7 +110,7 @@ hb set
./build.sh --product-name {product_name} --ccache
```
{product_name}为当前版本支持的平台。比如：Hi3516DV300和rk3568等。
{product_name}为当前版本支持的平台。比如：hispark_taurus_standard和rk3568等。
编译所生成的文件都归档在out/{device_name}/目录下，结果镜像输出在 out/{device_name}/packages/phone/images/ 目录下。
......
zh-cn/device-dev/porting/porting-linux-kernel.md
浏览文件 @ a9f36f19
......@@ -96,7 +96,7 @@ OH内核态层 = OH Linux内核 + OH内核态特性（可选特性或者必选
# 配置编译环境,使用工程项目自带的clang
export PATH=$PROJ_ROOT/prebuilts/clang/ohos/linux-x86_64/llvm/bin:$PROJ_ROOT/prebuilts/gcc/linux-x86/arm/gcc-linaro-7.5.0-arm-linux-gnueabi/bin/:$PATH
export MAKE_OPTIONS="ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- CC=clang HOSTCC=clang"
export PRODUCT_PATH=vendor/hisilicon/Hi3516DV300
export PRODUCT_PATH=vendor/hisilicon/hispark_taurus_standard
```
3. 注释掉clang不识别的flag。
......
zh-cn/device-dev/quick-start/quickstart-lite-reference.md
浏览文件 @ a9f36f19
......@@ -11,7 +11,7 @@
```
> ![icon-note.gif](public_sys-resources/icon-note.gif) **说明：**
> _name_为产品名称，例如Hi3516DV300、rk3568等。
> _name_为产品名称，例如hispark_taurus_standard、rk3568等。
2. 检查编译结果。编译完成后，log中显示如下：
......
zh-cn/device-dev/quick-start/quickstart-standard-reference.md
浏览文件 @ a9f36f19
......@@ -11,7 +11,7 @@
```
> ![icon-note.gif](public_sys-resources/icon-note.gif) **说明：**
> _name_为产品名称，例如Hi3516DV300、rk3568等。
> _name_为产品名称，例如hispark_taurus_standard、rk3568等。
2. 检查编译结果。编译完成后，log中显示如下：
......
zh-cn/device-dev/subsystems/subsys-build-standard-large.md
浏览文件 @ a9f36f19
......@@ -5,7 +5,7 @@
编译构建子系统提供了一个基于gn和ninja的编译构建框架。主要提供以下功能：
- 构建不同芯片平台的产品。如：Hi3516DV300平台。
- 构建不同芯片平台的产品。如：hispark_taurus_standard平台。
- 根据产品配置，按照组件组装并打包产品特性的能力。
......@@ -89,14 +89,14 @@ OpenHarmony侧的编译构建流程主要包括编译命令行解析，调用gn
./build.sh --product-name {product_name}
```
{product_name}为当前版本支持的平台。比如：Hi3516DV300等。
{product_name}为当前版本支持的平台。比如：hispark_taurus_standard等。
编译完成后，结果镜像保存在 out/{device_name}/packages/phone/images/ 目录下。
- 编译命令支持选项：
```
--product-name # 必须 编译的产品名称，如：Hi3516DV300
--product-name # 必须 编译的产品名称，如：hispark_taurus_standard
--build-target # 可选 指定编译目标，可以指定多个
--gn-args # 可选 gn参数，支持指定多个
--ccache # 可选 编译使用ccache，需要本地安装ccache
......@@ -400,7 +400,7 @@ ohos_shared_library("module2") {
该文件定义了有哪些子系统以及这些子系统所在文件夹路径，添加子系统时需要说明子系统path与name，分别表示子系统路径和子系统名。
4. 在//vendor/{product_company}/{product-name}目录下的产品配置如product-name是Hi3516DV300时，在config.json中添加对应的部件，直接添加到原有部件后即可。
4. 在//vendor/{product_company}/{product-name}目录下的产品配置如product-name是hispark_taurus_standard时，在config.json中添加对应的部件，直接添加到原有部件后即可。
```
{
......
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或