public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Piotr Skrzypek <peter@skrzypek.eu>
To: ecos-devel@ecos.sourceware.org
Subject: OpenRISC port
Date: Wed, 23 Jan 2013 09:36:00 -0000	[thread overview]
Message-ID: <CAAOJC6oe9BaVgu8y6O9e0m1=_DuLbFOtQE8qQ7zRuWnH_xWQvA@mail.gmail.com> (raw)

Dear eCos Maintainers,

Together with my colleages from Ant Micro, we have updated the
OpenRISC port. We discovered that the OpenRISC HAL was not working
anymore, probably due to ABI change. We have also added few device
drivers. All changes to the code were introduced against the code in
eCos repository. This makes me believe there is no problem with
licensing.

The code still has some identified bugs that should be fixed. Once we
get it done, we would like to contribute the code to the eCos
repostory if possible.

There is one more problem and we seek your advice. Current OpenRISC
architecture is called OpenRISC1000 (aka or1k). There is an update
foreseen. The new architecture will be called OpenRISC2000 (aka or2k)
and it will not be backwards compatible. How should we structure the
HAL directory to take into account the update in the future?

Here is the note about the update:
http://antmicro.com/OpenSource/OpenRISC-eCos

We have a small wiki page that describes the port here:
http://opencores.org/or1k/ECos

The code is hosted on OpenCores SVN, here:
http://opencores.org/ocsvn/openrisc/openrisc/trunk/rtos/ecos-3.0

Thanks in advance,
Piotr Skrzypek

             reply	other threads:[~2013-01-23  9:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23  9:36 Piotr Skrzypek [this message]
2013-01-23 10:56 ` Tomas Frydrych

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='CAAOJC6oe9BaVgu8y6O9e0m1=_DuLbFOtQE8qQ7zRuWnH_xWQvA@mail.gmail.com' \
    --to=peter@skrzypek.eu \
    --cc=ecos-devel@ecos.sourceware.org \
    /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).