Using code directly from CVS | Using the tarball in a file release | Using the diff in a file release | Using ISA PnP and atppc | Common Steps in Building
The code is being developed against NetBSD-current: you should know how to track NetBSD's kernel development at least in terms of having the kernel sources (more details are available on www.netbsd.org).
It will probably be a good idea to apply diffs/tarball or checkout code into an empty directory in case the code is not in sync with the latest NetBSD-current source and you need to apply patches by hand. You can try to minimize this trouble by getting NetBSD-current sources that would match the date of the file release.
You can checkout or export code from the CVS repository into an empty directory or even directly into the kernel source tree (this will probably overwrite files that may need to be patched). Once you have the files, you can remove the TODO's (files that contain development activity lists and do not have anything to do with compilation), apply any patches, and copy them (if necessary) to the kernel source directory.
If you want to do this directly into the kernel source tree, an export is probably a better idea than a checkout (otherwise CVS files may not agree and you may have problems).
cat /path/to/file/ppbus.diff | patch -p4
Before you can build a kernel with 'atppc* at isapnp?' in the configuration file (to configure atppc using the ISA PnP code), you must regenerate the database of known devices (described in isapnp(9)):
You must repeat these steps whenever the file 'src/sys/dev/isapnp/isapnpdevs', the master source for the ISA PnP database, changes.
For steps common to both diff and tarball, you will need to know how to build and configure a kernel in NetBSD - see NetBSD Kernel Documentation for details).
A kernel configuration file called 'PPBUS_DEV' is including in diffs and tarballs: this file contains the lines needed to add atppc, ppbus, and other related devices. Please note that 'PPBUS_DEV' is an i386 kernel configuration file: the relevant lines for the devices are not.
Once you are sure you can boot safely, you can test the code. Print some documents and use the other device drivers.
Documentation | Home