EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  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  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Vme support in devLib for Linux
From: Jane Richards <[email protected]>
To: Andrew Johnson <[email protected]>
Cc: tech-talk <[email protected]>
Date: Wed, 19 Feb 2014 11:37:05 -0800
Hi Andrew,

WRT the devLib issue, Graham Waters just applied your suggestions to his code for the Tundra Universe chip (devLibUniverse.c) and got an error free compilation for EPICS R3.14.12.2. Replacing reference to structure devLibVirtualOS with devLibVME and header file devLib.h with devLibVME.h was all that was needed.

  Thanks!

  We are pursuing the devLib2 questions with other tech-talk responders.

Jane and Graham


On 02/17/2014 08:43 AM, Andrew Johnson wrote:
Hi Jane,

On 02/14/2014 05:55 PM, Jane Richards wrote:
We use a linux VME kernel driver and API from GE-Fanuc. We have created
a "software shim" that recreates the VxWorks API in terms of the Linux
driver. This was developed using EPICS release 3.14.8.2 and has worked
well up to and including 3.14.11. However release 3.14.12 introduced a
"devLib
cleanup" which changed the API and broke our code.  We now want to
update our code to a sustainable model.

How should we proceed?
Hopefully the changes we made should not require too much in the way of
modifications to your implementation. The Release Notes entry explains
most of the changes, and my guess is that you may only have to include
the new devLibVMEImpl.h header to be able to compile against 3.14.12.
There are other changes which may be worth doing, renaming your virtual
OS table from pdevLibVirtualOS to pdevLibVME for example, but there is a
macro defined in the new Impl.h file which does that for you.

BTW We require devlib2 for building support for the MRF event
generator/receiver which will also run on Linux. How does devlib V1
relate to the additional functions defined in devlib2?
The best person to answer that question is Michael Davidsaver, who is
responsible for both implementations and can also comment on future
plans. He has been busy recently with the NSLS-2 work ramping up though,
so I don't know how soon or how extensively he'll be able to respond.

HTH,

- Andrew


--
Jane Richards
Controls Group Leader, TRIUMF
4004 Wesbrook Mall, Vancouver, BC V6T 2A3
Phone: (604) 222-1047 (ext 7693)
Fax: (604) 222-1074


References:
Vme support in devLib for Linux Jane Richards
Re: Vme support in devLib for Linux Andrew Johnson

Navigate by Date:
Prev: Installing EPICS on the Raspberry Pi Pete Jemian
Next: ImageJ Plugin not working with Area Detector Yoram Fisher
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Vme support in devLib for Linux Michael Davidsaver
Next: Re: Vme support in devLib for Linux Dirk Zimoch
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 17 Dec 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·