This is the mail archive of the
mailing list for the eCos project.
Re: MIPS variant specific stuff in arch.inc?
"Andy Dyer" <email@example.com> writes:
> 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.
The idea was that the R3900 option would transform eventually into
general R3000 support. While that hasn't happened, there are still
some R3000 based devices out there, so the option is still useful.
MIPS32/64 are architecture sub-variants developed by MIPS for embedded
> 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.
I guess, as it has turned out, the two examples of this could probably
be pushed out as you suggest. However, as examples of a design
principle that we would like to preserve, they probably ought to stay
where they are. If that makes sense.
Nick Garnett eCos Kernel Architect
http://www.ecoscentric.com The eCos and RedBoot experts
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss