> We have some applications which run mv162s using the EPICS/VxWorks mv167
> release. Does anyone know any reason why this is a bad idea? Obviously
> it works, but are there any functionality differences?
>
This is what I've been doing for some time. That is, build for the
mv167 and run it on the mv162. No problems.
Since I just installed a new system from scratch last week,
I thought I'd find out what's the correct way to support the mv162.
Consensus is, if the mv162 is not a mv162lc, then
[1] build for the mv167 and run it on the mv162
[2] edit config/CONFIG_ARCHS.mv162 and change the line
ARCH_DEP_CFLAGS=-DCPU=MC68040 -msoft-float -DCPU_FAMILY=MC680X0
to
ARCH_DEP_CFLAGS=-DCPU=MC68040 -DCPU_FAMILY=MC680X0
Pete
- Replies:
- Re: mv162 only Gabor Csuka
- Navigate by Date:
- Prev:
Re: EPICS on Baja. watson
- Next:
EPICS software distribution Bakul Banerjee
- 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: mv162 only Bret Goodrich
- Next:
Re: mv162 only Gabor Csuka
- 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
|