EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  <19971998  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  <19971998  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: Re: VxWorksp2 is ready now!
From: [email protected] (Tim Mooney)
To: [email protected]
Date: Fri, 15 Aug 1997 11:02:50 -0500
Dear Stumbling,

> > >I think the problems with vxV52p2.Tar.gz file is fixed now. Please
> > >download it if you are thinking about moving to EPICS Release R3.13.7
> > >and above.
> 
> I certainly hope you meant EPICS Release R3.13.0BETA7.  If not, my two
> 					       ^^^^^
> weeks of vacation must have been a whole lot longer than two weeks for
> the rest of universe, given the rate at which real (non-BETA) releases
> of EPICS happen.

Hey, you snooze, you lose.

> > >	       Please note that this is NOT a replcement of your full
> > >VxWorks distribution package.
>  
> > Admittedly, I am confused as ever.
> 
> Me too.  It's not clear to me what "vxV52p2.Tar.gz" fixes.  We "own" our own
> license from WRS, so it sounds like we need to apply this patch, if we can
> get it.  (Somebody else on our site knows the password.)  Can someone give
> me a clue as to what the patch fixes and what will break without the patch?
> 
> -bill (Organizationally Challenged, but stumbling on!)

The most recent fix adjusts the highest local memory address that gets
mapped to VME (for MVME162 processors only) and allows an MVME162 to
run EPICS and Hideos IndustryPack support.  (I.e., it allows you to
put IP modules on the main processor instead of, or in addition to,
IP modules on a separate MVME62 running only hideos.)

Earlier patches fixed the way cacheing was done so that two processors
could use semaphores across the VME backplane (the semaphore can't do
any good if it's cached in local memory), and allow a single vxWorks
image to handle boards with differing amounts of memory.

By the way, I don't actually know anything about this stuff.  I'm just
repeating what I've heard John Winans, Jim Kowalkowski, and Joe Sullivan
talking about.

Tim Mooney

Navigate by Date:
Prev: Re: VxWorksp2 is ready now! Bill Brown
Next: Re: VxWorksp2 is ready now! Bakul Banerjee
Index: 1994  1995  1996  <19971998  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: VxWorksp2 is ready now! Bakul Banerjee
Next: CA Server and CA Gateway Hammonds, John
Index: 1994  1995  1996  <19971998  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 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·