From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7790 invoked by alias); 23 Jan 2013 09:36:40 -0000 Received: (qmail 7746 invoked by uid 22791); 23 Jan 2013 09:36:39 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,KHOP_RCVD_TRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-qc0-f172.google.com (HELO mail-qc0-f172.google.com) (209.85.216.172) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 23 Jan 2013 09:36:34 +0000 Received: by mail-qc0-f172.google.com with SMTP id b25so3433881qca.3 for ; Wed, 23 Jan 2013 01:36:33 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.224.9.65 with SMTP id k1mr1104067qak.10.1358933793292; Wed, 23 Jan 2013 01:36:33 -0800 (PST) Received: by 10.49.116.243 with HTTP; Wed, 23 Jan 2013 01:36:33 -0800 (PST) Date: Wed, 23 Jan 2013 09:36:00 -0000 Message-ID: Subject: OpenRISC port From: Piotr Skrzypek To: ecos-devel@ecos.sourceware.org Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact ecos-devel-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-devel-owner@ecos.sourceware.org X-SW-Source: 2013-01/txt/msg00004.txt.bz2 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