Hi everyone,
We would like to go down a path of standardizing new EPICS drivers that we develop here at SLAC.
Can folks speak about pros/cons for using devlib2-based approach versus an asyn-based approach for access
to (1) PCI bus access, VME64x CSR/CSR, and other memory-mapped devices; (2) ethernet/RS232 based; stream-based ?
Here at SLAC we have a module that Till wrote which addresses:
(1) memory and I/O barriers, (2) endianess
Is this something that belongs in or is now in EPICS BASE?
Cheers,
Ernest
- Replies:
- RE: devlib2 and asyn Pros/Cons Mark Rivers
- Navigate by Date:
- Prev:
EPICS Alarm system via web browser Jiro Fujita
- Next:
RE: EPICS Alarm system via web browser Bertrand Alain Gregor (PSI)
- 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
- Navigate by Thread:
- Prev:
Re: EPICS Alarm system via web browser Kasemir, Kay
- Next:
RE: devlib2 and asyn Pros/Cons Mark Rivers
- 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
|