Image Type: ARM Linux Kernel Image (lzo compressed)ĭata Size: 5459649 Bytes = 5331.69 kB = 5. The last few lines of log look like KSYM. It may be a silly question, but sorry I'm pretty new to kernel/device drivers.Īfter git checkout and installing the cross-compiler(arm-linux-gnueabihf-gcc 4.9.2), I issue the basic make comands $ make odroidc_defconfigĪll the steps are successful. Also do make sure to use EXPORTSYMBOL (foo) when building the driver as module so that any dependencies are taken care of when loading module symbols. Then you should be able to see the '.ko' file corresponding to the driver. Apparently uImage/device tree image compilation doesn't work that way.ĭo I need to write my own Makefile for standalone device driver compilation? This will allow your driver to be compiled as module once you select the driver as 'M' in your kernel config. I was expecting to find a ".ko" file in the driver directory after doing the make, but no such file exists. I need to make some customized changes into an existing driver code present in the kernel repository and reload the driver. To make it easy through device drivers Linux Kernel provides a way to communicate from user-space to device’s chips like WiFi, Bluetooth etc otherwise it’ll not be an easy task to do. The Linux kernel has its own build system based on make, which generates the correct gcc options for a successful compilation of kernel components and modules.
0 Comments
Leave a Reply. |