On 9/15/2023 11:42 AM, Denys Dmytriyenko wrote:
On Fri, Sep 15, 2023 at 11:17:11AM -0500, Bajjuri, Praneeth wrote:
On 9/14/2023 8:47 PM, Balagopalakrishnan, Anand wrote:
Hi Denys,
This is only needed for v7 platforms like AM3 / AM4 and possibly AM57x also.
CONFIG_PREEMPT is enabled by default on arm64 platforms like AM65x.
Praneeth will send a kernel patch for TI kernel. This meta-ti patch is meant to
unblock anyone who wants to enable SGX drive in the meanwhile.
This patch can be abandoned .
https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/?h=ti-linux-6.1.y-cicd&id=e025e31126fff01ded59d901af916abe87646ca6
enables CONFIG_PREEMPT
Praneeth,
Slight offtopic, but I was wondering what are the rules now for changes like
this modifying upstream multi_v7_defconfig directly, vs. going into one of the
config fragments in kernel/configs/?
Sorry for the delayed reply.
As you can see here:
https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/arch/arm/configs/multi_v7_defconfig?h=ti-linux-6.1.y
we have recently added few more configurations.
I Plan to send all of these configurations to mainline
(Since these are drivers already in upstream and preference is to have
the config as well)
Similar to plan for drivers that are upstream complete for v8 platforms thru
arch/arm64/configs/defconfig
The general direction for kernel/configs/* fragments is for placeholder
prune configurations for faster builds and debug configurations and for
certain configurations which are certain that cannot be in mainline
default configuration yet.
Hope it clarifies.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#16999):
https://lists.yoctoproject.org/g/meta-ti/message/16999
Mute This Topic: https://lists.yoctoproject.org/mt/101362535/21656
Group Owner: [email protected]
Unsubscribe:
https://lists.yoctoproject.org/g/meta-ti/leave/6695321/21656/1393940836/xyzzy
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
