[ECOS] MIPS variant specific stuff in arch.inc?

[Andy Dyer]

> -----Original Message-----
> From: nickg@miso.calivar.com 
> [mailto:nickg@miso.calivar.com]On Behalf Of
> Nick Garnett
> Sent: Monday, February 16, 2004 11:43 AM
> To: Andy Dyer
> Cc: ecos-discuss@ecos.sourceware.org
> Subject: Re: [ECOS] MIPS variant specific stuff in arch.inc?
> 
> 
> "Andy Dyer" <adyer@righthandtech.com> writes:
> 
> > Is there a reason why there's so much variant specific stuff
> > in the hal/mips/arch/current/include/arch.inc?  There are a
> > bunch of #ifdef CYG_HAL_MIPS_R3900 and one or two #ifdef 
> CYG_HAL_MIPS32
> > statements in there.
> 
> These select different sub-variations of the basic MIPS
> architecture. These are things that would be common to many different
> implementations. Thus it makes sense to place them in the architecture
> and have them enabled from the variant if necessary.
> 

I guess the terminology fooled me - R3900 was really only ever used by
Toshiba
for their stuff, most everybody else used "R3000" for the family, and
MIPS32
I thought referred to the specific MIPS32 core that MIPS inc. offers.

> > 
> > I don't have any systems with those cpus, so if I made a patch
> > I have no way to test it.
> 
> What do you want to change?
> 

I was offering to push the R3900 stuff into
mips/tx39/current/variant.inc and the
MIPS32 into mips/mips32/current/variant.inc, but it sounds like you
don't want it
there, so never mind.

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss