What happened?
From v0.6.2 to v0.6.4 changed the way the vipcore kernel module was compiled.
The change now means that the 0.6.4 build compiles the viplite vipcore kernel module into the kernel as a builtin module, meaning it can't be unloaded with rmmod and is now permanently loaded
This breaks any code that wants to use the unified galcore NPU kernel driver, as it prevents the user from being able to unload the vplite vipcore kernel module.
This is a pretty big deal if we want to run any standard ML model on the Radxa A7Z, as the viplite vipcore kernel driver doesn't work with any standard ML framework like ONNXRT
How to reproduce?
Simply try run rmmod vipcore on the 0.6.4 image for the Radxa A7Z, and notice it complains about it being a builtin module and thus can't be unloaded.
This is not the case on the 0.6.2 release
Branch
other (only relevant in corner cases)
On which host OS are you running the build script and observing this problem?
Other
Are you building on Windows WSL2?
Relevant log URL
No response
Code of Conduct
What happened?
From v0.6.2 to v0.6.4 changed the way the vipcore kernel module was compiled.
The change now means that the 0.6.4 build compiles the viplite vipcore kernel module into the kernel as a builtin module, meaning it can't be unloaded with rmmod and is now permanently loaded
This breaks any code that wants to use the unified galcore NPU kernel driver, as it prevents the user from being able to unload the vplite vipcore kernel module.
This is a pretty big deal if we want to run any standard ML model on the Radxa A7Z, as the viplite vipcore kernel driver doesn't work with any standard ML framework like ONNXRT
How to reproduce?
Simply try run rmmod vipcore on the 0.6.4 image for the Radxa A7Z, and notice it complains about it being a builtin module and thus can't be unloaded.
This is not the case on the 0.6.2 release
Branch
other (only relevant in corner cases)
On which host OS are you running the build script and observing this problem?
Other
Are you building on Windows WSL2?
Relevant log URL
No response
Code of Conduct