From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Xuanhao Shi <x-shi@ti.com>
Cc: Suniel Mahesh <sunil@amarulasolutions.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 3/4] board/am6x: add new board support
Date: Tue, 26 Jul 2022 20:58:20 +0200 [thread overview]
Message-ID: <20220726205820.0dfda49b@windsurf> (raw)
In-Reply-To: <20220726165041.17584-4-x-shi@ti.com>
Hello,
On Tue, 26 Jul 2022 11:50:40 -0500
Xuanhao Shi <x-shi@ti.com> wrote:
> Adds the board support for TI's AM6X SoCs after patch,
> Currently just AM64X to start.
>
> Signed-off-by: Xuanhao Shi <x-shi@ti.com>
> ---
> .../linux/ti_sdk_arm64_release_defconfig | 1983 +++++++++++++++++
> board/am6x/genimage.cfg | 27 +
> board/am6x/readme.txt | 41 +
> 3 files changed, 2051 insertions(+)
> create mode 100644 board/am6x/am64x/linux/ti_sdk_arm64_release_defconfig
> create mode 100644 board/am6x/genimage.cfg
> create mode 100644 board/am6x/readme.txt
>
> diff --git a/board/am6x/am64x/linux/ti_sdk_arm64_release_defconfig b/board/am6x/am64x/linux/ti_sdk_arm64_release_defconfig
> new file mode 100644
> index 0000000000..7000ee1170
> --- /dev/null
> +++ b/board/am6x/am64x/linux/ti_sdk_arm64_release_defconfig
Just board/am6x/am64x/linux.config
Does your board have an actual name? Because am64x is just the name of
the SoC, no?
> @@ -0,0 +1,1983 @@
> +CONFIG_SYSVIPC=y
> +CONFIG_POSIX_MQUEUE=y
> +CONFIG_NO_HZ_IDLE=y
> +CONFIG_HIGH_RES_TIMERS=y
> +CONFIG_PREEMPT=y
> +CONFIG_IRQ_TIME_ACCOUNTING=y
[...]
This is a huge config file, with obviously stuff that isn't needed for
your platform. Could you review it and strip it down to some reasonable
level? It enables zillions of drivers that make absolutely no sense for
a TI platform.
> +##################################################
> +# TI Baseport Config Options
> +##################################################
Please do not manually edit the kernel configuration file.
> diff --git a/board/am6x/readme.txt b/board/am6x/readme.txt
> new file mode 100644
> index 0000000000..b08c385146
> --- /dev/null
> +++ b/board/am6x/readme.txt
> @@ -0,0 +1,41 @@
> +Texas Instuments AM6X Evaluation Modules
> +
> +Description
> +===========
> +
> +These configurations will build a complete image and
> +device tree blobs for the the TI AM6X boards.
Which "boards" ? Normally, we have one readme.txt per board, as the
details are board-specific, such as where is the UART connector, how to
flash, etc.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-07-26 18:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 16:50 [Buildroot] [PATCH 0/4] add support for TI's AM6X SoCs Xuanhao Shi via buildroot
2022-07-26 16:50 ` [Buildroot] [PATCH 1/4] package/arm-gnu-toolchain: add version selection Xuanhao Shi via buildroot
2022-07-26 17:37 ` Thomas Petazzoni via buildroot
2022-07-26 19:32 ` Xuanhao Shi via buildroot
2022-07-26 20:07 ` Thomas Petazzoni via buildroot
2022-07-26 21:29 ` Xuanhao Shi via buildroot
2022-07-26 16:50 ` [Buildroot] [PATCH 2/4] package/k3-image-gen: new package Xuanhao Shi via buildroot
2022-07-26 18:55 ` Thomas Petazzoni via buildroot
2022-07-26 20:56 ` Xuanhao Shi via buildroot
2022-07-26 21:07 ` Thomas Petazzoni via buildroot
2022-07-26 21:31 ` Xuanhao Shi via buildroot
2022-07-27 8:22 ` Arnout Vandecappelle
2022-07-26 16:50 ` [Buildroot] [PATCH 3/4] board/am6x: add new board support Xuanhao Shi via buildroot
2022-07-26 18:58 ` Thomas Petazzoni via buildroot [this message]
2022-07-26 21:08 ` Xuanhao Shi via buildroot
2022-07-27 8:32 ` Arnout Vandecappelle
2022-07-26 16:50 ` [Buildroot] [PATCH 4/4] configs/am64x_sk_defconfig: add new defconfig Xuanhao Shi via buildroot
2022-07-26 19:00 ` Thomas Petazzoni via buildroot
2022-07-26 21:11 ` Xuanhao Shi via buildroot
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=20220726205820.0dfda49b@windsurf \
--to=buildroot@buildroot.org \
--cc=sunil@amarulasolutions.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=x-shi@ti.com \
/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.