On Wed, 2007-04-11 at 14:19 +0200, Ralph Lange wrote:
> 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.
Cool. We would be interested in having a look at what you've done
there.
-- Ernest
>
> Ralph
>
- 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.
- Re: EPICS R3.14.9 and vxWorks Ralph Lange
- Navigate by Date:
- Prev:
Re: EPICS R3.14.9 and vxWorks Ernest L. Williams Jr.
- Next:
[Fwd: Track on control system evolution] News from EPICS - proposed topics Matthias Clausen
- 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 Ralph Lange
- 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
|