README revision 1.6
11.6Skamil $NetBSD: README,v 1.6 2018/04/13 20:30:09 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.1Spgoyette * properties - handle incoming properties during the module load 141.6Skamil * ping - basic ioctl(9) 151.1Spgoyette * readhappy - basic implementation of read(9) with happy numbers 161.5Skamil * sysctl - demonstrates adding a sysctl handle dynamically 171.1Spgoyette 181.1Spgoyette To build the examples you need a local copy of NetBSD sources. You also 191.1Spgoyette need the comp set with toolchain. To build the module just enter a 201.1Spgoyette directory with example modules and use make(1): 211.1Spgoyette 221.1Spgoyette # make 231.1Spgoyette 241.1Spgoyette To load, unload, and stat the module use modload(8), modunload(8) and 251.1Spgoyette modstat(8). 261.1Spgoyette 271.1Spgoyette The S parameter in the Makefile files points to src/sys and it can be 281.1Spgoyette overloaded in this way: 291.1Spgoyette 301.1Spgoyette # make S=/data/netbsd/src/sys 311.1Spgoyette 321.1Spgoyette The code of a module does not need to be in src/sys unless you use 331.1Spgoyette the autoconf(9) framework. 341.1Spgoyette 351.1Spgoyette A cross-built of a module for a target platform is possible with the 361.1Spgoyette build.sh framework. You need to generate the toolchain and set 371.1Spgoyette appropriately PATH to point bin/ in the TOOLDIR path. An example command 381.1Spgoyette to cross-build a module with the amd64 toolchain is as follows: 391.1Spgoyette 401.1Spgoyette # nbmake-amd64 S=/data/netbsd/src/sys 411.1Spgoyette 421.1Spgoyette 431.1Spgoyette The example modules should not be used on a production machine. 441.1Spgoyette 451.1Spgoyette All modules that create a cdevsw should be verified that the major number 461.1Spgoyette should not conflict with a real device. 471.1Spgoyette 481.1SpgoyetteSEE ALSO 491.3Spgoyette modctl(2), module(7), modload(8), modstat(8), modunload(8), module(9), 501.3Spgoyette intro(9lua) 511.1Spgoyette 521.1SpgoyetteHISTORY 531.1Spgoyette An example of handling incoming properties first appeared in NetBSD 5.0 541.1Spgoyette and was written by Julio Merino with further modifications by Martin 551.1Spgoyette Husemann, Adam Hamsik, John Nemeth and Mindaugas Rasiukevicius. 561.1Spgoyette 571.1Spgoyette This document and additional modules (hello, readhappy, properties, 581.4Ssevan ping, luahello and luareadhappy) first appeared in NetBSD 8.0; they were 591.4Ssevan written by Kamil Rytarowski. 601.1Spgoyette 611.6Skamil The executor and sysctls module first appeared in NetBSD 9.0 and were 621.6Skamil authored by Siddharth Muralee. 631.5Skamil 641.1SpgoyetteAUTHORS 651.1Spgoyette This document was written by Kamil Rytarowski. 66