README revision 1.8
11.8Skamil	$NetBSD: README,v 1.8 2018/05/29 16:53:56 kamil Exp $
21.1Spgoyette
31.1Spgoyette                           Kernel Developer's Manual
41.1Spgoyette
51.1SpgoyetteDESCRIPTION
61.1Spgoyette     The kernel example dynamic modules.
71.1Spgoyette
81.6Skamil     This directory contains the following example modules:
91.6Skamil     * executor        - basic implementation of callout and RUN_ONCE
101.1Spgoyette     * hello           - the simplest `hello world' module
111.6Skamil     * luahello        - the simplest `hello world' Lua module
121.6Skamil     * luareadhappy    - demonstrates calling Lua code from C
131.8Skamil     * panic_string    - shows how panic is being called through a device
141.8Skamil     * ping            - basic ioctl(9)
151.1Spgoyette     * properties      - handle incoming properties during the module load
161.1Spgoyette     * readhappy       - basic implementation of read(9) with happy numbers
171.7Skamil     * readhappy_mpsafe- demonstrates how to make a module MPSAFE
181.5Skamil     * sysctl          - demonstrates adding a sysctl handle dynamically
191.1Spgoyette
201.1Spgoyette     To build the examples you need a local copy of NetBSD sources. You also
211.1Spgoyette     need the comp set with toolchain. To build the module just enter a
221.1Spgoyette     directory with example modules and use make(1):
231.1Spgoyette
241.1Spgoyette         # make
251.1Spgoyette
261.1Spgoyette     To load, unload, and stat the module use modload(8), modunload(8) and
271.1Spgoyette     modstat(8).
281.1Spgoyette
291.1Spgoyette     The S parameter in the Makefile files points to src/sys and it can be
301.1Spgoyette     overloaded in this way:
311.1Spgoyette
321.1Spgoyette         # make S=/data/netbsd/src/sys
331.1Spgoyette
341.1Spgoyette     The code of a module does not need to be in src/sys unless you use
351.1Spgoyette     the autoconf(9) framework.
361.1Spgoyette
371.1Spgoyette     A cross-built of a module for a target platform is possible with the
381.1Spgoyette     build.sh framework. You need to generate the toolchain and set
391.1Spgoyette     appropriately PATH to point bin/ in the TOOLDIR path. An example command
401.1Spgoyette     to cross-build a module with the amd64 toolchain is as follows:
411.1Spgoyette
421.1Spgoyette        # nbmake-amd64 S=/data/netbsd/src/sys
431.1Spgoyette
441.1Spgoyette
451.1Spgoyette     The example modules should not be used on a production machine.
461.1Spgoyette
471.1Spgoyette     All modules that create a cdevsw should be verified that the major number
481.1Spgoyette     should not conflict with a real device.
491.1Spgoyette
501.1SpgoyetteSEE ALSO
511.3Spgoyette     modctl(2), module(7), modload(8), modstat(8), modunload(8), module(9),
521.3Spgoyette     intro(9lua)
531.1Spgoyette
541.1SpgoyetteHISTORY
551.1Spgoyette     An example of handling incoming properties first appeared in NetBSD 5.0
561.1Spgoyette     and was written by Julio Merino with further modifications by Martin
571.1Spgoyette     Husemann, Adam Hamsik, John Nemeth and Mindaugas Rasiukevicius.
581.1Spgoyette
591.1Spgoyette     This document and additional modules (hello, readhappy, properties,
601.4Ssevan     ping, luahello and luareadhappy) first appeared in NetBSD 8.0; they were
611.4Ssevan     written by Kamil Rytarowski.
621.1Spgoyette
631.7Skamil     The readhappy_mpsafe, executor and sysctls modules first appeared in NetBSD
641.7Skamil     9.0 and were authored by Siddharth Muralee.
651.5Skamil
661.8Skamil     The panic_string module first appeared in NetBSD 9.0 and was authored by
671.8Skamil     Harry Pantazis.
681.8Skamil
691.1SpgoyetteAUTHORS
701.1Spgoyette     This document was written by Kamil Rytarowski.
71