Lines Matching refs:module

3 This document describes how to build an out-of-tree kernel module.
45 external module should supply a makefile that hides most of the
46 complexity, so one only has to type "make" to build the module. This is
66 executed to make module versioning work.
70 	The command to build an external module is:
74 	The kbuild system knows that an external module is being built
81 	Then to install the module(s) just built, add the target
98 		Informs kbuild that an external module is being built.
100 		directory where the external module (kbuild file) is
105 	When building an external module, only a subset of the "make"
110 	The default will build the module(s) located in the current
123 		Install the external module(s). The default location is
128 		Remove all generated files in the module directory only.
135 	It is possible to build single files that are part of a module.
136 	This works equally well for the kernel, a module, and even for
139 	Example (The module foo.ko, consist of bar.o and baz.o):
148 In the last section we saw the command to build a module for the
149 running kernel. The module is not actually built, however, because a
151 the module(s) being built, along with the list of requisite source
157 and, after linking, will result in the kernel module <module_name>.ko.
159 When the module is built from multiple sources, an additional line is
168 module 8123.ko, which is built from the following files:
177 	An external module always includes a wrapper makefile that
178 	supports building the module using "make" with no arguments.
276 	the assignment to the module.
279 	build the kernel module 8123.ko; it has been included as
286 	when creating the object file for the module.
307 	  module, then the file is placed in the same directory as the
323 		#include <linux/module.h>
364 	To build the module complex.ko, we then need the following
430 for an exported symbol is created. When a module is loaded/used, the
432 the module; if they are not equal, the kernel refuses to load the
433 module.
446 		<CRC>	    <Symbol>	       <module>
459 	When building an external module, the build system needs access
464 	where the external module is being built, this file will be
471 	Sometimes, an external module uses exported symbols from
472 	another external module. kbuild needs to have full knowledge of
499 		full knowledge of symbols from either module.
502 		When an external module is built, a Module.symvers file
507 		built. During the module build, kbuild will read the
509 		module, and when the build is finished, a new
515 		another module, you can assign a space separated list
526 	decide if a specific feature is included in the module. In