summaryrefslogtreecommitdiffstats
path: root/sys/modules/digi
Commit message (Collapse)AuthorAgeFilesLines
* Let modules use the kernel's opt_*.h files if built along withyar2005-10-141-0/+2
| | | | | | | | | | | | | | the kernel by wrapping all targets for fake opt_*.h files in .if defined(KERNBUILDDIR). Thus, such fake files won't be created at all if modules are built with the kernel. Some modules undergo cleanup like removing unused or unneeded options or .h files, without which they wouldn't build this way or the other. Reviewed by: ru Tested by: no binary changes in modules built alone Tested on: i386 sparc64 amd64
* Fix my recent breakage of some modules.bde2002-02-151-0/+4
|
* digiio.h has moved to /usr/include/sysbrian2001-05-191-1/+1
|
* Add a ``digi'' driver.brian2001-05-0210-0/+73
This driver supports PCI Xr-based and ISA Xem Digiboard cards. dgm will go away soon if there are no problems reported. For now, configuring dgm into your kernel warns that you should be using digi. This driver is probably close to supporting Xi, Xe and Xeve cards, but I wouldn't expect them to work properly (hardware donations welcome). The digi_* pseudo-drivers are not drivers themselves but contain the BIOS and FEP/OS binaries for various digiboard cards and are auto-loaded and auto-unloaded by the digi driver at initialisation time. They *may* be configured into the kernel, but waste a lot of space if they are. They're intended to be left as modules. The digictl program is (mainly) used to re-initialise cards that have external port modules attached such as the PC/Xem.
OpenPOWER on IntegriCloud