Thompson, David H. wrote:
An alternative is to load a kernel specific epics support module post-boot and before any epics modules are loaded. That may be the best of all worlds, and we could share those between the labs.
Been there. Done that.
We are using a support module (bspDep), which contains the system part
of our library for usecond resolution timers and some other useful bsp
dependent stuff. Even though we don't use different vxWorks versions,
bspDep now contains many of the #ifdefs in one place that used to be
spread over our other support modules' code.
We use it for mv162 and mv2100.
Ralph
- Replies:
- Re: EPICS R3.14.9 and vxWorks Ernest L. Williams Jr.
- References:
- EPICS R3.14.9 and vxWorks Ernest L. Williams Jr.
- Re: EPICS R3.14.9 and vxWorks Andrew Johnson
- Re: EPICS R3.14.9 and vxWorks Ernest L. Williams Jr.
- Re: EPICS R3.14.9 and vxWorks Andrew Johnson
- Re: EPICS R3.14.9 and vxWorks Ernest L. Williams Jr.
- Re: EPICS R3.14.9 and vxWorks Andrew Johnson
- RE: EPICS R3.14.9 and vxWorks Thompson, David H.
- Navigate by Date:
- Prev:
RE: EPICS R3.14.9 and vxWorks Thompson, David H.
- Next:
Re: EPICS R3.14.9 and vxWorks Ernest L. Williams Jr.
- Index:
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 R3.14.9 and vxWorks Thompson, David H.
- Next:
Re: EPICS R3.14.9 and vxWorks Ernest L. Williams Jr.
- Index:
2002
2003
2004
2005
2006
<2007>
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|