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: | EPICS tech-talk <[email protected]> |
Date: | Wed, 24 Feb 2016 08:49:24 -1000 |
Hi Michael and Andrew,I will need compatibility with the Base-3.13.x. Seems the best outcome is a single common codebase. Michael, would that work for you?-MattOn Wed, Feb 24, 2016 at 7:47 AM, Andrew Johnson <[email protected]> wrote:Hi Michael,
On 02/23/2016 10:38 PM, Michael Davidsaver wrote:
> https://github.com/mdavidsaver/xycomioc
>
> Support for 220, 240, and 566 cards. Tested with RTEMS and vxWorks.
> Can't remember how feature complete. Other than checking that it builds
> just now, I haven't looked at it since 2010. This code holds some
> sentimental value to me as it's one of my first epics drivers, and the
> only one I found a good name for.
Nothing against your drivers, but Matt should understand that they were
not derived from the xycom drivers that were included with Base-3.13.x
and earlier. IIRC the original xycom digital drivers had a slightly
unexpected mapping between the signal address and I/O channels (S0 is
not port 0 bit 0). The xy240 driver also has a background thread that
emulates I/O Interrupt scanning.
I suspect Matt has existing applications that expect the original
capabilities, so compatibility may be important to him.
- 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