From bca530b288a3b7abedd8974e01189adc46fe3a1a Mon Sep 17 00:00:00 2001 From: shawn_he Date: Mon, 5 Sep 2022 17:34:24 +0800 Subject: [PATCH] update doc Signed-off-by: shawn_he --- en/device-dev/subsystems/subsys-boot-overview.md | 8 ++------ en/device-dev/subsystems/subsys-usbservice-guide.md | 3 +-- 2 files changed, 3 insertions(+), 8 deletions(-) diff --git a/en/device-dev/subsystems/subsys-boot-overview.md b/en/device-dev/subsystems/subsys-boot-overview.md index f3befef53f..c1adc01318 100644 --- a/en/device-dev/subsystems/subsys-boot-overview.md +++ b/en/device-dev/subsystems/subsys-boot-overview.md @@ -57,9 +57,7 @@ The Startup subsystem consists of the following modules: - When porting a new chip platform, you need to add the **/vendor/etc/init/init.{hardware}.cfg** file that contains the platform-level initialization configuration. This file is used to implement platform-level initialization, for example, installing the ko driver and configuring information on the related **/proc** nodes. - > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
- - > The configuration file **init.cfg** must be in JSON format. + > **NOTE**: The configuration file **init.cfg** must be in JSON format. - bootstrap module: The zInit code must be configured in the link script. @@ -188,9 +186,7 @@ On each development board, you need to partition the memory to store the precedi This example assumes the **system** partition as the required partition on the Hi3516D V300 platform to illustrate the boot process. During this process, the init process reads the required fstab information, creates a block device node, and mounts it to the required partition. The following provides the key code snippets and log information as reference for debugging. - > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
- - > The code snippets below are exhibited in the logical sequence. They are not neighboring to each other in the source code. + > **NOTE**: The code snippets below are exhibited in the logical sequence. They are not neighboring to each other in the source code. 1. Obtain required device information. ``` diff --git a/en/device-dev/subsystems/subsys-usbservice-guide.md b/en/device-dev/subsystems/subsys-usbservice-guide.md index fb1e9c7c46..8f95d32cb3 100644 --- a/en/device-dev/subsystems/subsys-usbservice-guide.md +++ b/en/device-dev/subsystems/subsys-usbservice-guide.md @@ -34,8 +34,7 @@ int32_t et = g_usbClient.OpenDevice(device, pip); 5. Configure the USB interface. ```cpp -ret = g_usbClient.ClaimInterface(pip, interface, true); -**interface** indicates an interface of the USB device in **deviceList**. +ret = g_usbClient.ClaimInterface(pip, interface, true); // **interface** indicates an interface of the USB device in **deviceList**. ``` 6. Transfer data. -- GitLab