From: Jonathan Larmour <jifl@eCosCentric.com>
To: Kiran Raj <Kiran.Raj@esk.fhg.de>
Cc: ecos-maintainers@sources.redhat.com
Subject: Re: Request to give information.
Date: Mon, 17 Mar 2003 12:26:00 -0000 [thread overview]
Message-ID: <3E75BEB1.4060505@eCosCentric.com> (raw)
In-Reply-To: <3E705C1E.2020305@esk.fhg.de>
Kiran Raj wrote:
> hello sir ,
> i am doing a research project which involves the integration of the
> Micro blaze .so can the ECOS support the Microblaze integration.
> i would be happy if u reply me as soon as possible.
As you probably already know, there's no current port to the MicroBlaze.
But I don't see any problem that would prevent you doing a port.
I see from
http://www.xilinx.com/support/training/abstracts/atp-mb.htm that there's a
GCC port to the MicroBlaze, so that shouldn't be an issue.
So it sounds like you could go ahead with a port.
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine
prev parent reply other threads:[~2003-03-17 12:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 10:23 Kiran Raj
2003-03-17 12:26 ` Jonathan Larmour [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=3E75BEB1.4060505@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=Kiran.Raj@esk.fhg.de \
--cc=ecos-maintainers@sources.redhat.com \
/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).