drvIpac testers wanted

[Andrew Johnson <anj@aps.anl.gov>]

I've been working on a new release of drvIpac, converting it and the 
drvTip810 CANbus driver (but not tyGSOctal) to use EPICS OSI and devLib 
calls instead of the native vxWorks APIs.  However I don't have access 
to the hardware to test all the converted code, and I'd like to have 
some confidence that I didn't break anything before I put out a numbered 
release.  I would be particularly interested to hear from anyone who 
tries the drivers out on RTEMS (or even Linux if you have a fully 
implemented version of devLib - I'm not sure if the Australian Light 
Source's plug-in supports interrupts, which the Tip810 driver needs, but 
the VIPC and TEWS IPAC carrier drivers should still work).

The converted code can be found in the CVS Snapshot for drvIpac at 
http://www.aps.anl.gov/epics/download/modules/ipac_cvs.tar.gz

This release *should* be source-level compatible with drvIpac carrier 
and module drivers that are maintained externally, but I have made 
changes to the type-names used in the drvIpac APIs so it would also be 
good to hear from authors of such code about anything that I broke.


My thanks to the people who have sent me partial conversions of drvIpac 
in the past, which I used as a starting point.  My version goes beyond 
all of those submissions however, and the code now compiles without 
errors or warnings on all the EPICS platforms I've tried building it on 
(yes, I even cleaned up the pesky 'strict-aliasing rules' warnings from 
GCC 4.x).  Not that that I'm aware of anyone who actually has a devLib 
plug-in for Solaris or Darwin, but if you do...

Thanks in advance,

- Andrew
--
The right to be heard does not automatically include
the right to be taken seriously. -- Hubert H. Humphrey