From: Bryan Brattlof via buildroot <buildroot@buildroot.org>
To: Paresh Bhagat <p-bhagat@ti.com>
Cc: Xuanhao Shi <X15000177@gmail.com>, Gyan Gupta <g-gupta@ti.com>,
Chirag Shilwant <c-shilwant@ti.com>,
Syed Mohammed Khasim <khasim@ti.com>,
buildroot@buildroot.org, Sai Sree Kartheek Adivi <s-adivi@ti.com>,
Anand Gadiyar <gadiyar@ti.com>
Subject: Re: [Buildroot] [RFC, 1/1] configs/am62x-sk: Add fragment for TI tree integration
Date: Tue, 30 Apr 2024 09:54:48 -0500 [thread overview]
Message-ID: <20240430145448.yhg6r64ohsfofeqv@bryanbrattlof.com> (raw)
In-Reply-To: <20240429092326.3247116-1-p-bhagat@ti.com>
On April 29, 2024 thus sayeth Paresh Bhagat via buildroot:
> This commit introduces a new fragment config aimed at integration of TI trees
> into the existing configuration for am62x-sk. The fragment config is designed
> to be merged with the current ti_am62x_sk_defconfig, enabling transition from
> mainline to TI versions for U-boot and kernel.
>
> The fragment config will be merged with existing ti_my_am62x_sk_defconfig
> using merge-config.sh script present in support/kconfig using following
> command.
>
> ./support/kconfig/merge-config.sh configs/ti_am62x_sk_defconfig configs/ti_am62x_sk.config
>
> It effectively changes uboot and kernel source from mainline version to TI
> version hosted here
>
> https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/?h=ti-linux-6.1.y
> https://git.ti.com/cgit/ti-u-boot/ti-u-boot/?h=ti-u-boot-2023.04
>
> Furthermore, as ti-uboot 2023.04 is used, kernel Image and dtb is expected
> in rootfs/boot/ and rootfs/boot/dtb/ti respectively. So add a new post-build
> script to copy these files to desired location.
>
> Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Thanks for the patch. My worry is these changes will only be needed for
the brief time the 9.2 SDK is relevant. The 10.X SDK is just around the
corner and will break all of this with its new baseline.
It may be easier to keep these configs all in a custom BR2_EXTERNAL
overlay and keep buildroot pointed to pure sources of these packages
~Bryan
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-04-30 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 9:23 [Buildroot] [RFC, 1/1] configs/am62x-sk: Add fragment for TI tree integration Paresh Bhagat via buildroot
2024-04-30 14:54 ` Bryan Brattlof via buildroot [this message]
2024-05-06 18:01 ` Andreas Dannenberg via buildroot
2024-05-08 13:27 ` Paresh Bhagat 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=20240430145448.yhg6r64ohsfofeqv@bryanbrattlof.com \
--to=buildroot@buildroot.org \
--cc=X15000177@gmail.com \
--cc=bb@ti.com \
--cc=c-shilwant@ti.com \
--cc=g-gupta@ti.com \
--cc=gadiyar@ti.com \
--cc=khasim@ti.com \
--cc=p-bhagat@ti.com \
--cc=s-adivi@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.