Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 3/3] board: Add Tinker RK388 board support
Date: Thu, 23 Nov 2017 22:45:24 +0100	[thread overview]
Message-ID: <20171123224524.1e933449@windsurf.lan> (raw)
In-Reply-To: <1510997329-4111-3-git-send-email-jagan@amarulasolutions.com>

Hello,

On Sat, 18 Nov 2017 10:28:49 +0100, Jagan Teki wrote:
> Add Tinker board, from rk3288 family SOC.
> 
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>

Same question about the title: shouldn't it be RK3288 ?


> diff --git a/board/asus/tinker/post-build.sh b/board/asus/tinker/post-build.sh
> new file mode 100755
> index 0000000..8108ed8
> --- /dev/null
> +++ b/board/asus/tinker/post-build.sh
> @@ -0,0 +1,9 @@
> +#!/bin/sh
> +
> +MKIMAGE=$HOST_DIR/bin/mkimage

host-uboot-tools is needed.


> diff --git a/configs/asus_tinker_rk3288_defconfig b/configs/asus_tinker_rk3288_defconfig
> new file mode 100644
> index 0000000..7f20cf1
> --- /dev/null
> +++ b/configs/asus_tinker_rk3288_defconfig
> @@ -0,0 +1,55 @@
> +# Architecture
> +BR2_arm=y
> +BR2_cortex_a17=y
> +BR2_ARM_FPU_NEON_VFPV4=y
> +
> +# Linux headers same as kernel, a 4.12 series
> +BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_12=y
> +
> +# Toolchain
> +BR2_TOOLCHAIN_BUILDROOT_GLIBC=y
> +BR2_TOOLCHAIN_BUILDROOT_CXX=y

Keep the default toolchain configuration.

> +# Kernel
> +BR2_LINUX_KERNEL=y
> +BR2_LINUX_KERNEL_CUSTOM_VERSION=y
> +BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.12"
> +BR2_LINUX_KERNEL_DEFCONFIG="multi_v7"
> +BR2_LINUX_KERNEL_UIMAGE=y
> +BR2_LINUX_KERNEL_UIMAGE_LOADADDR="0x02000000"
> +BR2_LINUX_KERNEL_DTS_SUPPORT=y
> +BR2_LINUX_KERNEL_INTREE_DTS_NAME="rk3288-tinker"
> +BR2_LINUX_KERNEL_INSTALL_TARGET=y
> +
> +# Filesystem
> +BR2_TARGET_GENERIC_HOSTNAME="tinker-rk3288"
> +BR2_TARGET_GENERIC_ISSUE="Welcome to TINKER RK3288!"
> +BR2_TARGET_ROOTFS_EXT2=y
> +BR2_TARGET_ROOTFS_EXT2_4=y
> +BR2_TARGET_ROOTFS_EXT2_SIZE="512M"
> +BR2_PACKAGE_HOST_DOSFSTOOLS=y
> +BR2_PACKAGE_HOST_GENIMAGE=y
> +BR2_PACKAGE_HOST_MTOOLS=y
> +BR2_ROOTFS_POST_IMAGE_SCRIPT="support/scripts/genimage.sh"
> +BR2_ROOTFS_POST_SCRIPT_ARGS="-c board/asus/tinker/genimage.cfg"
> +BR2_ROOTFS_POST_BUILD_SCRIPT="board/asus/tinker/post-build.sh"
> +
> +# qt5
> +BR2_PACKAGE_QT5=y
> +BR2_PACKAGE_QT5BASE_EXAMPLES=y
> +BR2_PACKAGE_QT5BASE_GUI=y
> +BR2_PACKAGE_QT5BASE_EGLFS=y
> +BR2_PACKAGE_MALI_T76X=y

And keep the configuration minimal by not adding Qt5/OpenGL.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-11-23 21:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-18  9:28 [Buildroot] [PATCH v4 1/3] uboot: Use BR2_TARGET_UBOOT_SPL_NAME for TPL name Jagan Teki
2017-11-18  9:28 ` [Buildroot] [PATCH v4 2/3] board: Add Vyasa RK388 board support Jagan Teki
2017-11-22 18:02   ` Jagan Teki
2017-11-23 21:43   ` Thomas Petazzoni
2017-11-29  7:07     ` Jagan Teki
2017-11-29  8:20       ` Thomas Petazzoni
2017-11-18  9:28 ` [Buildroot] [PATCH v4 3/3] board: Add Tinker " Jagan Teki
2017-11-23 21:45   ` Thomas Petazzoni [this message]
2017-11-23 21:40 ` [Buildroot] [PATCH v4 1/3] uboot: Use BR2_TARGET_UBOOT_SPL_NAME for TPL name Thomas Petazzoni

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=20171123224524.1e933449@windsurf.lan \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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