Lines Matching refs:modules

12 to pick up the right flags to the compiler. Functionality for building modules
14 either is similar, and all modules are initially developed and built
18 in building out-of-tree (or "external") modules. The author of an
28 To build external modules, you must have a prebuilt kernel available
30 Also, the kernel must have been built with modules enabled. If you are
37 building external modules.
55 		$ make -C /lib/modules/`uname -r`/build M=$PWD
60 		$ make -C /lib/modules/`uname -r`/build M=$PWD modules_install
98 	modules
99 		The default target for external modules. It has the
105 		/lib/modules/<kernel_release>/updates/, but a prefix may
113 		List the available targets for external modules.
120 	external modules.
179 		KDIR ?= /lib/modules/`uname -r`/build
208 		KDIR ?= /lib/modules/`uname -r`/build
214 	each file; however, some external modules use makefiles
221 	kbuild supports building multiple modules with a single build
222 	file. For example, if you wanted to build two modules, foo.ko
265 	External modules tend to place header files in a separate
326 	/lib/modules/$(KERNELRELEASE)/kernel/
328 And external modules are installed in:
330 	/lib/modules/$(KERNELRELEASE)/updates/
340 		=> Install dir: /frodo/lib/modules/$(KERNELRELEASE)/kernel/
345 	and out-of-tree modules.
350 	External modules are by default installed to a directory under
351 	/lib/modules/$(KERNELRELEASE)/updates/, but you may wish to
352 	locate modules for a specific functionality in a separate
358 		=> Install dir: /lib/modules/$(KERNELRELEASE)/gandalf/
374 Symbols From the Kernel (vmlinux + modules)
379 	the kernel and compiled modules. For each symbol, the
396 	1) It lists all exported symbols from vmlinux and all modules.
421 		If you have two modules, foo.ko and bar.ko, where
423 		common top-level kbuild file so both modules are
439 		will then do the expected and compile both modules with