From: Andy Yan <andy.yan@rock-chips.com>
To: u-boot@lists.denx.de
Subject: [PATCH 2/2] doc: rockchip: Fix reference the wrong defconfig name of ROC-CC-RK3308
Date: Thu, 26 Dec 2019 15:20:34 +0800 [thread overview]
Message-ID: <20191226072034.8594-1-andy.yan@rock-chips.com> (raw)
In-Reply-To: <20191226072004.8434-1-andy.yan@rock-chips.com>
The defconfig file for ROC-CC-RK3308 is roc-cc-rk3308_defconfig.
Fixes: 7f08bfb74f04 ("doc: rockchip: Add documentation for rk3308 based
boards")
Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
---
doc/README.rockchip | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/README.rockchip b/doc/README.rockchip
index dae4ebc8e4..ffab8ff417 100644
--- a/doc/README.rockchip
+++ b/doc/README.rockchip
@@ -50,7 +50,7 @@ Two RK3036 boards are supported:
Two RK3308 boards are supported:
- EVB RK3308 - use evb-rk3308 configuration
- - ROC-CC-RK3308 - use roc-rk3308-cc configuration
+ - ROC-CC-RK3308 - use roc-cc-rk3308 configuration
Two RK3328 board are supported:
@@ -106,7 +106,7 @@ For example:
- Compile U-Boot
=> cd /path/to/u-boot
=> export BL31=/path/to/rkbin/bin/rk33/rk3308_bl31_v2.22.elf
- => make roc-rk3308-cc_defconfig
+ => make roc-cc-rk3308_defconfig
=> make CROSS_COMPILE=aarch64-linux-gnu- all
=> ./tools/mkimage -n rk3308 -T rksd -d /path/to/rkbin/bin/rk33/rk3308_ddr_589MHz_uart2_m0_v1.26.bin idbloader.img
=> cat spl/u-boot-spl.bin >> idbloader.img
--
2.17.1
next prev parent reply other threads:[~2019-12-26 7:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-26 7:20 [PATCH 1/2] rockchip: rk3308: allow loading larger kernel Image Andy Yan
2019-12-26 7:20 ` Andy Yan [this message]
2019-12-26 12:25 ` [PATCH 2/2] doc: rockchip: Fix reference the wrong defconfig name of ROC-CC-RK3308 Kever Yang
2019-12-26 12:25 ` [PATCH 1/2] rockchip: rk3308: allow loading larger kernel Image Kever Yang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191226072034.8594-1-andy.yan@rock-chips.com \
--to=andy.yan@rock-chips.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.