title: sk98lin(4)

text:
# sk98lin(4)

## NAME
sk98lin - Marvell/SysKonnect Gigabit Ethernet driver v6.21

## SYNOPSIS
insmod sk98lin.o [Speed_A=i,j,...] [Speed_B=i,j,...] [AutoNeg_A=i,j,...] [AutoNeg_B=i,j,...] [DupCap_A=i,j,...] [DupCap_B=i,j,...] [FlowCtrl_A=i,j,...] [FlowCtrl_B=i,j,...] [Role_A=i,j,...] [Role_B=i,j,...] [ConType=i,j,...] [Moderation=i,j,...] [IntsPerSec=i,j,...] [PrefPort=i,j,...] [RlmtMode=i,j,...]

## DESCRIPTION
Note: This obsolete driver was removed from the kernel in version 2.6.26.

sk98lin is the Gigabit Ethernet driver for Marvell and SysKonnect network adapter cards. It supports SysKonnect SK-98xx/SK-95xx compliant Gigabit Ethernet Adapter and any Yukon compliant chipset.

When loading the driver using insmod, parameters for the network adapter cards might be stated as a sequence of comma separated commands. If for instance two network adapters are installed and AutoNegotiation on Port A of the first adapter should be ON, but on the Port A of the second adapter switched OFF, one must enter:

insmod sk98lin.o AutoNeg_A=On,Off

After sk98lin is bound to one or more adapter cards and the /proc filesystem is mounted on your system, a dedicated statistics file will be created in the folder /proc/net/sk98lin for all ports of the installed network adapter cards. Those files are named eth[x], where x is the number of the interface that has been assigned to a dedicated port by the system.

If loading is finished, any desired IP address can be assigned to the respective eth[x] interface using the ifconfig(8) command. This causes the adapter to connect to the Ethernet and to display a status message on the console saying "ethx: network connection up using port y" followed by the configured or detected connection parameters.

The sk98lin also supports large frames (also called jumbo frames). Using jumbo frames can improve throughput tremendously when transferring large amounts of data. To enable large frames, the MTU (maximum transfer unit) size for an interface is to be set to a high value. The default MTU size is 1500 and can be changed up to 9000 (bytes). Setting the MTU size can be done when assigning the IP address to the interface or later by using the ifconfig(8) command with the mtu parameter. If for instance eth0 needs an IP address and a large frame MTU size, the following two commands might be used:

ifconfig eth0 10.1.1.1

ifconfig eth0 mtu 9000

Those two commands might even be combined into one:

ifconfig eth0 10.1.1.1 mtu 9000

Note that large frames can be used only if permitted by your network infrastructure. This means, that any switch being used in your Ethernet must also support large frames. Quite some switches support large frames, but need to be configured to do so. Most of the times, their default setting is to support only standard frames with an MTU size of 1500 (bytes). In addition to the switches inside the network, all network adapters that are to be used must also be enabled regarding jumbo frames. If an adapter is not set to receive large frames, it will simply drop them.

Switching back to the standard Ethernet frame size can be done by using the ifconfig(8) command again:

ifconfig eth0 mtu 1500

The Marvell/SysKonnect Gigabit Ethernet driver for Linux is able to support VLAN and Link Aggregation according to IEEE standards 802.1, 802.1q, and 802.3ad. Those features are available only after installation of open source modules which can be found on the Internet:

VLAN: http://www.candelatech.com/~greear/vlan.html

Link Aggregation: http://www.st.rim.or.jp/~yumo

Note that Marvell/SysKonnect does not offer any support for these open source modules and does not take the responsibility for any kind of failures or problems arising when using these modules.

### Parameters
Speed_A=i,j,...

This parameter is used to set the speed capabilities of port A of an adapter card. It is valid only for Yukon copper adapters. Possible values are: 10, 100, 1000, or Auto; Auto is the default. Usually, the speed is negotiated between the two ports during link establishment. If this fails, a port can be forced to a specific setting with this parameter.

Speed_B=i,j,...

This parameter is used to set the speed capabilities of port B of an adapter card. It is valid only for Yukon copper adapters. Possible values are: 10, 100, 1000, or Auto; Auto is the default. Usually, the speed is negotiated between the two ports during link establishment. If this fails, a port can be forced to a specific setting with this parameter.

AutoNeg_A=i,j,...

Enables or disables the use of autonegotiation of port A of an adapter card. Possible values are: On, Off, or Sense; On is the default. The Sense mode automatically detects whether the link partner supports auto-negotiation or not.

AutoNeg_B=i,j,...

Enables or disables the use of autonegotiation of port B of an adapter card. Possible values are: On, Off, or Sense; On is the default. The Sense mode automatically detects whether the link partner supports auto-negotiation or not.

DupCap_A=i,j,...

This parameter indicates the duplex mode to be used for port A of an adapter card. Possible values are: Half, Full, or Both; Both is the default. This parameter is relevant only if AutoNeg_A of port A is not set to Sense. If AutoNeg_A is set to On, all three values of DupCap_A ( Half, Full, or Both) might be stated. If AutoNeg_A is set to Off, only DupCap_A values Full and Half are allowed. This DupCap_A parameter is useful if your link partner does not support all possible duplex combinations.

DupCap_B=i,j,...

This parameter indicates the duplex mode to be used for port B of an adapter card. Possible values are: Half, Full, or Both; Both is the default. This parameter is relevant only if AutoNeg_B of port B is not set to Sense. If AutoNeg_B is set to On, all three values of DupCap_B ( Half, Full, or Both) might be stated. If AutoNeg_B is set to Off, only DupCap_B values Full and Half are allowed. This DupCap_B parameter is useful if your link partner does not support all possible duplex combinations.

FlowCtrl_A=i,j,...

This parameter can be used to set the flow control capabilities the port reports during auto-negotiation. Possible values are: Sym, SymOrRem, LocSend, or None; SymOrRem is the default. The different modes have the following meaning:

Sym = Symmetric

both link partners are allowed to send PAUSE frames

SymOrRem = SymmetricOrRemote

both or only remote partner are allowed to send PAUSE frames

LocSend = LocalSend

only local link partner is allowed to send PAUSE frames

None = None

no link partner is allowed to send PAUSE frames

Note that this parameter is ignored if AutoNeg_A is set to Off.

FlowCtrl_B=i,j,...

This parameter can be used to set the flow control capabilities the port reports during auto-negotiation. Possible values are: Sym, SymOrRem, LocSend, or None; SymOrRem is the default. The different modes have the following meaning:

Sym = Symmetric

both link partners are allowed to send PAUSE frames

SymOrRem = SymmetricOrRemote

both or only remote partner are allowed to send PAUSE frames

LocSend = LocalSend

only local link partner is allowed to send PAUSE frames

None = None

no link partner is allowed to send PAUSE frames

Note that this parameter is ignored if AutoNeg_B is set to Off.

Role_A=i,j,...

This parameter is valid only for 1000Base-T adapter cards. For two 1000Base-T ports to communicate, one must take the role of the master (providing timing information), while the other must be the slave. Possible values are: Auto, Master, or Slave; Auto is the default. Usually, the role of a port is negotiated between two ports during link establishment, but if that fails the port A of an adapter card can be forced to a specific setting with this parameter.

Role_B=i,j,...

This parameter is valid only for 1000Base-T adapter cards. For two 1000Base-T ports to communicate, one must take the role of the master (providing timing information), while the other must be the slave. Possible values are: Auto, Master, or Slave; Auto is the default. Usually, the role of a port is negotiated between two ports during link establishment, but if that fails the port B of an adapter card can be forced to a specific setting with this parameter.

ConType=i,j,...

This parameter is a combination of all five per-port parameters within one single parameter. This simplifies the configuration of both ports of an adapter card. The different values of this variable reflect the most meaningful combinations of port parameters. Possible values and their corresponding combination of per-port parameters:

ConType

DupCap

AutoNeg

FlowCtrl

Role

Speed

Auto

Both

On

SymOrRem

Auto

Auto

100FD

Full

Off

None

Auto

100

100HD

Half

Off

None

Auto

100

10FD

Full

Off

None

Auto

10

10HD

Half

Off

None

Auto

10

Stating any other port parameter together with this ConType parameter will result in a merged configuration of those settings. This is due to the fact, that the per-port parameters (e.g., Speed_A) have a higher priority than the combined variable ConType.

Moderation=i,j,...

Interrupt moderation is employed to limit the maximum number of interrupts the driver has to serve. That is, one or more interrupts (which indicate any transmit or receive packet to be processed) are queued until the driver processes them. When queued interrupts are to be served, is determined by the IntsPerSec parameter, which is explained later below. Possible moderation modes are: None, Static, or Dynamic; None is the default. The different modes have the following meaning:

None No interrupt moderation is applied on the adapter card. Therefore, each transmit or receive interrupt is served immediately as soon as it appears on the interrupt line of the adapter card.

Static Interrupt moderation is applied on the adapter card. All transmit and receive interrupts are queued until a complete moderation interval ends. If such a moderation interval ends, all queued interrupts are processed in one big bunch without any delay. The term Static reflects the fact, that interrupt moderation is always enabled, regardless how much network load is currently passing via a particular interface. In addition, the duration of the moderation interval has a fixed length that never changes while the driver is operational.

Dynamic Interrupt moderation might be applied on the adapter card, depending on the load of the system. If the driver detects that the system load is too high, the driver tries to shield the system against too much network load by enabling interrupt moderation. If—at a later time—the CPU utilization decreases again (or if the network load is negligible), the interrupt moderation will automatically be disabled.

Interrupt moderation should be used when the driver has to handle one or more interfaces with a high network load, which—as a consequence—leads also to a high CPU utilization. When moderation is applied in such high network load situations, CPU load might be reduced by 20–30% on slow computers.

Note that the drawback of using interrupt moderation is an increase of the round-trip-time (RTT), due to the queuing and serving of interrupts at dedicated moderation times.

IntsPerSec=i,j,...

This parameter determines the length of any interrupt moderation interval. Assuming that static interrupt moderation is to be used, an IntsPerSec parameter value of 2000 will lead to an interrupt moderation interval of 500 microseconds. Possible values for this parameter are in the range of 30...40000 (interrupts per second). The default value is 2000.

This parameter is used only if either static or dynamic interrupt moderation is enabled on a network adapter card. This parameter is ignored if no moderation is applied.

Note that the duration of the moderation interval is to be chosen with care. At first glance, selecting a very long duration (e.g., only 100 interrupts per second) seems to be meaningful, but the increase of packet-processing delay is tremendous. On the other hand, selecting a very short moderation time might compensate the use of any moderation being applied.

PrefPort=i,j,...

This parameter is used to force the preferred port to A or B (on dual-port network adapters). The preferred port is the one that is used if both ports A and B are detected as fully functional. Possible values are: A or B; A is the default.

RlmtMode=i,j,...

RLMT monitors the status of the port. If the link of the active port fails, RLMT switches immediately to the standby link. The virtual link is maintained as long as at least one "physical" link is up. This parameters states how RLMT should monitor both ports. Possible values are: CheckLinkState, CheckLocalPort, CheckSeg, or DualNet; CheckLinkState is the default. The different modes have the following meaning:

CheckLinkState Check link state only: RLMT uses the link state reported by the adapter hardware for each individual port to determine whether a port can be used for all network traffic or not.

CheckLocalPort In this mode, RLMT monitors the network path between the two ports of an adapter by regularly exchanging packets between them. This mode requires a network configuration in which the two ports are able to "see" each other (i.e., there must not be any router between the ports).

CheckSeg Check local port and segmentation: This mode supports the same functions as the CheckLocalPort mode and additionally checks network segmentation between the ports. Therefore, this mode is to be used only if Gigabit Ethernet switches are installed on the network that have been configured to use the Spanning Tree protocol.

DualNet In this mode, ports A and B are used as separate devices. If you have a dual port adapter, port A will be configured as eth[x] and port B as eth[x+1]. Both ports can be used independently with distinct IP addresses. The preferred port setting is not used. RLMT is turned off.

Note that RLMT modes CheckLocalPort and CheckLinkState are designed to operate in configurations where a network path between the ports on one adapter exists. Moreover, they are not designed to work where adapters are connected back-to-back.

## FILES
/proc/net/sk98lin/eth[x]

The statistics file of a particular interface of an adapter card. It contains generic information about the adapter card plus a detailed summary of all transmit and receive counters.

/usr/src/linux/Documentation/networking/sk98lin.txt

This is the README file of the sk98lin driver. It contains a detailed installation HOWTO and describes all parameters of the driver. It denotes also common problems and provides the solution to them.

## BUGS
Report any bugs to linux@syskonnect.de

## SEE ALSO
ifconfig(8), insmod(8), modprobe(8)


smartpqi

package: man-pages

title: smartpqi(4)

summary: Microsemi Smart Family SCSI driver

text:
# smartpqi(4)

## NAME
smartpqi - Microsemi Smart Family SCSI driver

## SYNOPSIS
modprobe smartpqi

[disable_device_id_wildcards={0|1}] [disable_heartbeat={0|1}] [disable_ctrl_shutdown={0|1}] [lockup_action={none|reboot|panic}] [expose_ld_first={0|1}] [hide_vsep={0|1}]

## DESCRIPTION
smartpqi is a SCSI driver for Microsemi Smart Family controllers.

### Supported ioctl() operations
For compatibility with applications written for the cciss(4) and hpsa(4) drivers, many, but not all of the ioctl(2) operations supported by the hpsa driver are also supported by the smartpqi driver. The data structures used by these operations are described in the Linux kernel source file include/linux/cciss_ioctl.h.

CCISS_DEREGDISK, CCISS_REGNEWDISK, CCISS_REGNEWD

These operations all do exactly the same thing, which is to cause the driver to re-scan for new devices. This does exactly the same thing as writing to the smartpqi-specific host rescan attribute.

CCISS_GETPCIINFO

This operation returns the PCI domain, bus, device, and function and "board ID" (PCI subsystem ID).

CCISS_GETDRIVVER

This operation returns the driver version in four bytes, encoded as:

```
(major_version << 28) | (minor_version << 24) |

        (release << 16) | revision

```

CCISS_PASSTHRU

Allows BMIC and CISS commands to be passed through to the controller.

### Boot options
disable_device_id_wildcards={0|1}

Disables support for device ID wildcards. The default value is 0.

disable_heartbeat={0|1}

Disables support for the controller's heartbeat check. This parameter is used for debugging purposes. The default value is 0, leaving the controller's heartbeat check active.

disable_ctrl_shutdown={0|1}

Disables support for shutting down the controller in the event of a controller lockup. The default value is 0.

lockup_action={none|reboot|panic}

Specifies the action the driver takes when a controller lockup is detected. The default action is none. parameter

action

none

take controller offline only

reboot

reboot the system

panic

panic the system

expose_ld_first={0|1}

This option enables support for exposing logical devices to the operating system before physical devices. The default value is 0.

hide_vsep={0|1}

This option enables disabling exposure of the virtual SEP to the host. This is usually associated with direct attached drives. The default value is 0.

## FILES

### Device nodes
Logical drives are accessed via the SCSI disk driver (sd), tape drives via the SCSI tape driver (st), and the RAID controller via the SCSI generic driver (sg), with device nodes named /dev/sd*, /dev/st*, and /dev/sg*, respectively.

### SmartPQI-specific host attribute files in /sys
/sys/class/scsi_host/host*/rescan

The host rescan attribute is a write-only attribute. Writing to this attribute will cause the driver to scan for new, changed, or removed devices (e.g., hot-plugged tape drives, or newly configured or deleted logical drives) and notify the SCSI mid-layer of any changes detected. Usually this action is triggered automatically by configuration changes, so the user should not normally have to write to this file. Doing so may be useful when hot-plugging devices such as tape drives or entire storage boxes containing pre-configured logical drives.

/sys/class/scsi_host/host*/version

The host version attribute is a read-only attribute. This attribute contains the driver version and the controller firmware version.

For example:

```
$
cat /sys/class/scsi_host/host1/version
driver: 1.1.2-126
firmware: 1.29-112

```

/sys/class/scsi_host/host*/lockup_action

The host lockup_action attribute is a read/write attribute. This attribute will cause the driver to perform a specific action in the unlikely event that a controller lockup has been detected. See OPTIONS above for an explanation of the lockup_action values.

/sys/class/scsi_host/host*/driver_version

The driver_version attribute is read-only. This attribute contains the smartpqi driver version.

For example:

```
$
cat /sys/class/scsi_host/host1/driver_version
1.1.2-126

```

/sys/class/scsi_host/host*/firmware_version

The firmware_version attribute is read-only. This attribute contains the controller firmware version.

For example:

```
$
cat /sys/class/scsi_host/host1/firmware_version
1.29-112

```

/sys/class/scsi_host/host*/model

The model attribute is read-only. This attribute contains the product identification string of the controller.

For example:

```
$
cat /sys/class/scsi_host/host1/model
1100-16i

```

/sys/class/scsi_host/host*/serial_number

The serial_number attribute is read-only. This attribute contains the unique identification number of the controller.

For example:

```
$
cat /sys/class/scsi_host/host1/serial_number
6A316373777

```

/sys/class/scsi_host/host*/vendor

The vendor attribute is read-only. This attribute contains the vendor identification string of the controller.

For example:

```
$
cat /sys/class/scsi_host/host1/vendor
Adaptec

```

### SmartPQI-specific disk attribute files in /sys
In the file specifications below, c stands for the number of the appropriate SCSI controller, b is the bus number, t the target number, and l is the logical unit number (LUN).

/sys/class/scsi_disk/c:b:t:l/device/raid_level

The raid_level attribute is read-only. This attribute contains the RAID level of each logical drive.

For example:

```
$
cat /sys/class/scsi_disk/4:0:0:0/device/raid_level
RAID 0

```

/sys/class/scsi_disk/c:b:t:l/device/sas_address

The sas_address attribute is read-only. This attribute contains the unique identifier of the disk.

For example:

```
$
cat /sys/class/scsi_disk/1:0:3:0/device/sas_address
0x5001173d028543a2

```

/sys/class/scsi_disk/c:b:t:l/device/ssd_smart_path_enabled

The ssd_smart_path_enabled attribute is read-only. This attribute is for ioaccel-enabled volumes. (Ioaccel is an alternative driver submission path that allows the driver to send I/O requests directly to backend SCSI devices, bypassing the controller firmware. This results in an increase in performance. This method is used for HBA disks and for logical volumes comprised of SSDs.) Contains 1 if ioaccel is enabled for the volume and 0 otherwise.

For example:

```
$
cat /sys/class/scsi_disk/1:0:3:0/device/ssd_smart_path_enabled
0

```

## VERSIONS
The smartpqi driver was added in Linux 4.9.

## NOTES

### Configuration
To configure a Microsemi Smart Family controller, refer to the User Guide for the controller, which can be found by searching for the specific controller at https://storage.microsemi.com/.

## SEE ALSO
cciss(4), hpsa(4), sd(4), st(4)

Documentation/ABI/testing/sysfs-bus-pci-devices-cciss in the Linux kernel source tree.


st

title: st(4)

summary: SCSI tape device

text:
# st(4)

## NAME
st - SCSI tape device

## SYNOPSIS

```
#include <sys/mtio.h>
```

```
int ioctl(int fd, int request [, (void *)arg3]);
int ioctl(int fd, MTIOCTOP, (struct mtop *)mt_cmd);
int ioctl(int fd, MTIOCGET, (struct mtget *)mt_status);
int ioctl(int fd, MTIOCPOS, (struct mtpos *)mt_pos);
```

## DESCRIPTION
The st driver provides the interface to a variety of SCSI tape devices. Currently, the driver takes control of all detected devices of type “sequential-access”. The st driver uses major device number 9.

Each device uses eight minor device numbers. The lowermost five bits in the minor numbers are assigned sequentially in the order of detection. In the 2.6 kernel, the bits above the eight lowermost bits are concatenated to the five lowermost bits to form the tape number. The minor numbers can be grouped into two sets of four numbers: the principal (auto-rewind) minor device numbers, n, and the “no-rewind” device numbers, (n + 128). Devices opened using the principal device number will be sent a REWIND command when they are closed. Devices opened using the “no-rewind” device number will not. (Note that using an auto-rewind device for positioning the tape with, for instance, mt does not lead to the desired result: the tape is rewound after the mt command and the next command starts from the beginning of the tape).

Within each group, four minor numbers are available to define devices with different characteristics (block size, compression, density, etc.) When the system starts up, only the first device is available. The other three are activated when the default characteristics are defined (see below). (By changing compile-time constants, it is possible to change the balance between the maximum number of tape drives and the number of minor numbers for each drive. The default allocation allows control of 32 tape drives. For instance, it is possible to control up to 64 tape drives with two minor numbers for different options.)

Devices are typically created by:

```
mknod -m 666 /dev/st0 c 9 0
mknod -m 666 /dev/st0l c 9 32
mknod -m 666 /dev/st0m c 9 64
mknod -m 666 /dev/st0a c 9 96
mknod -m 666 /dev/nst0 c 9 128
mknod -m 666 /dev/nst0l c 9 160
mknod -m 666 /dev/nst0m c 9 192
mknod -m 666 /dev/nst0a c 9 224
```

There is no corresponding block device.

The driver uses an internal buffer that has to be large enough to hold at least one tape block. In kernels before 2.1.121, the buffer is allocated as one contiguous block. This limits the block size to the largest contiguous block of memory the kernel allocator can provide. The limit is currently 128 kB for 32-bit architectures and 256 kB for 64-bit architectures. In newer kernels the driver allocates the buffer in several parts if necessary. By default, the maximum number of parts is 16. This means that the maximum block size is very large (2 MB if allocation of 16 blocks of 128 kB succeeds).

The driver's internal buffer size is determined by a compile-time constant which can be overridden with a kernel startup option. In addition to this, the driver tries to allocate a larger temporary buffer at run time if necessary. However, run-time allocation of large contiguous blocks of memory may fail and it is advisable not to rely too much on dynamic buffer allocation with kernels older than 2.1.121 (this applies also to demand-loading the driver with kerneld or kmod).

The driver does not specifically support any tape drive brand or model. After system start-up the tape device options are defined by the drive firmware. For example, if the drive firmware selects fixed-block mode, the tape device uses fixed-block mode. The options can be changed with explicit ioctl(2) calls and remain in effect when the device is closed and reopened. Setting the options affects both the auto-rewind and the nonrewind device.

Different options can be specified for the different devices within the subgroup of four. The options take effect when the device is opened. For example, the system administrator can define one device that writes in fixed-block mode with a certain block size, and one which writes in variable-block mode (if the drive supports both modes).

The driver supports tape partitions if they are supported by the drive. (Note that the tape partitions have nothing to do with disk partitions. A partitioned tape can be seen as several logical tapes within one medium.) Partition support has to be enabled with an ioctl(2). The tape location is preserved within each partition across partition changes. The partition used for subsequent tape operations is selected with an ioctl(2). The partition switch is executed together with the next tape operation in order to avoid unnecessary tape movement. The maximum number of partitions on a tape is defined by a compile-time constant (originally four). The driver contains an ioctl(2) that can format a tape with either one or two partitions.

Device /dev/tape is usually created as a hard or soft link to the default tape device on the system.

Starting from kernel 2.6.2, the driver exports in the sysfs directory /sys/class/scsi_tape the attached devices and some parameters assigned to the devices.

### Data transfer
The driver supports operation in both fixed-block mode and variable-block mode (if supported by the drive). In fixed-block mode the drive writes blocks of the specified size and the block size is not dependent on the byte counts of the write system calls. In variable-block mode one tape block is written for each write call and the byte count determines the size of the corresponding tape block. Note that the blocks on the tape don't contain any information about the writing mode: when reading, the only important thing is to use commands that accept the block sizes on the tape.

In variable-block mode the read byte count does not have to match the tape block size exactly. If the byte count is larger than the next block on tape, the driver returns the data and the function returns the actual block size. If the block size is larger than the byte count, an error is returned.

In fixed-block mode the read byte counts can be arbitrary if buffering is enabled, or a multiple of the tape block size if buffering is disabled. Kernels before 2.1.121 allow writes with arbitrary byte count if buffering is enabled. In all other cases (kernel before 2.1.121 with buffering disabled or newer kernel) the write byte count must be a multiple of the tape block size.

In the 2.6 kernel, the driver tries to use direct transfers between the user buffer and the device. If this is not possible, the driver's internal buffer is used. The reasons for not using direct transfers include improper alignment of the user buffer (default is 512 bytes but this can be changed by the HBA driver), one or more pages of the user buffer not reachable by the SCSI adapter, and so on.

A filemark is automatically written to tape if the last tape operation before close was a write.

When a filemark is encountered while reading, the following happens. If there are data remaining in the buffer when the filemark is found, the buffered data is returned. The next read returns zero bytes. The following read returns data from the next file. The end of recorded data is signaled by returning zero bytes for two consecutive read calls. The third read returns an error.

### Ioctls
The driver supports three ioctl(2) requests. Requests not recognized by the st driver are passed to the SCSI driver. The definitions below are from /usr/include/linux/mtio.h:

### MTIOCTOP — perform a tape operation
This request takes an argument of type (struct mtop *). Not all drives support all operations. The driver returns an EIO error if the drive rejects an operation.

```
/* Structure for MTIOCTOP - mag tape op command: */
struct mtop {

    short   mt_op;       /* operations defined below */

    int     mt_count;    /* how many of them */
};
```

Magnetic tape operations for normal tape use:

MTBSF

Backward space over mt_count filemarks.

MTBSFM

Backward space over mt_count filemarks. Reposition the tape to the EOT side of the last filemark.

MTBSR

Backward space over mt_count records (tape blocks).

MTBSS

Backward space over mt_count setmarks.

MTCOMPRESSION

Enable compression of tape data within the drive if mt_count is nonzero and disable compression if mt_count is zero. This command uses the MODE page 15 supported by most DATs.

MTEOM

Go to the end of the recorded media (for appending files).

MTERASE

Erase tape. With 2.6 kernel, short erase (mark tape empty) is performed if the argument is zero. Otherwise, long erase (erase all) is done.

MTFSF

Forward space over mt_count filemarks.

MTFSFM

Forward space over mt_count filemarks. Reposition the tape to the BOT side of the last filemark.

MTFSR

Forward space over mt_count records (tape blocks).

MTFSS

Forward space over mt_count setmarks.

MTLOAD

Execute the SCSI load command. A special case is available for some HP autoloaders. If mt_count is the constant MT_ST_HPLOADER_OFFSET plus a number, the number is sent to the drive to control the autoloader.

MTLOCK

Lock the tape drive door.

MTMKPART

Format the tape into one or two partitions. If mt_count is positive, it gives the size of partition 1 and partition 0 contains the rest of the tape. If mt_count is zero, the tape is formatted into one partition. From kernel version 4.6, a negative mt_count specifies the size of partition 0 and the rest of the tape contains partition 1. The physical ordering of partitions depends on the drive. This command is not allowed for a drive unless the partition support is enabled for the drive (see MT_ST_CAN_PARTITIONS below).

MTNOP

No op—flushes the driver's buffer as a side effect. Should be used before reading status with MTIOCGET.

MTOFFL

Rewind and put the drive off line.

MTRESET

Reset drive.

MTRETEN

Re-tension tape.

MTREW

Rewind.

MTSEEK

Seek to the tape block number specified in mt_count. This operation requires either a SCSI-2 drive that supports the LOCATE command (device-specific address) or a Tandberg-compatible SCSI-1 drive (Tandberg, Archive Viper, Wangtek, ...). The block number should be one that was previously returned by MTIOCPOS if device-specific addresses are used.

MTSETBLK

Set the drive's block length to the value specified in mt_count. A block length of zero sets the drive to variable block size mode.

MTSETDENSITY

Set the tape density to the code in mt_count. The density codes supported by a drive can be found from the drive documentation.

MTSETPART

The active partition is switched to mt_count. The partitions are numbered from zero. This command is not allowed for a drive unless the partition support is enabled for the drive (see MT_ST_CAN_PARTITIONS below).

MTUNLOAD

Execute the SCSI unload command (does not eject the tape).

MTUNLOCK

Unlock the tape drive door.

MTWEOF

Write mt_count filemarks.

MTWSM

Write mt_count setmarks.

Magnetic tape operations for setting of device options (by the superuser):

MTSETDRVBUFFER

Set various drive and driver options according to bits encoded in mt_count. These consist of the drive's buffering mode, a set of Boolean driver options, the buffer write threshold, defaults for the block size and density, and timeouts (only in kernels 2.1 and later). A single operation can affect only one item in the list below (the Booleans counted as one item.)

A value having zeros in the high-order 4 bits will be used to set the drive's buffering mode. The buffering modes are:

0

The drive will not report GOOD status on write commands until the data blocks are actually written to the medium.

1

The drive may report GOOD status on write commands as soon as all the data has been transferred to the drive's internal buffer.

2

The drive may report GOOD status on write commands as soon as (a) all the data has been transferred to the drive's internal buffer, and (b) all buffered data from different initiators has been successfully written to the medium.

To control the write threshold the value in mt_count must include the constant MT_ST_WRITE_THRESHOLD bitwise ORed with a block count in the low 28 bits. The block count refers to 1024-byte blocks, not the physical block size on the tape. The threshold cannot exceed the driver's internal buffer size (see DESCRIPTION, above).

To set and clear the Boolean options the value in mt_count must include one of the constants MT_ST_BOOLEANS, MT_ST_SETBOOLEANS, MT_ST_CLEARBOOLEANS, or MT_ST_DEFBOOLEANS bitwise ORed with whatever combination of the following options is desired. Using MT_ST_BOOLEANS the options can be set to the values defined in the corresponding bits. With MT_ST_SETBOOLEANS the options can be selectively set and with MT_ST_DEFBOOLEANS selectively cleared.

The default options for a tape device are set with MT_ST_DEFBOOLEANS. A nonactive tape device (e.g., device with minor 32 or 160) is activated when the default options for it are defined the first time. An activated device inherits from the device activated at start-up the options not set explicitly.

The Boolean options are:

MT_ST_BUFFER_WRITES (Default: true)

Buffer all write operations in fixed-block mode. If this option is false and the drive uses a fixed block size, then all write operations must be for a multiple of the block size. This option must be set false to write reliable multivolume archives.

MT_ST_ASYNC_WRITES (Default: true)

When this option is true, write operations return immediately without waiting for the data to be transferred to the drive if the data fits into the driver's buffer. The write threshold determines how full the buffer must be before a new SCSI write command is issued. Any errors reported by the drive will be held until the next operation. This option must be set false to write reliable multivolume archives.

MT_ST_READ_AHEAD (Default: true)

This option causes the driver to provide read buffering and read-ahead in fixed-block mode. If this option is false and the drive uses a fixed block size, then all read operations must be for a multiple of the block size.

MT_ST_TWO_FM (Default: false)

This option modifies the driver behavior when a file is closed. The normal action is to write a single filemark. If the option is true, the driver will write two filemarks and backspace over the second one.

Note: This option should not be set true for QIC tape drives since they are unable to overwrite a filemark. These drives detect the end of recorded data by testing for blank tape rather than two consecutive filemarks. Most other current drives also detect the end of recorded data and using two filemarks is usually necessary only when interchanging tapes with some other systems.

MT_ST_DEBUGGING (Default: false)

This option turns on various debugging messages from the driver (effective only if the driver was compiled with DEBUG defined nonzero).

MT_ST_FAST_EOM (Default: false)

This option causes the MTEOM operation to be sent directly to the drive, potentially speeding up the operation but causing the driver to lose track of the current file number normally returned by the MTIOCGET request. If MT_ST_FAST_EOM is false, the driver will respond to an MTEOM request by forward spacing over files.

MT_ST_AUTO_LOCK (Default: false)

When this option is true, the drive door is locked when the device file is opened and unlocked when it is closed.

MT_ST_DEF_WRITES (Default: false)

The tape options (block size, mode, compression, etc.) may change when changing from one device linked to a drive to another device linked to the same drive depending on how the devices are defined. This option defines when the changes are enforced by the driver using SCSI-commands and when the drives auto-detection capabilities are relied upon. If this option is false, the driver sends the SCSI-commands immediately when the device is changed. If the option is true, the SCSI-commands are not sent until a write is requested. In this case, the drive firmware is allowed to detect the tape structure when reading and the SCSI-commands are used only to make sure that a tape is written according to the correct specification.

MT_ST_CAN_BSR (Default: false)

When read-ahead is used, the tape must sometimes be spaced backward to the correct position when the device is closed and the SCSI command to space backward over records is used for this purpose. Some older drives can't process this command reliably and this option can be used to instruct the driver not to use the command. The end result is that, with read-ahead and fixed-block mode, the tape may not be correctly positioned within a file when the device is closed. With 2.6 kernel, the default is true for drives supporting SCSI-3.

MT_ST_NO_BLKLIMS (Default: false)

Some drives don't accept the READ BLOCK LIMITS SCSI command. If this is used, the driver does not use the command. The drawback is that the driver can't check before sending commands if the selected block size is acceptable to the drive.

MT_ST_CAN_PARTITIONS (Default: false)

This option enables support for several partitions within a tape. The option applies to all devices linked to a drive.

MT_ST_SCSI2LOGICAL (Default: false)

This option instructs the driver to use the logical block addresses defined in the SCSI-2 standard when performing the seek and tell operations (both with MTSEEK and MTIOCPOS commands and when changing tape partition). Otherwise, the device-specific addresses are used. It is highly advisable to set this option if the drive supports the logical addresses because they count also filemarks. There are some drives that support only the logical block addresses.

MT_ST_SYSV (Default: false)

When this option is enabled, the tape devices use the System V semantics. Otherwise, the BSD semantics are used. The most important difference between the semantics is what happens when a device used for reading is closed: in System V semantics the tape is spaced forward past the next filemark if this has not happened while using the device. In BSD semantics the tape position is not changed.

MT_NO_WAIT (Default: false)

