From: Bart Veer <bartv@cygnus.co.uk>
To: mpokorny@glatmos.com
Cc: ecos-discuss@cygnus.com
Subject: [ECOS] Re: TMS320C6x port
Date: Thu, 10 Dec 1998 10:26:00 -0000 [thread overview]
Message-ID: <199812101826.SAA15793@sheesh.cygnus.co.uk> (raw)
In-Reply-To: < 3.0.5.32.19981201092020.008f7df0@xena > (mpokorny@glatmos.com)
>>>>> "Martin" == Martin P Pokorny <mpokorny@glatmos.com> writes:
Martin> Hi, I was wondering if anyone has done any work to port
Martin> eCos to the TI TMS320C6x family of DSP's. Are there any
Martin> opinions on whether this would be a good idea, or whether
Martin> it's even possible? I am new to eCos, but I'm interested
Martin> in looking into this possibility.
I am afraid that this is likely to prove difficult. To the best of my
knowledge there is no port of gcc and g++ to the 320C6x family, and
eCos relies on features provided by these compilers.
Bart Veer // eCos net maintainer
prev parent reply other threads:[~1998-12-10 10:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-01 8:18 [ECOS] " Martin P. Pokorny
[not found] ` < 3.0.5.32.19981201092020.008f7df0@xena >
1998-12-10 10:26 ` Bart Veer [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=199812101826.SAA15793@sheesh.cygnus.co.uk \
--to=bartv@cygnus.co.uk \
--cc=ecos-discuss@cygnus.com \
--cc=mpokorny@glatmos.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).