Experimental Physics and
Industrial Control System

Marty Kraimer <[email protected]> · Mon, 18 Dec 2000 14:53:55 -0600

Matthieu Bec wrote:
> 
> Dear all,
> 
> In the default config distributions, there are two distinct CONFIG_ARCH
> for the mv167 and the mv162.
> We have an application using both these targets and realized much code
> was probably compiled twice (starting wiht the EPICS core) when there
> was no need for it, the diffent flags beeing specifc to the 68040 CPU
> rather than the actual boards.
> 
> I had to build a whole system, and just realised how much time would be
> saved this way. the only issue being some ./bin/mv167 references in my
> mv162 startup script (or vice versa)..
> 
> My question is: would it make sense (and be safe) to declare a generic
> CONFIG_ARCH.68040 ? that would let me clean up the startup script issue.

Beginning with the 3.14 releases this is just what is done.

For 3.13 you can just build for one of the 68040 architectures and it should
work for any of the 68040/68060 architectures as long as they are compatible.

We build for mv167 and use it for our mv167, mv177, mv162, and mv172s. HOWEVER
we must build separately for some old mv162s that do not have a floating point
processor.

You must, of course, specify the correct board support package in the file
option of the boot parameters. Also do not mix tornado I and tornado II.

Marty

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System