From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3631 invoked by alias); 22 Jul 2005 10:38:39 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 3514 invoked by uid 22791); 22 Jul 2005 10:38:32 -0000 Received: from londo.lunn.ch (HELO londo.lunn.ch) (80.238.139.98) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 22 Jul 2005 10:38:32 +0000 Received: from lunn by londo.lunn.ch with local (Exim 3.36 #1 (Debian)) id 1Dvuuh-0001U5-00; Fri, 22 Jul 2005 12:37:55 +0200 Date: Fri, 22 Jul 2005 10:38:00 -0000 To: Rohit Agarwal Cc: ecos-discuss@sources.redhat.com Message-ID: <20050722103755.GW15048@lunn.ch> Mail-Followup-To: Rohit Agarwal , ecos-discuss@sources.redhat.com References: <20050720181725.12866.qmail@web88208.mail.re2.yahoo.com> <20050720182755.GI29741@lunn.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i From: Andrew Lunn Subject: Re: [ECOS] connecting a wi-fi lan card to a IXDP425 processor using the PCI slot X-SW-Source: 2005-07/txt/msg00234.txt.bz2 > level of work I am supposed to do. But all this was undecided when i > took up my project. I have come to the mailing list to solve my > problem. OK. If you really want to do this, i suggest you get hold of the books : TCP/IP Illustrated, Volume 1, The Protocols, W. Richard Stevens - ISBN 0-201-63346-9 TCP/IP Illustrated, Volume 2, The Implementation, Gary R. Wright, W. Richard Stevens - ISBN 0-201-63354-X These two books are really good at explaining TCP/IP and the implementation in BSD systems. To get this working you are going to have to get deeply involved with the insides of TCP/IP and being able to debug TCP/IP when you have bugs in your port. I also suggest you get hold of another desktop machine and install FreeBSD and make 802.11 networking work. You want to be able to compile the kernel from sources and be able to debug them. You will be using this as a reference platform. You can compare how things work on this platform compared to what happens when you have bugs in your port on eCos. I also suggest you put your target hardware away for the moment and use the synthetic version of ecos running on top of linux. You will find that platform much easier to use and debug. Get the networking working properly with synth, make sure you can run all the network tests etc. Gary Thomas can probably give you the clean FreeBSD sources he started his port from. Diff'ing between those clean sources and the current eCos sources will give you can idea what had to be changed to get the FreeBSSD stack into eCos. You will need similar changes in your new port. Applying the diff will get you some way in the right direction, but i expect there will be conflicts you need to fix. Your aim is to get the existing network tests working with the new TCP/IP stack. You can probably forget about 802.11 for the moment. You can come back to that once TCP/IP is working over ethernet. That should be enought to keep you busy for a while. Andrew -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss