EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: IPac driver organisation
From: "Denison, PN \(Peter\)" <[email protected]>
To: "Andrew Johnson" <[email protected]>, "Doug Murray" <[email protected]>, "Foster, AJ \(Andrew\)" <[email protected]>
Cc: TechTalk EPICS <[email protected]>
Date: Wed, 18 Jul 2007 11:17:31 +0100
> From: Andrew Johnson
> 
> Hi Doug,
> 
> Doug Murray wrote:
> > Hi Andrew, I've noticed the IPac directory contains support for a 
> > number of carrier cards.  Would it be possible to add drivers for:
> > xycom9660
> > acromag9670
> > hytec8002
> > 
> > We use these at SLAC, and we're using RTEMS so we've had to OSI-ify
> > these packages.
> 
> Andy Foster wrote the Xycom/Acromag carrier driver which is licensed 
> like the rest of Ipac under the LGPL (currently V2.1; I may 
> move Ipac to V3 before the next release).  If Andy is happy for it to
> be included I'm willing to add it (with a few minor changes) to the
> Ipac distribution. The next release of Ipac already uses the OSI
> interfaces for everything except the tyGSOctal driver and ATC-40
> carrier driver, so I'd want an OSIfied version rather than the vxWorks
> only code that is in his xycomIpac-1.0 release.  If you have an
> OSIfied version, please send me a copy.
> 
> The Hytec driver is Copyright Hytec, and the source code we have here 
> does not mention any licensing terms at all, so I can't distribute it 
> anyway.  I would not be willing to maintain this code at present,
> which also provides some VME64X hot swap capabilities that I do not 
> claim to comprehend.

I would like to see the Hy8002 (and Hy8001) drivers making it into the
main ipac distribution. The issue of hotswap should be peripheral (in
that you don't need the support to make it work), but I grant that it
does confuse the current code. I will pursue the issue of licencing at
this end and try to arrive at code that you are happy with. It should
be in everyone's interests (including Hytec) to have the code in the
main distribution.

> IP module drivers should be released either individually or in small 
> groups of related drivers, making it as easy to put together the 
> software for an IP-based IOC as it is for the hardware.

Here, here.

-- 
Peter Denison, Senior Software Engineer
Diamond Light Source Ltd., Diamond House, Harwell Science and Innovation
Campus
Didcot, Oxon, OX11 0DE
Tel: +44 1235 778511
(apologies in advance for the lines below. I have no control over it)
<DIV><FONT size="1" color="gray">This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. 
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
</FONT></DIV> 


Replies:
RE: IPac driver organisation Andy Foster
References:
Re: IPac driver organisation Andrew Johnson

Navigate by Date:
Prev: RE: ai, soft channel, and breakpoint table Allison, Stephanie
Next: Re: ai, soft channel, and breakpoint table Martin L. Smith
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: IPac driver organisation Andrew Johnson
Next: RE: IPac driver organisation Andy Foster
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Nov 2011 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·