simplifying the arch/arm64/boot/dts/freescale/Makefile

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 

simplifying the arch/arm64/boot/dts/freescale/Makefile

1,014 次查看
dsiegers
Contributor I

I'm using the i.MX 8MP SOC for a custom board. I'm using a Debian Bookworm OS, non-Yocto platform and have downloaded the lf-6.1.y_var03 repository for the kernel build.
Can I simplify the Makefile so that I don't have to include all the dts files and bindings for the entire i.MX8 family of processors? I'm finding it difficult to remove the features that we don't intend to support without breaking the kernel build when I alter the Makefile using the make menuconfig tool.
Are there any examples for this procedure available?

David

0 项奖励
回复
4 回复数

992 次查看
dsiegers
Contributor I

Also, is there a suggested approach to modifying the defconfig file (we are using the Variscite dev kit, hence the imx8_var_defconfig file). It seems every time I attempt to remove even a simple subsystem, I break the kernel build because of bindings to others SOCs.

0 项奖励
回复

992 次查看
dsiegers
Contributor I

Thank you @Chavira. By maintaining the makefile as provided, are you indicating that it is suggested to carry all the .dts files and supported subsystems contained in the baseline freescale Makefile with our custom designs kernel?

0 项奖励
回复

966 次查看
Chavira
NXP TechSupport
NXP TechSupport

Hi @dsiegers!

 

You should maintain all the files, you only have to add your configurations and device tree files to the kernel.

If you do your own configurations you only can compile for your target.

 

 

0 项奖励
回复

1,008 次查看
Chavira
NXP TechSupport
NXP TechSupport

HI @dsiegers!
Thank you for contacting NXP Support!

You can modify the Makefile to support the targets that you need, I recommend to maintain the make file as we provide.

Also you can take as a reference this community post.

 

Best Regards!

Chavira

0 项奖励
回复