Lines Matching refs:modules

28 	   --- 6.1 Symbols From the Kernel (vmlinux + modules)
41 to pick up the right flags to "gcc." Functionality for building modules
43 either is similar, and all modules are initially developed and built
47 in building out-of-tree (or "external") modules. The author of an
57 To build external modules, you must have a prebuilt kernel available
59 Also, the kernel must have been built with modules enabled. If you are
66 building external modules.
84 		$ make -C /lib/modules/`uname -r`/build M=$PWD
89 		$ make -C /lib/modules/`uname -r`/build M=$PWD modules_install
124 	modules
125 		The default target for external modules. It has the
131 		/lib/modules/<kernel_release>/extra/, but a prefix may
138 		List the available targets for external modules.
145 	external modules.
205 		KDIR ?= /lib/modules/`uname -r`/build
239 		KDIR ?= /lib/modules/`uname -r`/build
249 	each file; however, some external modules use makefiles
268 		KDIR ?= /lib/modules/`uname -r`/build
287 	Some external modules need to include an object file as a blob.
307 	kbuild supports building multiple modules with a single build
308 	file. For example, if you wanted to build two modules, foo.ko
351 	External modules tend to place header files in a separate
416 	/lib/modules/$(KERNELRELEASE)/kernel/
418 And external modules are installed in:
420 	/lib/modules/$(KERNELRELEASE)/extra/
430 		=> Install dir: /frodo/lib/modules/$(KERNELRELEASE)/kernel/
435 	and out-of-tree modules.
440 	External modules are by default installed to a directory under
441 	/lib/modules/$(KERNELRELEASE)/extra/, but you may wish to
442 	locate modules for a specific functionality in a separate
448 		=> Install dir: /lib/modules/$(KERNELRELEASE)/gandalf/
464 6.1 Symbols From the Kernel (vmlinux + modules)
469 	the kernel and compiled modules. For each symbol, the
486 	1) It lists all exported symbols from vmlinux and all modules.
511 		If you have two modules, foo.ko and bar.ko, where
513 		common top-level kbuild file so both modules are
529 		will then do the expected and compile both modules with
557 	External modules have traditionally used "grep" to check for
559 	broken. As introduced before, external modules should use
561 	in-tree modules when testing for `CONFIG_` definitions.