summaryrefslogtreecommitdiff
path: root/sys/dev/digi/CX.c
Commit message (Collapse)AuthorAgeFilesLines
* Remove the source to digi(4).John Baldwin2017-04-251-48/+0
| | | | | | | This was forgotten when the driver was removed in r305235. Notes: svn path=/head/; revision=317426
* Use __FBSDID().David E. O'Brien2003-08-241-1/+3
| | | | | | | Also some minor style cleanups. Notes: svn path=/head/; revision=119418
* Add some missing MODULE_VERSIONsBrian Somers2002-04-101-0/+1
| | | | | | | | Without these, the kern_linker interface doesn't record these pseudo-drivers, making them unavailable via modlist_lookup2*(). Notes: svn path=/head/; revision=94320
* Add a ``digi'' driver.Brian Somers2001-05-021-0/+45
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. Notes: svn path=/head/; revision=76195