From: IJSAPL::KUPPENS "Do I have a complete working knowledge of virtually everything ?....." 8-SEP-1996 12:50:06.09 To: STAR::EVERHART CC: KUPPENS Subj: U: SCSI Philips Medical SEPT 3 1996 minutes and actions Glenn, Question from Philips: "Is it possible to make a user-callable call which does a SCSI-RESET ?", as they have major problems in the hospitals when they sometimes need a SCSI-RESET and now can only do a SCSI-RESET by a total system reboot, which takes *too* long.... Please advise?, ThanXs!, Robbert. To all, Minutes and actionlist of the conference call of Tuesday September 3 at Nashua: 9.00 am Moscow: 5.00 pm Netherlands: 3.00 pm AGENDA: ======= - Introduced involved people and responsiblities Johan van Oosterhout (Philips) software specialist Lex van Gijssel (Philips) project leader Wim Mosterman (Philips) software specialist Glenn Everhart (Digital Nashua) SCSI architect OpenVMS Sergei Osipov (Digital Moscow) project manager Igor Abramov (Digital Moscow) software specialist Vadim Model (Digital Moscow) software specialist Gleb Rajko (Digital Moscow) software specialist Jur van den Burg (Digital Utrecht) MCS software specialist Arie de Groot (Digital Utrecht) account manager (not present at conf. call.) SCSI DRIVER(s): --------------- SCSI driver to support host/target functionality: - Understanding requirements Philips Medical SCSI driver Digital MSC (Moscow Software Center) people understand the current requirement but requested missing hardware spec + required hardware components. - Understanding re-using existing SCSI driver (Glenn) Glenn Everhart is available for questions regarding the re-use of existing SCSI drivers, Glenn will mail the sources to Moscow. - Understanding timeline/milestones of delivery It is understood by all parties that latest delivery of operational drivers must be no later than November 29, 1996. Digital MSC has made a preliminary qualification and has proposed to deliver the OpenVMS driver in 2 months. Windows NT drivers development is under investigation but depends on availability of Windows NT SCSI sources. Costs for development have been qualified and has been communicated to Philips Medical. Final agreement how costs will be X-charged is to be finalized latest september 27, 1996. Michel van der Togt (manager OEM group Digital) has agreed with Robert Boers (manager Digital MSC) that development of the drivers can start directly (as costs will be pre-paid by Digital Netherlands). - Understanding communication/support channels Communication will take place through Email and telephone, below you will find all information: DIGITAL: ======== Digital MSC office post address is: Digital Equipment Corporation 129223 Russia Moscow Prospect Mira AO VVC Business Center JV "Technopark" Building 6 Attn. Sergei Osipov The preferred e-mail/tel/fax coordinates of Digital MSC persons are the following: Igor (CECMOW::) Abramov abramov@cecmow.enet.dec.com Gleb (CECMOW::) Rajko rajko@cecmow.enet.dec.com Vadim (CECMOW::) Model model@cecmow.enet.dec.com Sergei (MSCDEV::) Osipov osipov@cecmow.enet.dec.com tel. +7 502 223 2601/2602 +7 095 974 7610/7612 fax +7 502 223 2600 +7 095 188 4557 DTN 892 2601 Glenn C. (STAR::) Everhart everhart@star.enet.dec.com tel. +1 603 881 1497 Jur van den Burg vdburg@utrtsc.enet.dec.com tel. +31 30 2833973 Arie de Groot groot_ar@utrop1.enet.dec.com tel. +31 30 2833166 fax. +31 30 2832161 PHILIPS MEDICAL SYSTEMS MR DIVISION: ==================================== Postaddress: Philips Medical Systems MR Attent. of Lex van Gijsel Veenpluis 2-10 Best The Netherlands telephone fax Johan van Oosterhout +31-40-2762203 +31-40-2765644 ohout@best.ms.philips.com Wim Mosterman +31-40-2763407 +31-40-2765644 mosterman@best.ms.philips.com Lex van Gijsel +31-40-2763583 +31-40-2765644 avgijsel@best.ms.philips.com - Understanding how to deliver driver to comply with requirements and how to be included in OpenVMS codestream V7.? Glenn Everhart will email SCSI sourcecode and together with Jur van der Burg (debugging/testing support max. 1 day/week) will ensure that driver(s) to be delivered will be qualified for inclusion in OpenVMS codestream. - Understanding testing and qualification delivery procedure Philips Medical MR will send all hardware and available tools and documentation and will document latest September 27, 1996 how drivers will be tested and how acceptance-tests will be undertaken. Philips Medical must at least send the following to Digital MSC latest September 9, 1996: - 2x PCI-ARI board - source code initial test program ARI - Hardware specification(s) - 2x KZPSA PCI-SCSI board - Plan follow-on meeting(s), Email/telephone See also above for Email and telephone interfaces. Direct communication will take place between Digital MSC and Philips Medical, as soon as Digital MSC has preliminary working drivers Jur van der Burg must be notified to be able to test and debug the driver(s) together with Philips Medical (Johan van Oosterhout). ARI DRIVER(s): -------------- ARI driver to support PCI-ARI board as developed by Philips Medical: - Understanding requirements Philips Medical ARI driver Digital MSC (Moscow Software Center) people understand the current requirements. - Understanding re-using existing PCI driver Glenn Everhart will ask VMS engineers which existing OpenVMS PCI drivers already do PCI-DMA (as example driver), possible PCI-FDDI driver (DEFPA?) - Understanding timeline/milestones of delivery It is understood by all parties that latest delivery of operational drivers must be no later than November 29, 1996. Digital MSC has made a preliminary qualification and has proposed to deliver the OpenVMS driver in 2 months. Windows NT drivers development is under investigation but depends on availability of Windows NT sources. Costs for development have been qualified and has been communicated to Philips Medical. Final agreement how costs will be X-charged is to be finalized latest september 27, 1996. Michel van der Togt (manager OEM group Digital) has agreed with Robert Boers (manager Digital MSC) that development of the drivers can start directly (as costs will be pre-paid by Digital Netherlands). - Understanding communication/support channels See above. - Understanding how to deliver driver to comply with requirements and how to be delivered to Philips Medical for their own support? - Understanding testing and qualification delivery procedure Philips Medical MR will send all hardware and available tools and documentation and will document latest September 27, 1996 how drivers will be tested and how acceptance-tests will be undertaken. Philips Medical must at least send the following to Digital MSC latest September 9, 1996: - 2x PCI-ARI board - source code initial test program ARI - Hardware specification(s) - 2x KZPSA PCI-SCSI board - Plan follow-on meeting(s), Email/telephone See also above for Email and telephone interfaces. Direct communication will take place between Digital MSC and Philips Medical. Questions and remarks for Digital MSC people (from Philips): - Drivers must be VMS and WNT release independent - Drivers must be platform independent - Drivers must be PCI compliant 1. It is not clear to me which SCSI-drivers will be changed in order to get target functionality. At this moment we are using the GKdriver (class-driver) and the PKSdriver (portdriver for KZPSA) Will both drivers be changed? It must be possible to talk to the BDAS (data-acquisition system) via the SCSI interface the way we do it now. Will this be possible after the changes? 2. There is an error in Req. Spec SCSI-driver (XJS-155-4626). In section 4, it says: 'It must be possible to define the Host as SCSI-initiator ... ..... As such, a function should be available to define initiator or target behaviour on a SCSI channel basis.' This should NOT be on channel basis but on SCSI-ID basis. In other words, a SCSI-device (represented by its SCSI-ID) must be defined as initiator or target. All SCSI-channels representing this device should have target or initiator behaviour. The problem however is that for the QIO function a 'channel' is defined as the combination of a SCSI-ID and a SCSI-LUN. With the 'open' function defined in XJS-155-4626 it is, in theory, possible to define 'target' for channel 600 and initiator for channel 601. I suggest to add a function that defines target or initiator on a SCSI_ID basis and to leave-out the 'open_flag' parameter in the open function. If this can be agreed, I will update XJS-155-4626. Johan van Oosterhout. Thanks and regards, Arie and Robbert.