From: "Jurica Baricevic" <jura@INTESIS.hr>
To: "Xavier Wang" <xavierwang@ms19.url.com.tw>
Cc: "Ecos" <ecos-discuss@sourceware.cygnus.com>
Subject: RE: [ECOS] LX4180
Date: Fri, 27 Oct 2000 06:36:00 -0000 [thread overview]
Message-ID: <001e01c0401a$9c5be790$6b00a8c0@JURA> (raw)
In-Reply-To: <002401c04008$ca234900$c12314ac@realtek.com.tw>
Xavier wrote:
> I tried to build eCos for Lexra LX4180 which is a MIPS
> R3000-like CPU. It seems to be a good start from building
> GNU toolchains and eCos for Toshiba TX39. But I found
> that TX39 seems to have instructions that are not in the
> standard ISA I instruction set, such as Branch Likely and
> ISA III cache instructions. So, is it possible to configure
> GCC to generate only standard ISA I instructions?
Probably the best solution would be to configure GCC to support your
specific processor architecture by default (i.e. I am using
'mipsel-r3041-elf-gcc'). There is also possibility to build GCC for any MIPS
ISA architecture ('mips-any-elf-gcc'). In that case, you should provide GCC
with some specific options (egg '-mcpu=r3000'), when building eCos.
Anyway, since you have intention to run eCos on a R3000 MIPS, you may have
some problems with a 'load delay slot'. Please, check the ecos-discuss
mailing list archive:
http://sources.redhat.com/ml/ecos-discuss/2000-06/msg00003.html
http://sources.redhat.com/ml/ecos-discuss/2000-06/msg00014.html
http://sources.redhat.com/ml/ecos-discuss/2000-06/msg00024.html
Regards,
Jura
prev parent reply other threads:[~2000-10-27 6:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-27 5:54 Xavier Wang
2000-10-27 6:36 ` Jurica Baricevic [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001e01c0401a$9c5be790$6b00a8c0@JURA' \
--to=jura@intesis.hr \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=xavierwang@ms19.url.com.tw \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).