Problem With Kernel Driver Compiled-In Data (mcx/gpu-viv)

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

Problem With Kernel Driver Compiled-In Data (mcx/gpu-viv)

Jump to solution
271 Views
A_Guyula
Contributor I

This isn't so much a question as a hope for future Kernel upgrades. 
As a matter of policy, we don't like to have any identifying information written into the Kernel. 
There is a useful build option KBUILD_BUILD_HOST, that can be applied to give a build host name of our choosing.
Scans through the binaries of our Kernel and module builds have shown that the mxc/gpu-viv portion of the source generates its own HOST variable instead of using the kernel option.
I know that the entire kernel source package is huge and that resources are minimal for things that are working/mature, however I was hoping that this "feature" could be perhaps modified in the Kbuild to use KBUILD_BUILD_HOST or simply removed.
For me it is extremely hard to really say what the value of the building host name has to the driver. Its only used here mxc/gpu-viv/hal/os/linux/kernel/gc_hal_kernel_device.c .

0 Kudos
Reply
1 Solution
254 Views
AldoG
NXP TechSupport
NXP TechSupport

Hello,

Thank you for your comments, will take it and share it with software team for evaluation.

Best regards/Saludos,
Aldo.

View solution in original post

0 Kudos
Reply
1 Reply
255 Views
AldoG
NXP TechSupport
NXP TechSupport

Hello,

Thank you for your comments, will take it and share it with software team for evaluation.

Best regards/Saludos,
Aldo.

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2143651%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EProblem%20With%20Kernel%20Driver%20Compiled-In%20Data%20(mcx%2Fgpu-viv)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2143651%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EThis%20isn't%20so%20much%20a%20question%20as%20a%20hope%20for%20future%20Kernel%20upgrades.%26nbsp%3B%3CBR%20%2F%3EAs%20a%20matter%20of%20policy%2C%20we%20don't%20like%20to%20have%20any%20identifying%20information%20written%20into%20the%20Kernel.%26nbsp%3B%3CBR%20%2F%3EThere%20is%20a%20useful%20build%26nbsp%3Boption%20KBUILD_BUILD_HOST%2C%20that%20can%20be%20applied%20to%20give%20a%20build%20host%20name%20of%20our%20choosing.%3CBR%20%2F%3EScans%20through%20the%20binaries%20of%20our%20Kernel%20and%20module%20builds%20have%20shown%20that%20the%20mxc%2Fgpu-viv%20portion%20of%20the%20source%20generates%20its%20own%20HOST%20variable%20instead%20of%20using%20the%20kernel%20option.%3CBR%20%2F%3EI%20know%20that%20the%20entire%20kernel%20source%20package%20is%20huge%20and%20that%20resources%20are%20minimal%20for%20things%20that%20are%20working%2Fmature%2C%20however%20I%20was%20hoping%20that%20this%20%22feature%22%20could%20be%20perhaps%20modified%20in%20the%20Kbuild%20to%20use%20KBUILD_BUILD_HOST%20or%20simply%20removed.%3CBR%20%2F%3EFor%20me%20it%20is%20extremely%20hard%20to%20really%20say%20what%20the%20value%20of%20the%20building%20host%20name%20has%20to%20the%20driver.%20Its%20only%20used%20here%26nbsp%3Bmxc%2Fgpu-viv%2Fhal%2Fos%2Flinux%2Fkernel%2Fgc_hal_kernel_device.c%20.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2144713%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20Problem%20With%20Kernel%20Driver%20Compiled-In%20Data%20(mcx%2Fgpu-viv)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2144713%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHello%2C%3CBR%20%2F%3E%3CBR%20%2F%3EThank%20you%20for%20your%20comments%2C%20will%20take%20it%20and%20share%20it%20with%20software%20team%20for%20evaluation.%3CBR%20%2F%3E%3CBR%20%2F%3EBest%20regards%2FSaludos%2C%3CBR%20%2F%3EAldo.%3C%2FP%3E%3C%2FLINGO-BODY%3E