From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20982 invoked by alias); 16 Feb 2010 19:03:24 -0000 Received: (qmail 20855 invoked by uid 22791); 16 Feb 2010 19:03:23 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from mtaout01-winn.ispmail.ntl.com (HELO mtaout01-winn.ispmail.ntl.com) (81.103.221.47) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 16 Feb 2010 19:03:20 +0000 Received: from aamtaout03-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout01-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20100216190308.IBRY4204.mtaout01-winn.ispmail.ntl.com@aamtaout03-winn.ispmail.ntl.com>; Tue, 16 Feb 2010 19:03:08 +0000 Received: from cog.dallaway.org.uk ([213.106.80.48]) by aamtaout03-winn.ispmail.ntl.com (InterMail vG.2.02.00.01 201-2161-120-102-20060912) with ESMTP id <20100216190308.XYDH2093.aamtaout03-winn.ispmail.ntl.com@cog.dallaway.org.uk>; Tue, 16 Feb 2010 19:03:08 +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 o1GJ354Y026052; Tue, 16 Feb 2010 19:03:06 GMT Message-ID: <4B7AEBE9.6090206@dallaway.org.uk> Date: Tue, 16 Feb 2010 19:03:00 -0000 From: John Dallaway User-Agent: Thunderbird 2.0.0.22 (X11/20090625) MIME-Version: 1.0 To: Ilija Stanislevik CC: eCos developers Subject: Re: Ethernet over SPI driver for ENC424J600 References: <4B7A5530.5040404@siva.com.mk> In-Reply-To: <4B7A5530.5040404@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: 2010-02/txt/msg00010.txt.bz2 Hi Ilija Ilija Stanislevik wrote: > The work on the driver is pretty much done. Great! > I intend to spend a day or > two on additional testing before publishing the code. > > 1. Please suggest a place where I could put the code? > 2. In what form I should give the files? It's probably easiest to create a Bugzilla report for this. Attach the new package as a .tar.bz2 file. Attach your changes to ecos.db and to existing packages (if any) in the form of a plain text patch file. You can generate the patch file using: cd packages cvs -q diff -u5 > ecos.patch John Dallaway eCos maintainer