On the Boundary Devices kernel, and maybe others, you can use cat /sys/kernel/debug/gpio to get a list of the mapped gpios, their states, and name given when it was allocated. You can grep the kernel source for the name and find out what module grabbed it. root@nitrogen6x:/opt# cat /sys/kernel/debug/gpio GPIOs 0-31, platform/209c000.gpio, 209c000.gpio: gpio-2 (flexcan-trx-stby … Read more
Depends on your current skills. If you’re really new to Linux, perhaps you should start with user space system programming with Advanced Linux Programming. You’ll get good knowledge of Unix system calls and other concepts such as signals, processes/threads and so on with this free resource. This is a must (understanding the user space API) … Read more
I see the relationship between BSPs and devices drivers as “has-a”. Board support packages include device drivers. The differences between BSPs & kernels isn’t easy to distinguish. A kernel translates instructions to the hardware. Kernels are often written to particular families of hardware, so they’re not as portable or generic as they seem. It amounts … Read more
The short answer is that the .ko file is your object file linked with some kernel automatically generated data structures that are needed by the kernel. The .o file is the object file of your module – the result of compiling your C file. The kernel build system then automatically creates another C file with … Read more