From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28564 invoked by alias); 26 Oct 2009 12:04:39 -0000 Received: (qmail 28487 invoked by uid 22791); 26 Oct 2009 12:04:37 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from mtaout03-winn.ispmail.ntl.com (HELO mtaout03-winn.ispmail.ntl.com) (81.103.221.49) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 26 Oct 2009 12:04:33 +0000 Received: from aamtaout02-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout03-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20091026120430.QIHU17277.mtaout03-winn.ispmail.ntl.com@aamtaout02-winn.ispmail.ntl.com>; Mon, 26 Oct 2009 12:04:30 +0000 Received: from cog.dallaway.org.uk ([213.106.93.52]) by aamtaout02-winn.ispmail.ntl.com (InterMail vG.2.02.00.01 201-2161-120-102-20060912) with ESMTP id <20091026120430.RSMU21638.aamtaout02-winn.ispmail.ntl.com@cog.dallaway.org.uk>; Mon, 26 Oct 2009 12:04:30 +0000 Received: from cog.dallaway.org.uk (cog.dallaway.org.uk [127.0.0.1]) by cog.dallaway.org.uk (8.13.8/8.13.8) with ESMTP id n9QC4SvG018964; Mon, 26 Oct 2009 12:04:28 GMT Message-ID: <4AE5904C.8080502@dallaway.org.uk> Date: Mon, 26 Oct 2009 12:04:00 -0000 From: John Dallaway User-Agent: Thunderbird 2.0.0.22 (X11/20090625) MIME-Version: 1.0 To: Ilija Stanislevik CC: ecos-devel@ecos.sourceware.org Subject: Re: Ethernet over SPI driver for ENC424J600 References: <4AE546ED.3000303@siva.com.mk> <4AE56642.20201@dallaway.org.uk> <4AE5857B.6020309@siva.com.mk> In-Reply-To: <4AE5857B.6020309@siva.com.mk> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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: 2009-10/txt/msg00055.txt.bz2 Hi Ilija Ilija Stanislevik wrote: > I have already harnessed the Microchip board with ENC624J600 to my > STM3210E-EVAL. The 424 and 624 chips are identical regarding the SPI > functionality. I plan to do most of the development on 624, till our > hardware with 424 gets ready. Great. Hopefully your driver will correctly initialise both parts for operation in SPI mode with no extra effort. > We intend to use lwip. That's good. I envisage that the lwIP 1.3.1 stack will become popular with eCos developers. > Please explain what will be our obligations if we decide to register > this project. The main ideas behind project registration are to encourage collaboration on new eCos components, to minimise duplicated effort and to allow for early feedback from the eCos maintainers. With this mind, we would expect: a) contribution of the code to eCos CVS when it is ready (subject to review by the eCos maintainers and copyright assignment to FSF) b) sharing of your pre-release code with others in the eCos community on request c) responsiveness to feedback from the community In fact, the lwIP 1.3.1 port is a good example of how the community can work together in this way. There are several people already making use of this code. John Dallaway