public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: "Balasubramaniam, Harish" <harish.balasubramaniam@intel.com>
To: "Jonathan Larmour" <jifl@eCosCentric.com>
Cc: <ecos-maintainers@ecos.sourceware.org>
Subject: RE: Ecos port to RVDS + new board port
Date: Mon, 13 Dec 2004 22:21:00 -0000	[thread overview]
Message-ID: <B8E391BBE9FE384DAA4C5C003888BE6F0108CE04@scsmsx401.amr.corp.intel.com> (raw)

Thanks for the link. Will get back to you on it.

 Yes that was a tricky one. We used a mix of manual (for OS) + automatic
(for applns) invoking of the constructors.

Rgds
Harish

-----Original Message-----
From: Jonathan Larmour [mailto:jifl@eCosCentric.com] 
Sent: Sunday, December 12, 2004 12:51 PM
To: Balasubramaniam, Harish
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: Ecos port to RVDS + new board port


Balasubramaniam, Harish wrote:
> Hi Ecos Owners,
>  
>  We have successfully ported Ecos source to use Arm compiler (instead
of
> gcc).

That sounds very interesting indeed. Lots of people have asked about
that, 
and we've usually considered it too difficult. How did you deal with 
constructor priority ordering? It'll certainly be an interesting set of 
changes!

>  We have also created a new HAL port for one of our upcoming chips
> (tested in both gcc & armcc).

Great.

>  We would like to know how to contribute these extensions to public
> domain.

We've got a write-up here, and it's probably not worth me repeating it
all:

http://ecos.sourceware.org/patches.html

But we should probably talk in more detail about the copyright 
assignment... we've talked to people in Intel before who have had some 
difficulty in persuading the Intel legal department to assign copyright.

I'd be interested to know if you have any perspective on this. There may
be 
other routes we can take to handle this which we don't normally take 
though, but we could make an exemption for a well-known reputable
company 
like Intel.

Jifl
-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot
experts
--["No sense being pessimistic, it wouldn't work anyway"]--
Opinions==mine

             reply	other threads:[~2004-12-13 22:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-13 22:21 Balasubramaniam, Harish [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-12-10 20:10 Balasubramaniam, Harish
2004-12-12 20:51 ` Jonathan Larmour

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=B8E391BBE9FE384DAA4C5C003888BE6F0108CE04@scsmsx401.amr.corp.intel.com \
    --to=harish.balasubramaniam@intel.com \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=jifl@eCosCentric.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).