Why not changeing the names ?
CONFIG_SITE: CROSS_COMPILER_TARGET_ARCHS=mv162 mv167
~~~~~~~~~~~
CONFIG_SITE: CROSS_COMPILER_TARGET_ARCHS=mv16x-lc mv16x
The confuesing is comeing of the target name, while
the target is mv167 - meaning a MC680X0 processor with FP
and the target mv162 - meaninig is a MC680X0 terget without FP.
but thera are a lot of mv162 boards with FP.
My suggestion changeing the target names, such as:
mv167 -> mv16x
mv162 -> mv16x-lc
>
>
> > 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
so this is not a bad ide, this is the only way yet (without modification
a lot in config files :) )
> > 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
I don't suggest this, while maybe you have mv162 boards with and without FP
in the same time :)
--
Regards
Gabor Csuka
DESY, Germany
- References:
- Re: mv162 only Pete Jemian
- Navigate by Date:
- Prev:
EPICS software distribution Bakul Banerjee
- Next:
Re: mv162 only Johnny Tang
- 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 Pete Jemian
- Next:
Re: mv162 only Johnny Tang
- 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
|