Hi, Am Freitag, 15. September 2023, 03:47:08 CEST schrieb Paul Graham:
...
So, my questions are: 1. Do you have any hints or suggestions on debugging issues with device trees and kernel module loading at boot time? Gateworks demonstrated that the board works fine with a Linux 6.4.6 kernel with their .config file, but they compile most, if not all, of their drivers directly into the kernel. Anyway, I believe that using the openSUSE kernels will work if I can work through some device tree issues.
What's the issue precisely? Usually any driver that can be built as a module can be used just fine when loaded as a module, so inherently using =m shouldn't be an issue. Is this about specific platform drivers which don't have any autoloading/hardware matching configured?
2. In the short term, if I needed to use a custom kernel for this board with MicroOS, is there any straightforward method to use it with the usual transactional-update process? We already have custom application packages that we host in a repository that MicroOS uses for installing and updating our packages. Could we just include our custom kernel package in our repository somehow despite the fact that MicroOS pushes out its own kernel package? It seems like the kernel is part of the group of packages that MicroOS installs as its base OS, so it isn't clear to me that I can just replace the kernel from MicroOS with my own.
You can. MicroOS will honour any repo and packaging changes you make. Ideally you set up builds on OBS based on the latest distro kernel to get updates, but this only works if the patches are very simple such that they don't need to be rebased manually all the time. Cheers, Fabian
Sorry for the long email and thanks again for your help!
Paul