1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 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 2007 2008 2009 2010 2011 2012 2013 2014 2015 <2016> 2017 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: OSI Compliant VME Support |
From: | Matt Rippa <[email protected]> |
To: | Andrew Johnson <[email protected]> |
Cc: | Talk EPICS Tech <[email protected]> |
Date: | Tue, 23 Feb 2016 13:01:49 -1000 |
Thanks for this, Andrew. Starting the XYCOM modules from a common base git hub sounds perfect to me.
Matt
Hi Matt,
On 02/23/2016 04:28 PM, Matt Rippa wrote:
> * GreenSprings TIP810
> * VIP610 (Industry Pack)
These two have already been converted and are available in my regular
IPAC module, see https://svn.aps.anl.gov/trac/epics/ipac for details.
The APS still uses the XYCOM 240 and 566 modules (see
http://www.aps.anl.gov/epics/modules/digital/xycom/index.html and
http://www.aps.anl.gov/epics/modules/analog/xycom/index.html ) but while
they were converted to the 3.14 build system a long time ago we have
never tried to make them OSI-compliant.
I would be happy to convert the CVS history of the two XYCOM modules to
git and create github projects for them if you want to start from the
"official" unbundled versions and maintain them there.
- Andrew
--
There are only two hard problems in distributed systems:
2. Exactly-once delivery
1. Guaranteed order of messages
2. Exactly-once delivery
-- Mathias Verraes