From cc781da4c4e3c249a35048645961cec1311c0edd Mon Sep 17 00:00:00 2001 From: Austin Date: Mon, 29 Aug 2022 11:44:38 +0000 Subject: [PATCH] update en/device-dev/porting/porting-smallchip-kernel-linux.md. Signed-off-by: Austin --- en/device-dev/porting/porting-smallchip-kernel-linux.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/en/device-dev/porting/porting-smallchip-kernel-linux.md b/en/device-dev/porting/porting-smallchip-kernel-linux.md index e71c2da835..a9f570e329 100644 --- a/en/device-dev/porting/porting-smallchip-kernel-linux.md +++ b/en/device-dev/porting/porting-smallchip-kernel-linux.md @@ -60,7 +60,7 @@ Based on the preceding process, the recommended verification procedure is as fol 1. Create a root file system image. - Create a root file system image **rootfs.img** by following instructions in [Adding a Chipset Solution and a Product Solution](../subsystems/subsys-build-mini-lite.md). As shown in the preceding figure, the startup process is closely related to the product configuration. You need to complete the following configuration when creating **rootfs.img**: + Create a root file system image **rootfs.img** by following instructions in [Adding a Chipset Solution and a Product Solution](../subsystems/subsys-build-all.md). As shown in the preceding figure, the startup process is closely related to the product configuration. You need to complete the following configuration when creating **rootfs.img**: - Component configuration -- GitLab