| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 47.1 | Ditto | BITBKT::FORBES | Bill Forbes - RTI BU | Mon Mar 30 1992 20:36 | 6 |
| I would really like to see this question answered, not only for 3rd party
drivers, but Digital-written drivers, as well. Basically, customers tend to
ask the simple question "What drivers are available?" It would be immensely
helpful if the (up-to-date) answer were available in this conference.
Bill
|
| 47.2 | driver = project | MLN08::CASTELLUCCI | EIS - Italy /DTN: *793-2292 | Tue Mar 31 1992 12:04 | 5 |
| The only KAV30 drivers I know are those developed
for internal projects.
I suggest to put here the list with a brief description
of the software/hardware functionality.
Aldo
|
| 47.3 | Driver for the PEP VDAD I/O board | EICMFG::BURKE | Jim Burke, @UFC | Tue Mar 31 1992 16:28 | 9 |
|
If this is any use to you, I wrote this driver as a template for the
KAV30 Toolkit. It is incomplete in that it does not drive the full
functionality of this board (eg. Dig-in's, Dig-out's, Anal-out).
It was written to access the analog sampling by polling and also by
interrupt, thus giving some useful performance figures.
The structure of this driver is the 'linkable module' type. That is;
the user application just links the driver modules with his own process.
|
| 47.4 | Driver for the Radstone SIO-4 | EICMFG::BURKE | Jim Burke, @UFC | Tue Mar 31 1992 16:40 | 12 |
|
The Radstone SIO-4 serial line multiplexor is a firmware and/or
downloadable 68020-based module, handling up to 16 lines.
In our current project, we are having special firmware developed
(specifically to handle DIN 19244 traffic) for this module.
We are currently developing a full-blown driver to interface with it.
This driver is the 'job' type. It exists as it's own job, and
I/O requests are made using ELN 'AREA' and 'CIRCUIT' objects.
Jim
|
| 47.5 | | HERR::CROSBIE | | Tue Mar 31 1992 17:46 | 14 |
|
Digital does not supply any supported VMEbus device drivers as part of the
VAXELN KAV TOOLKIT EXTENSIONS FOR VMS (KAV30 software) layered product.
The device driver examples shipped with the KAV30 software are intended
as templates for customers to use in the implementation of their own.
drivers
Drivers developed on a custom project basis, and by our partner
companies were going to be made available via the ASSETS program, I'm
not up-to-date as to how things are proceeding on this though.
Graham Crosbie
KAV30 Engineering Project Leader
|