public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Bart Veer <bartv@redhat.com>
To: tim@cygnetinc.com
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Port to MIPS II, IDT-79RC32334
Date: Wed, 11 Oct 2000 09:03:00 -0000	[thread overview]
Message-ID: <200010111602.e9BG2Fa30847@sheesh.cygnus> (raw)
In-Reply-To: <002901c032bb$fc04f3b0$1a01010a@cygnetinc.com>

>>>>> "Tim" == Tim Michals <tim@cygnetinc.com> writes:

    Tim> Bart,
    Tim> I have a MIPS gcc compiler from a "company" which supports
    Tim> the IDT part. I will do some research to see if they modified
    Tim> the compiler and associated tools.

I would recommend also checking the vintage of that compiler and
linker. If it is based on sources prior to gcc 2.95.2 or binutils 2.10
it might lack features such as constructor priority ordering or
selective linking.

    Tim> Thanks for the input on the BSP. The "company" has a BSP
    Tim> already, so I was going to move some parts to eCOS as
    Tim> necessary.

Existing working code is always a big help, especially because it
implies that the hardware actually works. There is one possible issue:
if you are thinking about contributing back some of your work and you
incorporate bits of that existing BSP, there could be copyright and/or
licensing problems. Just something to keep in mind.

Bart Veer // eCos net maintainer

      reply	other threads:[~2000-10-11  9:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-03 12:27 Tim Michals
2000-10-08  9:43 ` Bart Veer
2000-10-10  6:09   ` Tim Michals
2000-10-11  9:03     ` 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=200010111602.e9BG2Fa30847@sheesh.cygnus \
    --to=bartv@redhat.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=tim@cygnetinc.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).