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 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: | IPac driver organisation |
| From: | Doug Murray <[email protected]> |
| To: | Andrew Johnson <[email protected]> |
| Cc: | TechTalk EPICS <[email protected]> |
| Date: | Tue, 17 Jul 2007 11:15:17 -0700 |
xycom9660
acromag9670
hytec8002
We use these at SLAC, and we’re using RTEMS so we’ve had to OSI-ify these packages.
Also, I see drivers for a few IP cards in that directory, such as CANbus and an Octal UART card. Is the idea that new IP drivers be placed in this directory as well?
On a related note, the GPIB IP card (IP488) is located in the Asyn directory. Should IP modules be put under Asyn?
Regards
-doug
- Replies:
- Re: IPac driver organisation Andrew Johnson
- Navigate by Date:
- Prev: RE: RE: Asyn 4.8 compile error with Linux GPIB Mark Rivers
- Next: Re: Asyn 4.8 compile error with Linux GPIB Janet Anderson
- 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: MEDM enum not displaying correctly? Benjamin Franksen
- Next: Re: IPac driver organisation Andrew Johnson
- 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
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·