From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] configs: add defconfig for TS-4600
Date: Thu, 27 Oct 2016 10:53:19 +0200 [thread overview]
Message-ID: <20161027105319.6788479a@free-electrons.com> (raw)
In-Reply-To: <20161027000807.20206-2-sebastien.bourdelin@savoirfairelinux.com>
Hello,
(Adding Fabio Estevam in Cc, since he has lots of experience with
Freescale stuff, of course.)
On Wed, 26 Oct 2016 20:08:06 -0400, Sebastien Bourdelin wrote:
> board/technologic/ts4600/genimage.cfg | 18 +++++
> board/technologic/ts4600/linux.fragment | 2 +
> board/technologic/ts4600/post-image.sh | 18 +++++
> board/technologic/ts4600/readme.txt | 57 +++++++++++++++
> boot/Config.in | 1 +
> boot/ts4600-bootrom/Config.in | 6 ++
> boot/ts4600-bootrom/ts4600-bootrom-sign | 124 ++++++++++++++++++++++++++++++++
> boot/ts4600-bootrom/ts4600-bootrom.mk | 33 +++++++++
Please separate the boot/ts4600-bootrom/ addition from the addition of
the board configuration (i.e, separate patches).
> diff --git a/boot/ts4600-bootrom/ts4600-bootrom-sign b/boot/ts4600-bootrom/ts4600-bootrom-sign
> new file mode 100755
> index 0000000..d91c10f
> --- /dev/null
> +++ b/boot/ts4600-bootrom/ts4600-bootrom-sign
> @@ -0,0 +1,124 @@
> +#!/bin/bash
> +#
> +# Copyright (C) 2016 Savoir-Faire Linux, Inc
> +# Copyright (C) 2013 Technologic System, Inc
> +# Author: ts-kris <https://github.com/ts-kris>
> +# Author: Sebastien Bourdelin <sebastien.bourdelin@savoirfairelinux.com>
> +#
> +# This tool signs a bootstream and add a BCB (Boot Control Block) to be used on i.MX28 SoC.
> +# It is based on the install_bootstream tool from Technologic System:
> +# https://github.com/embeddedarm/linux-2.6.35.3-imx28/blob/master/install_bootstream
Why don't we use this tool instead?
Is this tool really specific to the ts4600 platform, or is it
generally useful on i.MX28 platforms?
> diff --git a/boot/ts4600-bootrom/ts4600-bootrom.mk b/boot/ts4600-bootrom/ts4600-bootrom.mk
> new file mode 100644
> index 0000000..681152d
> --- /dev/null
> +++ b/boot/ts4600-bootrom/ts4600-bootrom.mk
> @@ -0,0 +1,33 @@
> +################################################################################
> +#
> +# ts4600-bootrom
> +#
> +################################################################################
I dislike this new package, because we already have a package for
mxs-bootlets, in boot/mxs-bootlets/.
Could you instead ask embeddedarm people to have a separate repository
for their version of mxs-bootlets, instead of mixing that in the kernel
repository, which is really awful? That would allow you to re-use the
existing mxs-bootlets package.
> diff --git a/configs/ts4600_defconfig b/configs/ts4600_defconfig
> new file mode 100644
> index 0000000..21f5d7f
> --- /dev/null
> +++ b/configs/ts4600_defconfig
> @@ -0,0 +1,20 @@
> +BR2_arm=y
> +BR2_TOOLCHAIN_EXTERNAL=y
> +BR2_TOOLCHAIN_EXTERNAL_CUSTOM=y
> +BR2_TOOLCHAIN_EXTERNAL_DOWNLOAD=y
> +BR2_TOOLCHAIN_EXTERNAL_URL="ftp://ftp.embeddedarm.com/ts-arm-sbc/ts-7600-linux/cross-toolchains/imx28-cross-glibc.tar.bz2"
> +BR2_TOOLCHAIN_EXTERNAL_GCC_4_4=y
> +BR2_TOOLCHAIN_EXTERNAL_CUSTOM_GLIBC=y
> +BR2_TOOLCHAIN_EXTERNAL_CXX=y
Why are you using this toolchain rather than the default Buildroot
toolchain?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-10-27 8:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 0:08 [Buildroot] [PATCH 0/2] add the TS-4600 board support Sebastien Bourdelin
2016-10-27 0:08 ` [Buildroot] [PATCH 1/2] configs: add defconfig for TS-4600 Sebastien Bourdelin
2016-10-27 8:53 ` Thomas Petazzoni [this message]
2016-10-27 10:44 ` Fabio Estevam
2016-10-27 0:08 ` [Buildroot] [PATCH 2/2] ts4600-tshwctl: add ts4600-tshwctl package Sebastien Bourdelin
2016-10-27 8:41 ` 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=20161027105319.6788479a@free-electrons.com \
--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 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.