From: "Gadiyar, Anand via buildroot" <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: "Brattlof, Bryan" <bb@ti.com>, "Davis, Andrew" <afd@ti.com>,
Xuanhao Shi <X15000177@gmail.com>,
"buildroot@buildroot.org" <buildroot@buildroot.org>,
Giulio Benetti <giulio.benetti@benettiengineering.com>,
Romain Naour <romain.naour@gmail.com>
Subject: Re: [Buildroot] [PATCH v7 3/3] board/ti/am64x_sk: add new board
Date: Tue, 20 Dec 2022 19:29:56 +0000 [thread overview]
Message-ID: <70cc5213bb4d4e4d8e4b21b1c7122daf@ti.com> (raw)
In-Reply-To: <b88bb3e12f131de1038887a94211a64d@free.fr>
> From: Julien Olivain <ju.o@free.fr>
> > +
> > +These configurations will build a complete image and
> > +device tree blobs for the the TI AM64x_sk board.
>
> To avoid confusion between SK-AM64 and SK-AM64B, I suggest:
>
> 1. to add the board url in this readme.txt, for example,
> using the same comment as in the commit log:
> """
> More information about the board can be found at:
> https://www.ti.com/tool/SK-AM64
> """
>
> 2. add a note that:
> This configuration is for SK-AM64 only, since it's including:
> BR2_TARGET_TI_K3_IMAGE_GEN_SOC_TYPE="gp"
> The SK-AM64B [2] is not supported, as it would require "hs-fs".
>
> [2] https://www.ti.com/tool/SK-AM64B
>
Thanks for the review Julien!
The SK-AM64B wasn't around when we submitted the first patchset.
I expected a follow on patch to add the hs-fs support properly.
I'll clarify in the next revision that this series is for GP only. We'll need
some work to get the SK-AM64B supported and tested, and I'll try and
get that enabled after this initial series is merged.
I'll post a new series shortly with changes addressing review comments
from you and Thomas
- Anand
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-12-20 19:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 17:17 [Buildroot] [PATCH v7 0/3] add support for TI's AM64x boards Anand Gadiyar via buildroot
2022-12-06 17:17 ` [Buildroot] [PATCH v7 1/3] boot/ti-k3-r5-loader: add new package Anand Gadiyar via buildroot
2022-12-06 20:18 ` François Perrad
2022-12-11 20:06 ` Thomas Petazzoni via buildroot
2022-12-06 17:17 ` [Buildroot] [PATCH v7 2/3] boot/ti-k3-image-gen: " Anand Gadiyar via buildroot
2022-12-06 20:19 ` François Perrad
2022-12-11 20:09 ` Thomas Petazzoni via buildroot
2022-12-11 20:41 ` François Perrad
2022-12-11 21:22 ` Thomas Petazzoni via buildroot
2022-12-12 22:35 ` Gadiyar, Anand via buildroot
2022-12-19 20:56 ` Julien Olivain
2022-12-06 17:17 ` [Buildroot] [PATCH v7 3/3] board/ti/am64x_sk: add new board Anand Gadiyar via buildroot
2022-12-06 20:19 ` François Perrad
2022-12-11 20:12 ` Thomas Petazzoni via buildroot
2022-12-19 21:12 ` Julien Olivain
2022-12-20 19:29 ` Gadiyar, Anand via buildroot [this message]
[not found] ` <20230608063000.882363-1-patrick.oppenlander@gmail.com>
2023-06-08 13:29 ` [Buildroot] [PATCH v7 0/3] add support for TI's AM64x boards Gadiyar, Anand via buildroot
2023-06-08 15:59 ` Andreas Dannenberg via buildroot
2023-06-13 5:56 ` Patrick Oppenlander
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=70cc5213bb4d4e4d8e4b21b1c7122daf@ti.com \
--to=buildroot@buildroot.org \
--cc=X15000177@gmail.com \
--cc=afd@ti.com \
--cc=bb@ti.com \
--cc=gadiyar@ti.com \
--cc=giulio.benetti@benettiengineering.com \
--cc=ju.o@free.fr \
--cc=romain.naour@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox