Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
ACC Installation and Configuration Guide > Appendix A Files, Utilities, and Daemons

Device Files

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

The device files that are used by the ACC product are automatically created as they are needed. If a daemon requires a device file that does not exist, the daemon will create it. If an application program that makes use of the ZCOM programmatic interface requires a device file that does not exist, the ZCOM Interface library call that requires the device file will create it.The following list shows the device files that are used by the ACC product.

The major number for the following device files is dynamically allocated upon system initialization, and can be determined using
% lsdev -d zcom0.

/dev/zmlog

This file is used by applications and utilities to send messages to the logging mechanism zmlog.

The minor number is 0xf00000.

/dev/zmon

This file is used by the zmon utility.

The minor number is 0x200000.

/dev/zglobal

This file is used by application programs that make the zinit() ZCOM Application Interface request.

The minor number is 0x100000.

/dev/zremote

This file is used by the znode utility.

The minor number is 0x300000.

/dev/zcom/pzlu00XXX

These files are used by programs that make the zluopen() ZCOM Application Interface request. These files are used for the select() functionality. The use of these files is transparent to the user.

The number in the device file name is decimal, and the minor number is the equivalent value in hex. For example, the file pzlu00012 has minor number 0xc.

/dev/zmuxbYYsZZ or
/dev/zmuxBXXbYYsZZ

A device file is required for each ACC MUX card that will be accessed on the system. The naming convention of the device file depends on the type of system being used.

For systems that have no extended bus converter addressing, the naming convention for the device files is/dev/zmuxbYYsZZ. The YY and ZZ represent the values that make up the hardware path to the card. The YY represents the bus converter address and the ZZ represents the card address.

For systems that do have extended bus converter addressing, the naming convention for the device files is /dev/zmuxBXXbYYsZZ. The XX, YY, and ZZ represent the values that make up the hardware path to the card. The XX represents the extended bus converter address. The YY and ZZ represent the bus converter address and card address respectively.

The format of the major number is 124 and the minor number is shown below. Note that the uppermost byte is always 0x40. Also note that the extended bus converter address is 0 if the system has no extended bus converter addressing.

23222120191817161514131211109876543210
40Ext. BC Addr.BC AddressCard Address

The hardware path for the ACC card can be found by entering:

   ioscan -f | grep ACC

Some typical examples are as shown below.

Example #1

The following ioscan -f output denotes a standard HP-PB system with no bus converter and the 8-channel ACC card has a card address of 4:

Class   I  H/W Path  Driver  S/W State  H/W Type   Descr.
nacc    0  4         nacc0   CLAIMED    INTERFACE  ACC MUX

The corresponding mux statement in the ttgen configuration file should be:

Mux 0 0:4 /opt/acc/z7200a/sample.zabs. 

The zero in the "0:4" term denotes no bus converter. The corresponding device file will be /dev/zmuxb0s4, where the minor number is 0x400004.

Example #2

The following ioscan -f output denotes a standard HP-PB system with bus converters. The 8-channel ACC card has a bus converter address of 56 and a card address of 48:

Class   I  H/W Path  Driver  S/W State  H/W Type    Descr.
nacc    0  56/48     nacc0   CLAIMED    INTERFACE   ACC MUX

The corresponding mux statement in the ttgen configuration file should be:

Mux 0 56:48 /opt/acc/z7200a/sample.zabs. 

The corresponding device file will be /dev/zmuxb56s48, where the minor number is 0x400e30.

Example #3

The following ioscan -f output denotes a standard HP-PB system with bus converters where the 8-channel ACC card has a bus converter address of 10/16 and a card address of 8:

  Class   I  H/W Path Driver  S/W State H/W Type   Descr.
  nacc    0  10/16/8  nacc0   CLAIMED   INTERFACE  ACC MUX

The corresponding mux statement in the ttgen configuration file should be:

Mux 0 10:16:8 /opt/acc/z7200a/sample.zabs. 

The corresponding device file will be /dev/zmuxB10b16s8, where the minor number is 0x40a408.

Example #4

The following ioscan -f output denotes an EISA system with no bus converter and the ACC card has a card address of 3:

Class  I  H/W Path  Driver  S/W State  H/W Type   Descr.
eacc   0  4/0/3     eacc0   CLAIMED    INTERFACE  EISA card HWP5400

The corresponding mux statement in the ttgen configuration file should be:

Mux 0 0:3 /opt/acc/z7400a/sample.zabs. 

The zero in the "0:" term denotes no bus converter. The corresponding device file will be /dev/zmuxb0s3, where the minor number is 0x400003.

Refer to the ACC Utilities Reference Guide for more details on the use of the zmlog, zmon, and znode utilities. Refer to the ACC Programmer's Reference Guide for more details on the ZCOM Programmatic Interface requests.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2000 Hewlett-Packard Development Company, L.P.