Enables immediate mode (i.e., don't wait for the command to finish) for some commands (e.g., rewind).

An example:

```
struct mtop mt_cmd;
mt_cmd.mt_op = MTSETDRVBUFFER;
mt_cmd.mt_count = MT_ST_BOOLEANS |

        MT_ST_BUFFER_WRITES | MT_ST_ASYNC_WRITES;
ioctl(fd, MTIOCTOP, mt_cmd);
```

The default block size for a device can be set with MT_ST_DEF_BLKSIZE and the default density code can be set with MT_ST_DEFDENSITY. The values for the parameters are or'ed with the operation code.

With kernels 2.1.x and later, the timeout values can be set with the subcommand MT_ST_SET_TIMEOUT ORed with the timeout in seconds. The long timeout (used for rewinds and other commands that may take a long time) can be set with MT_ST_SET_LONG_TIMEOUT. The kernel defaults are very long to make sure that a successful command is not timed out with any drive. Because of this, the driver may seem stuck even if it is only waiting for the timeout. These commands can be used to set more practical values for a specific drive. The timeouts set for one device apply for all devices linked to the same drive.

Starting from kernels 2.4.19 and 2.5.43, the driver supports a status bit which indicates whether the drive requests cleaning. The method used by the drive to return cleaning information is set using the MT_ST_SEL_CLN subcommand. If the value is zero, the cleaning bit is always zero. If the value is one, the TapeAlert data defined in the SCSI-3 standard is used (not yet implemented). Values 2–17 are reserved. If the lowest eight bits are >= 18, bits from the extended sense data are used. The bits 9–16 specify a mask to select the bits to look at and the bits 17–23 specify the bit pattern to look for. If the bit pattern is zero, one or more bits under the mask indicate the cleaning request. If the pattern is nonzero, the pattern must match the masked sense data byte.

### MTIOCGET — get status
This request takes an argument of type (struct mtget *).

```
/* structure for MTIOCGET - mag tape get status command */
struct mtget {

    long     mt_type;

    long     mt_resid;

    /* the following registers are device dependent */

    long     mt_dsreg;

    long     mt_gstat;

    long     mt_erreg;

    /* The next two fields are not always used */

    daddr_t  mt_fileno;

    daddr_t  mt_blkno;
};
```

mt_type

The header file defines many values for mt_type, but the current driver reports only the generic types MT_ISSCSI1 (Generic SCSI-1 tape) and MT_ISSCSI2 (Generic SCSI-2 tape).

mt_resid

contains the current tape partition number.

mt_dsreg

reports the drive's current settings for block size (in the low 24 bits) and density (in the high 8 bits). These fields are defined by MT_ST_BLKSIZE_SHIFT, MT_ST_BLKSIZE_MASK, MT_ST_DENSITY_SHIFT, and MT_ST_DENSITY_MASK.

mt_gstat

reports generic (device independent) status information. The header file defines macros for testing these status bits:

GMT_EOF(x): The tape is positioned just after a filemark (always false after an MTSEEK operation).

GMT_BOT(x): The tape is positioned at the beginning of the first file (always false after an MTSEEK operation).

GMT_EOT(x): A tape operation has reached the physical End Of Tape.

GMT_SM(x): The tape is currently positioned at a setmark (always false after an MTSEEK operation).

GMT_EOD(x): The tape is positioned at the end of recorded data.

GMT_WR_PROT(x): The drive is write-protected. For some drives this can also mean that the drive does not support writing on the current medium type.

GMT_ONLINE(x): The last open(2) found the drive with a tape in place and ready for operation.

GMT_D_6250(x), GMT_D_1600(x), GMT_D_800(x): This “generic” status information reports the current density setting for 9-track ½" tape drives only.

GMT_DR_OPEN(x): The drive does not have a tape in place.

GMT_IM_REP_EN(x): Immediate report mode. This bit is set if there are no guarantees that the data has been physically written to the tape when the write call returns. It is set zero only when the driver does not buffer data and the drive is set not to buffer data.

GMT_CLN(x): The drive has requested cleaning. Implemented in kernels since 2.4.19 and 2.5.43.

mt_erreg

The only field defined in mt_erreg is the recovered error count in the low 16 bits (as defined by MT_ST_SOFTERR_SHIFT and MT_ST_SOFTERR_MASK). Due to inconsistencies in the way drives report recovered errors, this count is often not maintained (most drives do not by default report soft errors but this can be changed with a SCSI MODE SELECT command).

mt_fileno

reports the current file number (zero-based). This value is set to -1 when the file number is unknown (e.g., after MTBSS or MTSEEK).

mt_blkno

reports the block number (zero-based) within the current file. This value is set to -1 when the block number is unknown (e.g., after MTBSF, MTBSS, or MTSEEK).

### MTIOCPOS — get tape position
This request takes an argument of type (struct mtpos *) and reports the drive's notion of the current tape block number, which is not the same as mt_blkno returned by MTIOCGET. This drive must be a SCSI-2 drive that supports the READ POSITION command (device-specific address) or a Tandberg-compatible SCSI-1 drive (Tandberg, Archive Viper, Wangtek, ... ).

```
/* structure for MTIOCPOS - mag tape get position command */
struct mtpos {

    long mt_blkno;    /* current block number */
};
```

## RETURN VALUE
EACCES

An attempt was made to write or erase a write-protected tape. (This error is not detected during open(2).)

EBUSY

The device is already in use or the driver was unable to allocate a buffer.

EFAULT

The command parameters point to memory not belonging to the calling process.

EINVAL

An ioctl(2) had an invalid argument, or a requested block size was invalid.

EIO

The requested operation could not be completed.

ENOMEM

The byte count in read(2) is smaller than the next physical block on the tape. (Before 2.2.18 and 2.4.0 the extra bytes have been silently ignored.)

ENOSPC

A write operation could not be completed because the tape reached end-of-medium.

ENOSYS

Unknown ioctl(2).

ENXIO

During opening, the tape device does not exist.

EOVERFLOW

An attempt was made to read or write a variable-length block that is larger than the driver's internal buffer.

EROFS

Open is attempted with O_WRONLY or O_RDWR when the tape in the drive is write-protected.

## FILES
/dev/st*

the auto-rewind SCSI tape devices

/dev/nst*

the nonrewind SCSI tape devices

## NOTES
1.

When exchanging data between systems, both systems have to agree on the physical tape block size. The parameters of a drive after startup are often not the ones most operating systems use with these devices. Most systems use drives in variable-block mode if the drive supports that mode. This applies to most modern drives, including DATs, 8mm helical scan drives, DLTs, etc. It may be advisable to use these drives in variable-block mode also in Linux (i.e., use MTSETBLK or MTSETDEFBLK at system startup to set the mode), at least when exchanging data with a foreign system. The drawback of this is that a fairly large tape block size has to be used to get acceptable data transfer rates on the SCSI bus.

2.

Many programs (e.g., tar(1)) allow the user to specify the blocking factor on the command line. Note that this determines the physical block size on tape only in variable-block mode.

3.

In order to use SCSI tape drives, the basic SCSI driver, a SCSI-adapter driver and the SCSI tape driver must be either configured into the kernel or loaded as modules. If the SCSI-tape driver is not present, the drive is recognized but the tape support described in this page is not available.

4.

The driver writes error messages to the console/log. The SENSE codes written into some messages are automatically translated to text if verbose SCSI messages are enabled in kernel configuration.

5.

The driver's internal buffering allows good throughput in fixed-block mode also with small read(2) and write(2) byte counts. With direct transfers this is not possible and may cause a surprise when moving to the 2.6 kernel. The solution is to tell the software to use larger transfers (often telling it to use larger blocks). If this is not possible, direct transfers can be disabled.

## SEE ALSO
mt(1)

The file drivers/scsi/README.st or Documentation/scsi/st.txt (kernel >= 2.6) in the Linux kernel source tree contains the most recent information about the driver and its configuration possibilities


tty

title: tty(4)

summary: controlling terminal

text:
# tty(4)

## NAME
tty - controlling terminal

## DESCRIPTION
The file /dev/tty is a character file with major number 5 and minor number 0, usually with mode 0666 and ownership root:tty. It is a synonym for the controlling terminal of a process, if any.

In addition to the ioctl(2) requests supported by the device that tty refers to, the ioctl(2) request TIOCNOTTY is supported.

### TIOCNOTTY
Detach the calling process from its controlling terminal.

If the process is the session leader, then SIGHUP and SIGCONT signals are sent to the foreground process group and all processes in the current session lose their controlling tty.

This ioctl(2) call works only on file descriptors connected to /dev/tty. It is used by daemon processes when they are invoked by a user at a terminal. The process attempts to open /dev/tty. If the open succeeds, it detaches itself from the terminal by using TIOCNOTTY, while if the open fails, it is obviously not attached to a terminal and does not need to detach itself.

## FILES
/dev/tty

## SEE ALSO
chown(1), mknod(1), ioctl(2), ioctl_console(2), ioctl_tty(2), termios(3), ttyS(4), vcs(4), pty(7), agetty(8), mingetty(8)


ttyS

title: ttyS(4)

summary: serial terminal lines

text:
# ttyS(4)

## NAME
ttyS - serial terminal lines

## DESCRIPTION
ttyS[0-3] are character devices for the serial terminal lines.

They are typically created by:

```
mknod -m 660 /dev/ttyS0 c 4 64 # base address 0x3f8
mknod -m 660 /dev/ttyS1 c 4 65 # base address 0x2f8
mknod -m 660 /dev/ttyS2 c 4 66 # base address 0x3e8
mknod -m 660 /dev/ttyS3 c 4 67 # base address 0x2e8
chown root:tty /dev/ttyS[0-3]
```

## FILES
/dev/ttyS[0-3]

## SEE ALSO
chown(1), mknod(1), tty(4), agetty(8), mingetty(8), setserial(8)


vcs

title: vcs(4)

summary: virtual console memory

text:
# vcs(4)

## NAME
vcs, vcsa - virtual console memory

## DESCRIPTION
/dev/vcs0 is a character device with major number 7 and minor number 0, usually with mode 0644 and ownership root:tty. It refers to the memory of the currently displayed virtual console terminal.

/dev/vcs[1-63] are character devices for virtual console terminals, they have major number 7 and minor number 1 to 63, usually mode 0644 and ownership root:tty. /dev/vcsa[0-63] are the same, but using unsigned shorts (in host byte order) that include attributes, and prefixed with four bytes giving the screen dimensions and cursor position: lines, columns, x, y. (x = y = 0 at the top left corner of the screen.)

When a 512-character font is loaded, the 9th bit position can be fetched by applying the ioctl(2) VT_GETHIFONTMASK operation (available in Linux kernels 2.6.18 and above) on /dev/tty[1-63]; the value is returned in the unsigned short pointed to by the third ioctl(2) argument.

These devices replace the screendump ioctl(2) operations of ioctl_console(2), so the system administrator can control access using filesystem permissions.

The devices for the first eight virtual consoles may be created by:

```
for x in 0 1 2 3 4 5 6 7 8; do

    mknod -m 644 /dev/vcs$x c 7 $x;

    mknod -m 644 /dev/vcsa$x c 7 $[$x+128];
done
chown root:tty /dev/vcs*
```

No ioctl(2) requests are supported.

## FILES
/dev/vcs[0-63]

/dev/vcsa[0-63]

## VERSIONS
Introduced with version 1.1.92 of the Linux kernel.

## EXAMPLES
You may do a screendump on vt3 by switching to vt1 and typing

```
cat /dev/vcs3 >foo
```

Note that the output does not contain newline characters, so some processing may be required, like in

```
fold -w 81 /dev/vcs3 | lpr
```

or (horrors)

```
setterm -dump 3 -file /proc/self/fd/1
```

The /dev/vcsa0 device is used for Braille support.

This program displays the character and screen attributes under the cursor of the second virtual console, then changes the background color there:

```
#include <unistd.h>
#include <stdlib.h>
#include <stdio.h>
#include <fcntl.h>
#include <sys/ioctl.h>
#include <linux/vt.h>
int
main(void)
{

    int fd;

    char *device = "/dev/vcsa2";

    char *console = "/dev/tty2";

    struct {unsigned char lines, cols, x, y;} scrn;

    unsigned short s;

    unsigned short mask;

    unsigned char attrib;

    int ch;

    fd = open(console, O_RDWR);

    if (fd < 0) {

        perror(console);

        exit(EXIT_FAILURE);

    }

    if (ioctl(fd, VT_GETHIFONTMASK, &mask) < 0) {

        perror("VT_GETHIFONTMASK");

        exit(EXIT_FAILURE);

    }

    (void) close(fd);

    fd = open(device, O_RDWR);

    if (fd < 0) {

        perror(device);

        exit(EXIT_FAILURE);

    }

    (void) read(fd, &scrn, 4);

    (void) lseek(fd, 4 + 2*(scrn.y*scrn.cols + scrn.x), SEEK_SET);

    (void) read(fd, &s, 2);

    ch = s & 0xff;

    if (s & mask)

        ch |= 0x100;

    attrib = ((s & ~mask) >> 8);

    printf("ch=%#03x attrib=%#02x\n", ch, attrib);

    s ^= 0x1000;

    (void) lseek(fd, -2, SEEK_CUR);

    (void) write(fd, &s, 2);

    exit(EXIT_SUCCESS);
}
```

## SEE ALSO
ioctl_console(2), tty(4), ttyS(4), gpm(8)


veth

title: veth(4)

summary: Virtual Ethernet Device

text:
# veth(4)

## NAME
veth - Virtual Ethernet Device

## DESCRIPTION
The veth devices are virtual Ethernet devices. They can act as tunnels between network namespaces to create a bridge to a physical network device in another namespace, but can also be used as standalone network devices.

veth devices are always created in interconnected pairs. A pair can be created using the command:

```
# ip link add <p1-name> type veth peer name <p2-name>
```

In the above, p1-name and p2-name are the names assigned to the two connected end points.

Packets transmitted on one device in the pair are immediately received on the other device. When either devices is down the link state of the pair is down.

veth device pairs are useful for combining the network facilities of the kernel together in interesting ways. A particularly interesting use case is to place one end of a veth pair in one network namespace and the other end in another network namespace, thus allowing communication between network namespaces. To do this, one can provide the netns parameter when creating the interfaces:

```
# ip link add <p1-name> netns <p1-ns> type veth peer <p2-name> netns <p2-ns>
```

or, for an existing veth pair, move one side to the other namespace:

```
# ip link set <p2-name> netns <p2-ns>
```

ethtool(8) can be used to find the peer of a veth network interface, using commands something like:

```
# ip link add ve_A type veth peer name ve_B   # Create veth pair
# ethtool -S ve_A         # Discover interface index of peer
NIC statistics:

     peer_ifindex: 16
# ip link | grep '^16:'   # Look up interface
16: ve_B@ve_A: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc ...
```

## SEE ALSO
clone(2), network_namespaces(7), ip(8), ip-link(8), ip-netns(8)


wavelan

title: wavelan(4)

summary: AT&T GIS WaveLAN ISA device driver

text:
# wavelan(4)

## NAME
wavelan - AT&T GIS WaveLAN ISA device driver

## SYNOPSIS

```
insmod wavelan_cs.o [io=B,B..] [ irq=I,I..] [name=N,N..]
```

## DESCRIPTION
This driver is obsolete: it was removed from the kernel in version 2.6.35.

wavelan is the low-level device driver for the NCR / AT&T / Lucent WaveLAN ISA and Digital (DEC) RoamAbout DS wireless ethernet adapter. This driver is available as a module or might be compiled in the kernel. This driver supports multiple cards in both forms (up to 4) and allocates the next available ethernet device (eth0..eth#) for each card found, unless a device name is explicitly specified (see below). This device name will be reported in the kernel log file with the MAC address, NWID, and frequency used by the card.

### Parameters
This section applies to the module form (parameters passed on the insmod(8) command line). If the driver is included in the kernel, use the ether=IRQ,IO,NAME syntax on the kernel command line.

io

Specify the list of base addresses where to search for wavelan cards (setting by dip switch on the card). If you don't specify any io address, the driver will scan 0x390 and 0x3E0 addresses, which might conflict with other hardware...

irq

Set the list of IRQs that each wavelan card should use (the value is saved in permanent storage for future use).

name

Set the list of names to be used for each wavelan card device (name used by ifconfig(8)).

### Wireless extensions
Use iwconfig(8) to manipulate wireless extensions.

### NWID (or domain)
Set the network ID [0 to FFFF] or disable it [off]. As the NWID is stored in the card Permanent Storage Area, it will be reused at any further invocation of the driver.

### Frequency & channels
For the 2.4 GHz 2.00 Hardware, you are able to set the frequency by specifying one of the 10 defined channels (2.412, 2.422, 2.425, 2.4305, 2.432, 2.442, 2.452, 2.460, 2.462 or 2.484) or directly as a numeric value. The frequency is changed immediately and permanently. Frequency availability depends on the regulations...

### Statistics spy
Set a list of MAC addresses in the driver (up to 8) and get the last quality of link for each of those (see iwspy(8)).

### /proc/net/wireless
status is the status reported by the modem. Link quality reports the quality of the modulation on the air (direct sequence spread spectrum) [max = 16]. Level and Noise refer to the signal level and noise level [max = 64]. The crypt discarded packet and misc discarded packet counters are not implemented.

### Private ioctl
You may use iwpriv(8) to manipulate private ioctls.

### Quality and level threshold
Enables you to define the quality and level threshold used by the modem (packet below that level are discarded).

### Histogram
This functionality makes it possible to set a number of signal level intervals and to count the number of packets received in each of those defined intervals. This distribution might be used to calculate the mean value and standard deviation of the signal level.

### Specific notes
This driver fails to detect some non-NCR/AT&T/Lucent Wavelan cards. If this happens for you, you must look in the source code on how to add your card to the detection routine.

Some of the mentioned features are optional. You may enable to disable them by changing flags in the driver header and recompile.

## SEE ALSO
wavelan_cs(4), ifconfig(8), insmod(8), iwconfig(8), iwpriv(8), iwspy(8)