i.MX 8X - imx_v8_defconfig - optimised for size, boot time, CVE risk

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

i.MX 8X - imx_v8_defconfig - optimised for size, boot time, CVE risk

359 Views
petero5
Contributor IV

Hi, where can we find examples of defconfigs that are optimised for size, boot time, CVE risk?

Ideally for i.MX 8X, but failing that for IMX or embedded Linux in general?

https://github.com/nxp-imx/linux-imx/blob/lf-6.12.y/arch/arm64/configs/imx_v8_defconfig

has y for many things that an i.MX 8X embedded Linux device would not typically use?

Thank you
Peter

Tags (1)
0 Kudos
Reply
1 Reply

280 Views
JosephAtNXP
NXP TechSupport
NXP TechSupport

Hi,

Thank you for your interest in NXP Semiconductor products,

Actually i.MX processors defconfigs have a lot of drivers and modules since it's the kernel that is going to be used in all Yocto images, including all their device tree and binary demos and the proof of concepts featuring them.

CVE risk is covered between every release, so this recommendation would be about the branch, use the latest one.

For size and boot time, you can start from imx_v8_defconfig and remove the drivers that your application won't need, it's mostly trial and error and application dependent.

Regards

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2290299%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3Ei.MX%208X%20-%20imx_v8_defconfig%20-%20optimised%20for%20size%2C%20boot%20time%2C%20CVE%20risk%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2290299%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%2C%20where%20can%20we%20find%20examples%20of%20defconfigs%20that%20are%20optimised%20for%20size%2C%20boot%20time%2C%26nbsp%3BCVE%20risk%3F%3C%2FP%3E%3CP%3EIdeally%20for%26nbsp%3Bi.MX%208X%2C%20but%20failing%20that%20for%20IMX%20or%20embedded%20Linux%20in%20general%3F%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fnxp-imx%2Flinux-imx%2Fblob%2Flf-6.12.y%2Farch%2Farm64%2Fconfigs%2Fimx_v8_defconfig%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2Fnxp-imx%2Flinux-imx%2Fblob%2Flf-6.12.y%2Farch%2Farm64%2Fconfigs%2Fimx_v8_defconfig%3C%2FA%3E%3C%2FP%3E%3CP%3Ehas%20y%20for%20many%20things%20that%20an%26nbsp%3Bi.MX%208X%20embedded%20Linux%20device%20would%20not%20typically%20use%3F%3C%2FP%3E%3CP%3EThank%20you%3CBR%20%2F%3EPeter%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2290299%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CLINGO-LABEL%3Ei.MX%208%20Family%20%7C%20i.MX%208QuadMax%20(8QM)%20%7C%208QuadPlus%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2291186%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20i.MX%208X%20-%20imx_v8_defconfig%20-%20optimised%20for%20size%2C%20boot%20time%2C%20CVE%20risk%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2291186%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CP%3EThank%20you%20for%20your%20interest%20in%20NXP%20Semiconductor%20products%2C%3C%2FP%3E%0A%3CP%3EActually%20i.MX%20processors%20defconfigs%20have%20a%20lot%20of%20drivers%20and%20modules%20since%20it's%20the%20kernel%20that%20is%20going%20to%20be%20used%20in%20all%20Yocto%20images%2C%20including%20all%20their%20device%20tree%20and%20binary%20demos%20and%20the%20proof%20of%20concepts%20featuring%20them.%3C%2FP%3E%0A%3CP%3ECVE%20risk%20is%20covered%20between%20every%20release%2C%20so%20this%20recommendation%20would%20be%20about%20the%20branch%2C%20use%20the%20latest%20one.%3C%2FP%3E%0A%3CP%3EFor%20size%20and%20boot%20time%2C%20you%20can%20start%20from%20imx_v8_defconfig%20and%20remove%20the%20drivers%20that%20your%20application%20won't%20need%2C%20it's%20mostly%20trial%20and%20error%20and%20application%20dependent.%3C%2FP%3E%0A%3CP%3ERegards%3C%2FP%3E%3C%2FLINGO-BODY%3E