I see no path forward for rapid-application-development and multi-vendor integration when everyone has to build their own kernel. This is the point and purpose of using a highly stable platform such as an Ubuntu LTR.
A 5 minute task, build a DKMS module, turns into considerably more work.
The discrepancy between the default config and released config highlights a quality-control / release-control issue.
The binary released does not match the source-code release. This particular difference is small and easily remedied.
However consider how many people building the kernel to build new modules didn’t check and it indicates there is a flaw in the release process which makes this discrepancy possible at all.
This diminishes the value proposition of the Drive AGX platform for R&D.
I also need to know how to pull the .dtb file from the unit so I can check that isn’t broken or significantly different.
e.g. How do I access the boot partition and copy a file out of it?
(I am familiar with the u-boot tool and how it works.)