From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12332 invoked by alias); 26 Oct 2009 21:28:26 -0000 Received: (qmail 12311 invoked by uid 22791); 26 Oct 2009 21:28:24 -0000 X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-bw0-f211.google.com (HELO mail-bw0-f211.google.com) (209.85.218.211) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 26 Oct 2009 21:28:18 +0000 Received: by bwz3 with SMTP id 3so2889387bwz.36 for ; Mon, 26 Oct 2009 14:28:15 -0700 (PDT) Received: by 10.204.152.22 with SMTP id e22mr6608461bkw.93.1256592493484; Mon, 26 Oct 2009 14:28:13 -0700 (PDT) Received: from localhost ([93.85.201.1]) by mx.google.com with ESMTPS id 13sm924898bwz.14.2009.10.26.14.28.11 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 26 Oct 2009 14:28:12 -0700 (PDT) Date: Mon, 26 Oct 2009 21:28:00 -0000 From: Sergei Gavrikov To: Alex Schuilenburg Cc: Ilija Stanislevik , ecos-devel@ecos.sourceware.org Subject: Re: Ethernet over SPI driver for ENC424J600 Message-ID: <20091026212810.GA12538@sg-laptop> References: <4AE546ED.3000303@siva.com.mk> <4AE56642.20201@dallaway.org.uk> <4AE58C05.9000305@ecoscentric.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AE58C05.9000305@ecoscentric.com> User-Agent: Mutt/1.5.18 (2008-05-17) 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: 2009-10/txt/msg00060.txt.bz2 On Mon, Oct 26, 2009 at 11:46:13AM +0000, Alex Schuilenburg wrote: > John Dallaway wrote on 2009-10-26 09:05: > > Ilija Stanislevik wrote: > >> Dear fellows, > >> > >> I use this opportunity to announce our development project. It is > >> a driver for Microchip's ENC424J600 Ethernet controller. [snip] Thank you! > > This is great news. Thank you for letting the eCos community know > > of your plans at an early stage. [snip] > > Are you intending to use lwIP or the FreeBSD TCP/IP stack in your > > project? Regardless, I would encourage you to verify correct > > operation with Simon Kallweit's port of lwIP 1.3.1: > > > > http://download.westlicht.ch/ [snip] > I think it is fair to advise you of the risks involved in using the > newer lwIP 1.3.1 stack and of more stable options available to you > when developing new code for eCos. Since you are developing a new > device driver, I suggest you initially stick with the FreeBSD port > (and optionally older lwIP port) which are known to work reliably, > rather Hello guys, may be I miss something but I thought that any Ethernet eCos driver is enough abstract thing to manage ETH L2 and that does not depend (well, depends a bit) on any next layer, e.g., a TCP/IP implementation (RedBoot TCP/IP, *BSD, lwIP* stacks) even if the driver uses another channel (SPI) to get a memory access to MAC buffers. I talk about generic io/eth/* stuff and..., well some kind of a future devs/eth/mc/spi/* eth_drv_.* routines, for example. Why do you "link" ya L2 controller with some kind of the TCP/IP? I do not understand it enough. Will it be able to use that driver w/out interrupts in a polling mode, i.e. to use RedBoot's TCP/IP=GDB? If it won't be, well, that is code limits, why the lwIP 1.X.X TCP/IP only then? Thank you for any clarifications, Regards Sergei