| Title: | DIGITAL UNIX (FORMERLY KNOWN AS DEC OSF/1) |
| Notice: | Welcome to the Digital UNIX Conference |
| Moderator: | SMURF::DENHAM |
| Created: | Thu Mar 16 1995 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 10068 |
| Total number of notes: | 35879 |
A customer sent me this question about making modifications in
/sys/data/cam_data.c for RZ29B disks behind a KZPSC. Does anyone have
any insight into this? By the way, this system is an AlphaServer 2100
4/200 running Digital UNIX 3.2G...
Thanks,
Olin
>When I installed the HSZ50, the documentation discussed modifying
>cam_data.c by copying the HSZ40 entry and renaming it HSZ50, and then
>using the "disk" type "HSZ50" when labelling a "disk" (unit) presented
>by the controller.
>>
>My question is: Are there any flag bits/what cam_data.c entry
>should be created, to tell the SCSI CAM driver that disks on a KZPSC
>are smarter than the default dumb disk, and which would therefore
>increase performance?
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 9286.1 | SMURF::KNIGHT | Fred Knight | Tue Mar 25 1997 15:44 | 18 | |
There is nothing in cam_data.c related to the adapter. http://www.zk3.dec.com/~knight/revs/ says about the RZ29B: RZ29B This device is fully supported in V3.2 or later. To use this device with V3.0/V3.0B the disktab entry must be changed. Therefore, this drive can not be an installation device when installing V3.0 or V3.0B. So, with V3.2G, there is NOTHING you need to do for the RZ29B. The reason for the HSZ50 note is because we don't have a process for adding support for non-existant H/W (the HSZ50 wasn't available until well after V3.2G shipped). Fred | |||||
| 9286.2 | netrix.lkg.dec.com::thomas | The Code Warrior | Tue Mar 25 1997 16:20 | 1 | |
Note that the KZPSC does not use SCSI CAM at all. | |||||
| 9286.3 | Thanks! | ORHVAX::HOLLY | Olin Holly @ALF, DTN 343-2737 | Wed Mar 26 1997 11:32 | 4 |
Thanks for the quick replies!
- Olin
| |||||