Driver for the NCR 53c810, 815, 820, 825, 860, 875, 885, 895, and 896 PCI SCSI host adapter (QNX Neutrino)
|You must be root to start this driver.|
devb-ncr8 [cam option[,option]...] [cdrom option[,option]...] [disk option[,option]...] [optical option[,option]...] [ncr8 option[,option]...] [blk option[,option]...] &
|Use commas (,) to separate the options. You can put the cam, cdrom, disk, optical, ncr8, and blk groups of options in any order.|
The cdrom options control the driver's interface to cam-cdrom.so. If specified, they must follow the cdrom keyword.
The disk options control the driver's interface to cam-disk.so. If specified, they must follow the disk keyword.
The optical options control the driver's interface to cam-optical.so. If specified, they must follow the optical keyword.
The ncr8 options control the driver's interface to the NCR 8 series controllers.
The blk options control io-blk.so. If specified, they must follow the blk keyword.
The devb-ncr8 driver is for the NCR53c810, NCR53c815, NCR53c820, NCR53c825, NCR53c860, NCR53c875, NCR53c885, NCR53c895, and NCR53c896 PCI SCSI adapters. The driver automatically scans the machine for controllers. Controllers are numbered from 0 to n, in the order they're found.
The driver performs a scan, looking for installed units. All targets are scanned (0 to 7) and for each target, each LUN (Logical Unit Number) is scanned (0 to 7). Devices are numbered starting from 0, and each type of device is numbered separately.
The devb-ncr8 driver autodetects all PCI NCR53c810 adapters by default, therefore you must specify the ncr8 pci option to the driver if you only require a specific SCSI adapter to be used.
|This driver currently doesn't support synchronous or wide data transfers.|
The devb-ncr8 driver closes its standard input, standard output and standard error immediately after completing its initializations. Error messages may be produced during the initialization phase and are written to standard error.
Assume an NCR 53c810 controller, and list all connected devices:
Assume an NCR 53c810 controller with a PCI index of 1, and list all connected devices:
devb-ncr8 ncr8 pci=1 &
The devb-ncr8 driver causes io-blk.so to adopt various block special devices under /dev. These devices are normally named hdn (or cdn for CD-ROMs), where n is the physical unit number of the device.
This driver could also require the following shared objects:
|cam-cdrom.so||For CD-ROM access|
|cam-disk.so||For hard-disk access|
The devb-ncr8 driver terminates only if an error occurs during startup, or if it has successfully forked itself upon startup because it hadn't been initially started in the background.
Unless overridden with the blk automount= option (see io-blk.so), devices are mounted as:
While there's no limit to the size of a disk or partition, I/O (i.e. the lseek(), read() and write() functions) is currently limited to 2 gigabytes per partition (or disk). This I/O limit has no effect on the partition size for mounted filesystems.
Known supported functions include:
chmod(), chown(), close(), closedir(), creat(), devctl(), dup(), dup2(), fcntl(), fpathconf(), fstat(), lseek(), mkdir(), mkfifo(), mknod(), open(), opendir(), pathconf(), read(), readdir(), readlink(), rewinddir(), rmdir(), stat(), symlink(), unlink() (not supported for directories), utime(), write()
Note that certain calls (such as pipe(), as well as read() and write() on FIFOs) may require the pipe manager.
"Block-oriented drivers (devb-*)," "Common access method (cam-*)," and "Filesystem drivers (fs-*)" in the Utilities Summary