public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: Josie Adams <jadams@phytec.com>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: MPC555 BSP
Date: Mon, 09 Aug 2004 11:33:00 -0000	[thread overview]
Message-ID: <411760F0.8070006@eCosCentric.com> (raw)
In-Reply-To: <ENEALIHOMPJJMDOCOHJFIECFCDAA.jadams@phytec.com>

Josie Adams wrote:
> Hello,
> We have an eCOS BSP which supports the MPC555. We would like to contribute
> this BSP to eCOS.
> 
> Our phyCORE-MPC555 single board computer is based on the MPC555 embedded
> controller.
> http://www.phytec.com/sbc/32bit/pc555.htm
> 
> Please let me know what further steps we need to take to get our
> phyCORE-MPC555 in your list of supported hardware:
> http://ecos.sourceware.org/hardware.html

Hi Jodie,

It sounds great that you've got a port done. I assume you used the existing 
mpc5xx variant HAL as the basis?

As for adding to the hardware list, we only list targets there that are 
actually part of the main eCos distribution. So the best thing to do is 
integrate your port into the main eCos distribution. That way everyone can 
get the port more easily, and you have the advantage of it being more 
likely to be kept up-to-date and have fixes and improvements applied by users.

The process to do this is described here:
http://ecos.sourceware.org/patches.html
As you will read there, the first step will be getting a copyright 
assignment in place. Then we can actually look at the patch!

Thanks for contributing back!

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-08-09 11:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-03 15:58 Josie Adams
2004-08-09 11:33 ` 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=411760F0.8070006@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=jadams@phytec.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).