13f8d2ce5f
Gone are the old kern_sysctl(), cpu_sysctl(), hw_sysctl(), vfs_sysctl(), etc, routines, along with sysctl_int() et al. Now all nodes are registered with the tree, and nodes can be added (or removed) easily, and I/O to and from the tree is handled generically. Since the nodes are registered with the tree, the mapping from name to number (and back again) can now be discovered, instead of having to be hard coded. Adding new nodes to the tree is likewise much simpler -- the new infrastructure handles almost all the work for simple types, and just about anything else can be done with a small helper function. All existing nodes are where they were before (numerically speaking), so all existing consumers of sysctl information should notice no difference. PS - I'm sorry, but there's a distinct lack of documentation at the moment. I'm working on sysctl(3/8/9) right now, and I promise to watch out for buses. |
||
---|---|---|
.. | ||
cesfic | ||
compile | ||
conf | ||
dev | ||
include | ||
Makefile | ||
README |
$NetBSD: README,v 1.2 2003/12/04 13:05:16 keihan Exp $ This is a port of NetBSD to the FIC8234 VME processor board, made by the swiss company CES (Geneve). These boards are (or have been) popular in high energy physics data acquisition (think of CERN!). See http://www.ces.ch/Products/CPUs/FIC8234/FIC8234.html for some technical data. The highlights: - MC68040 processor at 25 MHz (optional dual-processor) - 8 or 32 MByte RAM - 2 serial ports on Z85c30 - 79c900 (ILACC) ethernet - 53c710 SCSI The port is quite rudimentary at the moment. The kernel is started out of a running OS-9 system. SCSI support is not present yet, so it only works diskless with NFS (or ramdisk - not tested) root. It is good enough for multiuser, self-hosting etc. however. To start it: - make OS image by "objcopy --output-target=binary netbsd <imagename>" - load image to physical address 0x20100000 (RAM start + 1M) - jump to 0x20100400 For questions and contributions, contact Matthias Drochner (drochner@NetBSD.org).