提交 7979845d 编写于 作者: A Austin 提交者: Gitee

update en/device-dev/porting/porting-chip-prepare-knows.md.

Signed-off-by: NAustin <liaozhiqi7@huawei.com>
上级 6036e9c2
...@@ -79,6 +79,6 @@ The **device** directory of OpenHarmony is the adaptation directory for the ba ...@@ -79,6 +79,6 @@ The **device** directory of OpenHarmony is the adaptation directory for the ba
## Porting Specifications<a name="section187870185219"></a> ## Porting Specifications<a name="section187870185219"></a>
- The porting must comply with the basic OpenHarmony principles described in [Contribution](https://gitee.com/openharmony/docs/blob/master/en/contribute/contribution.md). - The porting must comply with the basic OpenHarmony principles described in [Contribution](../../contribute/contribution.md).
- The code required for third-party SoC adaptation is stored in the **device**, **vendor**, and **arch** directories. Naming and usage of these directories must comply with specified naming and usage specifications. For details, see [Directory Specifications](porting-chip-kernel-overview.md) and [Board-Level Directory Specifications](porting-chip-board-overview.md#section6204129143013). - The code required for third-party SoC adaptation is stored in the **device**, **vendor**, and **arch** directories. Naming and usage of these directories must comply with specified naming and usage specifications. For details, see [Directory Specifications](porting-chip-kernel-overview.md) and [Board-Level Directory Specifications](porting-chip-board-overview.md#section6204129143013).
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册