From: Nicolas Boulenguez <nicolas@debian.org>
To: u-boot@lists.denx.de
Subject: [PATCH] configs: add PineTab defconfig
Date: Sun, 7 Mar 2021 13:53:56 +0100 [thread overview]
Message-ID: <YETM5Nx10Fi8uwN2@nicolasthinkpad> (raw)
From: Arnaud Ferraris <arnaud.ferraris@collabora.com>
The PineTab device-tree is already in u-boot, this commit adds the corresponding
defconfig, based on pinephone_defconfig.
Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>
--- a/board/sunxi/MAINTAINERS
+++ b/board/sunxi/MAINTAINERS
@@ -471,6 +471,11 @@ M: Samuel Holland <samuel@sholland.org>
S: Maintained
F: configs/pinephone_defconfig
+PINETAB BOARD
+M: Arnaud Ferraris <arnaud.ferraris@collabora.com>
+S: Maintained
+F: configs/pinetab_defconfig
+
R16 EVB PARROT BOARD
M: Quentin Schulz <quentin.schulz@free-electrons.com>
S: Maintained
--- /dev/null
+++ b/configs/pinetab_defconfig
@@ -0,0 +1,21 @@
+CONFIG_ARM=y
+CONFIG_ARCH_SUNXI=y
+CONFIG_SPL=y
+CONFIG_IDENT_STRING=""
+CONFIG_MACH_SUN50I=y
+CONFIG_SUNXI_DRAM_LPDDR3_STOCK=y
+CONFIG_DRAM_CLK=552
+CONFIG_DRAM_ZQ=3881949
+CONFIG_MMC_SUNXI_SLOT_EXTRA=2
+# CONFIG_VIDEO_DE2 is not set
+CONFIG_DEFAULT_DEVICE_TREE="sun50i-a64-pinetab"
+# CONFIG_SYS_MALLOC_CLEAR_ON_INIT is not set
+CONFIG_BOOTDELAY=0
+CONFIG_SYS_CONSOLE_INFO_QUIET=y
+# CONFIG_DISPLAY_CPUINFO is not set
+# CONFIG_DISPLAY_BOARDINFO is not set
+# CONFIG_SPL_RAW_IMAGE_SUPPORT is not set
+# CONFIG_SPL_BANNER_PRINT is not set
+# CONFIG_SPL_POWER_SUPPORT is not set
+# CONFIG_NET is not set
+# CONFIG_EFI_LOADER is not set
next reply other threads:[~2021-03-07 12:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 12:53 Nicolas Boulenguez [this message]
2021-03-07 13:58 ` [PATCH] configs: add PineTab defconfig Peter Robinson
2021-03-07 20:34 ` Vagrant Cascadian
2021-03-07 22:15 ` Andre Przywara
2021-03-08 0:12 ` Andre Przywara
2021-03-08 0:13 ` Icenowy Zheng
2021-03-13 15:32 ` Arnaud Ferraris
-- strict thread matches above, loose matches on Subject: below --
2021-09-06 21:06 Arnaud Ferraris
2021-09-06 23:47 ` Andre Przywara
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=YETM5Nx10Fi8uwN2@nicolasthinkpad \
--to=nicolas@debian.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox