> I am a little confused. Peter Kurpis tells me he has built
> 3.13.2 for Tornado II and your announcemnet was that 3.13.3
> was for support of Tornado II. Could clarify the differences
> please.
I intend to make three CA related changes in the
upcoming R3.13.3 release:
1) Change the names of fields in CA data structures that
collide with MACROS in the WRS SENS IP kernel.
2) Modify CA's auto configuration of its internal
search / beacon address list so that it works with the
backwards incompatible network interface query API present
in the WRS SENS IP kernel.
3) Fix a serious but infrequently occurring bug relevant
only to RISC based IOCs where a counter was incremented, but
was inadvertently protected by the wrong mutex semaphore.
CISC based computers (68k, 386, etc) do not experience this
bug because C's increment operator ends up producing a
single atomic instruction. A detailed description of this
bug was posted earlier on tech-talk.
Several sites have accomplished (1) above on their own, but
they will soon run into problems at run time with (2) which is more
difficult to fix since WRS does not document the API changes.
Frequently sites need Tornado II, and end up with SENS, because
they have a newer PPC RISC based CPU, and therefore
they will also need (3).
Jeff
> -----Original Message-----
> From: Leonard J. Reder [mailto:[email protected]]
> Sent: Thursday, June 15, 2000 10:10 AM
> To: Peter Kurpis
> Cc: [email protected]; [email protected]; EPICS
> Tech-Talk
> Subject: Re: Proposed R3.13.3
>
>
> Marty,
>
> I am a little confused. Peter Kurpis tells me he has built
> 3.13.2 for Tornado II and your announcemnet was that 3.13.3
> was for support of Tornado II. Could clarify the differences
> please.
>
> Thanks,
>
> Len
>
> Peter Kurpis wrote:
> >
> > No, I haven't. How would I go about doing this?
> >
> > (I just assumed that since the mods came from anl.gov,
> > that this was a sanctioned and tested thing, as if
> > I'd built an unmodified version from them. I was
> > mainly wondering aloud whether these were the only
> > changes to implement for Tornado II support, and
> > whether the proposed 3.13.3 only had these changes
> > regarding Tornado II, plus mainly unrelated addtions.)
> > >
> > > Peter Kurpis wrote:
> > > >
> > > > Len, just to make sure we are on the same page, I built 3.13.2
> > > > against Tornado II here for the interferometer project. EPICS
> > > > required a few changes to accomodate this, which I attach at
> > > > the end of this email FYC. (I wonder whether the proposed 3.13.3
> > > > includes anything essential beyon these patches.)
> > > >
> > > > >
> > > > > Marty Kraimer wrote:
> > > > > >
> > > > > > We are getting ready to generate a new 3.13 release of epics base.
> > > > > >
> > > > > > The main reason is to provide support for Tornado II.
> > > > > >
> > > > > > If Korhonen Timo and Eric Bjorklund have a new version of the support for the
> > > > > > aai and aao records, this is a good time to put it in base.
> > > > > >
> > > > > > Marty Kraimer
> > > > >
>
> --
> ____________________________________________________
> Leonard J. Reder
> Jet Propulsion Laboratory
> Interferometry Systems and Technology Section 383
> Email: [email protected]
> Phone (Voice): 818-354-3639
> ____________________________________________________
>
- References:
- Re: Proposed R3.13.3 Leonard J. Reder
- Navigate by Date:
- Prev:
Re: PID records [was Re: Proposed R3.13.3] Brian Bevins
- Next:
Re: mbbo record Leo Dalesio
- 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: Proposed R3.13.3 Leonard J. Reder
- Next:
Need driver for VIPC616 IP carrier board Vladis Korobov
- 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
|