| 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 2025 | 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 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | RE: Using Asyn driver or modifying devLib (or related programs) of EPICSbase for any knid of cPCI cards |
| From: | "Jenny Chen" <[email protected]> |
| To: | <[email protected]>, <[email protected]> |
| Date: | Thu, 4 Oct 2007 10:47:48 +0800 |
|
Dear Mark, >- Using asyn driver.
You can use asyn to write your driver whether or not
it uses register access, calls to a >vendor library, or some other
mechanism. In this context asyn is just a
standardized interface between EPICS >device support and your driver.
This means that once you write an asyn driver you
should be able to use the >asyn device support for
standard records (ai, ao,
bi, bo, etc.), and you don't
need to write your own device >support. This is my problem I think. How to link one asyn driver for any card? Or one driver
for one card? Is there any example I can refer? Another question, Should
we have to install all drivers before startup EPICS at every boot (or EPICS
init function does that) (the linux version is later
then 2.6)? Jenny |