It would be really nice If I could avoid to fork the repo just because if that single kernel module.
Are there any chances that you will include it in the official balena-os/balena-intel repo?
As seen in the linux-yocto_%.bbappend, you have already included some customer requests. What are your policies regarding what can be included in your official repository?
Usually what you see in the Requested by customer field were requests from our paying customers.
We will evaluate the adding of usbmon to the list of modules and will get to you with a reply.
In the past we had some issue with the free space availability for Intel NUC so adding more modules was a problem. Now we freed some space so there is some margin to add user requested modules.
Hi @abaldur,
Usually what you see in the Requested by customer field were requests from our paying customers.
We will evaluate the adding of usbmon to the list of modules and will get to you with a reply.
In the past we had some issue with the free space availability for Intel NUC so adding more modules was a problem. Now we freed some space so there is some margin to add user requested modules.
Regards!
When you say that “Requested by customer” is from your paying customers, does that mean customers that are at least on the prototype plan? Or do you charge a separate fee for special requests like that?
What are the criteria for kernel modules to be included in the balena-os/balena-intel repo? I guess that you would like to keep it as small as possible?
If we decide to build our own custom yocto image, can we then still make use of your backend for pushing and deploying images?
1 and 2 We enable kernel modules for paying and non-paying customers depending on how important is for the community to have those modules. We usually want to preserve the free space, to have it available for modules that are important for the community.
3 If you decide to build your own custom image you can still make use of our infrastructure to deploy and manage your applications. The only caveat is if you will update the OS from the dashboard, your custom image will be overwritten with the default OS. As long as you don’t do remote update to the OS you won’t have problems.
Another question would be why do you need this kernel module activated and if you need it permanently activated or only for some temporary debug purposes?
The reason we need the kernel module activated is because we are having trouble with a USB device that sometimes (unfortunately rarely) fails, and I would like to have as much debugging information as possible when that happens.
It would definitely be beneficial for us to have the module available permanently in order to track down any potential future problems.