| Title: | VAX on VMEbus: KAV30 |
| Notice: | Could have been as fast as 68K but its a VAX! |
| Moderator: | CSSVMS::KAV30_SUPP |
| Created: | Thu Apr 18 1991 |
| Last Modified: | Fri Aug 02 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 159 |
| Total number of notes: | 645 |
Hello, I have some questions to the KAV30. Background: We have a customer, who worked up till now, with the VME-Bus and with components from MOTOROLA. He had a complete development- system directly an the VME-BUS, and he had the operating-System VERSADOS from Motorola. Mow: the customer reflects to take VAX-ELN AND A KAV30, to have a better connection to the DEC-World. But he wants to take also in future f. ex the following Board: MVME332 Intelligentz Communication Controller. For this board he had (under VERSADOS) a driver, he told us, that the calls via this driver were simular our QIO-Calls in our world. He now wants from us a simular Interface to his MOTOROLA-HW, like he had befor. My knowledge from KAV30 and/or VAXELN ist in the moment not so deep, that J could estimate, how long ist would take to write such a driver. He gave me the Manual from the MVME332-Controller to read and waits now for my answer...... Has anyboy experience in this field, specially that question: how can I devide a Programm for the KAV30 in a "normal user-written part" and a "driver-code-part" Any commentaries welcome! Bernhard Jooss
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 45.1 | HERR::CROSBIE | Tue Feb 11 1992 15:35 | 26 | ||
Hi Bernhard,
Under VAXELN there is not a lot of difference between a normal user
application and a device driver, both are written in one of the
supported high level languages (C, FORTRAN, ADA, VAXELN PASCAL). There
are a couple of approaches to writing device drivers under VAXELN.
One approach is to implement the "driver" as a number of subroutines
that manipulate the device your are controlling, which you call
directly from the application program that uses the device. This
approach has a disadvantage in that there can only be one "user" of the
device. The other approach is to implement the driver as a standalone
program that has some form of user-interface (usually message passing),
the user application(s) then send messages to the driver program
requesting it to do some work on behalf of the user program. The first
approach I mentioned is probably the closest to "QIOs".
VAXELN is a very different environment from VMS and VERSAdos, I would
strongly recommend that you try to find somebody familiar with VAXELN
to advise you in how to design and implement a VAXELN device driver.
The EIC here in Munich may be able to help in providing a resource to
assist you and your customer.
I hope the above information is of some use to you.
Graham
| |||||
| 45.2 | how long ?? | NBOIS::JOOSS | Tue Feb 11 1992 17:27 | 8 | |
>> The other approach is to implement the driver as a standalone
program
Ok, that's exactly the way, that we should go... But now once more the
question: How long will "a knowledgel person" need time, to write that
"stand-alone-program" , if he/she has the SW/HW-description (about 100
pages) of the MVME332 ????
Bernhard
| |||||
| 45.3 | HERR::CROSBIE | Wed Feb 12 1992 10:23 | 6 | ||
Hi Bernhard,
This is just a guess, it could take anywhere between 4 to 8 weeks
to design, implement and test the driver.
Graham
| |||||
| 45.4 | thank you | NBOIS::JOOSS | Wed Feb 12 1992 14:16 | 9 | |
>> This is just a guess, it could take anywhere between 4 to 8 weeks
to design, implement and test the driver.
Ok, that was also my "personal feeling". Now our "responsibles"
have to decide, what we shall do....
Thank you for your help
Bernhard Jooss
| |||||