PROBLEM:	(QAR 45730 and QAR 46647)	(Patch ID: OSF410-400066)
********
DDR partially builds some device records.

This problem is extremely hard to detect, as the creation of device records
usually happens silently in the kernel as it encounters new devices.  Symptoms
of this error may be slight oddities in device behavior.  Unfortunately, the
extent to which behavior is affected cannot be predicted.

The problem can be seen most easily by executing the following :

      Invoke "ddr_config -s disk DEC RZ28B".

      The (failing) output should look as follows:
         Building Device Information for:
           Type = disk
           Vendor ID: "DEC"   Product ID: "RZ28B"

      Applying Modifications from Device Record for:
           Vendor ID: "DEC"   Product ID: "RZ28"
             TagQueueDepth = 0x4a

      The (correct) output should look as follows:

      Building Device Information for:
           Type = disk
           Vendor ID: "DEC"   Product ID: "RZ28B"

      Applying Modifications from Device Record for:
           Vendor ID: "DEC"   Product ID: "RZ28"
             TagQueueDepth = 0x4a

      Applying Modifications from Device Record for:
           Vendor ID: "DEC"   Product ID: "RZ28B"
             TagQueueDepth = 0x40

PROBLEM:	(QAR 45730 and QAR 46647)	(Patch ID: OSF410-400066)
********
The "ddr_config -x" option fails to compile a cam_data.c file from a version 
prior to Digital UNIX v4.0.

The following error messages will be reported:

       ddr_config.ORIG: Line 3233: Syntax Error
       ddr_config.ORIG: Line 3233: Failed parsing DENSITY_TBL entry

       Conversion of /sys/data/cam_data.c failed. 

Line numbers are relative to the temporary file /tmp/cam_data.tmp

Looking at the /tmp/cam_data.tmp file, the error occurs between two records
separated by a comma. For example:

       TYPE
       Record_A = { ....
       },                           <----- fails here
       Record_B = { ...
       };

PROBLEM:  (HPAQB16E6)	 (Patch ID: OSF410-400218)
********
The DDR subsystem did not appropriately handle SCSI devices that return
non-standard device types. The standard device types range from 0 (disk
device) to 9 (Communications Device).

For example, a custom SCSI device that returns a device type of UNKNOWN (0x1f)
could panic the system with the following message:

   "trap: invalid memory read access from kernel mode"

A device with a non-standard device type would ordinarily not be shown as
present on the system as it would require a custom SCSI device driver to 
access it (one which does not come with the base operating system).

Note: Non-standard device types are supported by CAM in pre-v4.0 releases.


FILE(s):

/sbin/ddr_config		subset OSFHWBASE410
CHECKSUM: 14256    256     RCSfile: ddr_config.c      RCS: 1.1.7.2
/sys/BINARY/ddr.mod		subset OSFBIN410
CHECKSUM: 07482     43
/etc/ddr.db			subset OSFHWBASE410
CHECKSUM: 43407     15 
/etc/.mrg..ddr.db		subset OSFHWBASE410
CHECKSUM: 01589      3		
