On Apple's documentation page Installing a Custom Kernel Extension, which has been updated to include information for macOS 11, it includes the following:
Is it possible we're building our codeless kext incorrectly? (The source code for the kext is literally an empty file, though the resulting kext does contain an executable under Contents/MacOS.) Or is this documentation page simply wrong?
My company has been using a codeless kext for many years, and installing it on Big Sur requires the user to reboot, contradicting this claim.For codeless kexts, the system asks the user for permission to install the kext, but doesn’t reboot the user’s system.
Is it possible we're building our codeless kext incorrectly? (The source code for the kext is literally an empty file, though the resulting kext does contain an executable under Contents/MacOS.) Or is this documentation page simply wrong?
