From 09597b0e0363da9733139e0a39e7f870f3eee49a Mon Sep 17 00:00:00 2001 From: liyan Date: Fri, 21 Apr 2023 09:29:15 +0000 Subject: [PATCH] update en/device-dev/porting/Readme-EN.md. https://gitee.com/openharmony/community/blob/master/sig/sig_devboard/sig_devboard.md Signed-off-by: liyan --- en/device-dev/porting/Readme-EN.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/en/device-dev/porting/Readme-EN.md b/en/device-dev/porting/Readme-EN.md index f86cab4298..18e068c40c 100644 --- a/en/device-dev/porting/Readme-EN.md +++ b/en/device-dev/porting/Readme-EN.md @@ -1,6 +1,6 @@ ## Introduction -OpenHarmony has organized a Special Interest Group (SIG) [SIG_DevBoard](https://gitee.com/openharmony/community/blob/master/sig/sig-devboard/sig_devboard.md) to provide support for third-party development boards. +OpenHarmony has organized a Special Interest Group (SIG) [SIG_DevBoard](https://gitee.com/openharmony/community/blob/master/sig/sig_devboard/sig_devboard.md) to provide support for third-party development boards. Before learning about how to port the code of a development board, take a look at the device classification on OpenHarmony. The porting methods vary according to the device type. -- GitLab