From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21487 invoked by alias); 23 Jan 2013 10:56:38 -0000 Received: (qmail 21477 invoked by uid 22791); 23 Jan 2013 10:56:37 -0000 X-SWARE-Spam-Status: No, hits=-3.4 required=5.0 tests=BAYES_00,KHOP_THREADED,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from r-finger.com (HELO r-finger.com) (178.79.160.5) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 23 Jan 2013 10:56:31 +0000 Received: from [192.168.0.2] (host86-137-77-182.range86-137.btcentralplus.com [86.137.77.182]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by r-finger.com (Postfix) with ESMTPSA id 8B3FD9BF8 for ; Wed, 23 Jan 2013 10:56:30 +0000 (GMT) Message-ID: <50FFC1DD.5040702@r-finger.com> Date: Wed, 23 Jan 2013 10:56:00 -0000 From: Tomas Frydrych User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.5) Gecko/20120624 Icedove/10.0.5 MIME-Version: 1.0 To: ecos-devel@ecos.sourceware.org Subject: Re: OpenRISC port References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/msg00005.txt.bz2 Hi, On 23/01/13 09:36, Piotr Skrzypek wrote: > 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. This is excellent news; I looked what could be done about updating the ecos orc platform based on the OpenRISC fork about a year ago after the excellent OpenRISC talk at FOSDEM, but was not able to find out who the real authors were so that the copyright re-assignment could be done. > 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? I am not a maintainer, but since these are two different architectures, my inkling would be toward renaming the current architecture to something like 'hal/openrisk1k' so that later on you can add 'hal/openrisk2k'. Tomas