public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Rohit Agarwal <rohitrules@gmail.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] connecting a wi-fi lan card to a IXDP425 processor using the PCI slot
Date: Fri, 22 Jul 2005 10:38:00 -0000	[thread overview]
Message-ID: <20050722103755.GW15048@lunn.ch> (raw)
In-Reply-To: <fc5cbb3205072202377128cb04@mail.gmail.com>

> 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

  reply	other threads:[~2005-07-22 10:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-20  5:18 Rohit Agarwal
2005-07-20  5:45 ` Andrew Lunn
2005-07-20  6:30   ` Rohit Agarwal
2005-07-20 18:17     ` L D
2005-07-20 18:28       ` Andrew Lunn
2005-07-22  9:38         ` Rohit Agarwal
2005-07-22 10:38           ` Andrew Lunn [this message]
2005-07-22 12:10             ` Rohit Agarwal
2005-07-22 14:12           ` [ECOS] " Grant Edwards
2005-07-21 16:14       ` Grant Edwards
2005-07-22 12:15       ` [ECOS] " Rohit Agarwal
2005-07-20  6:31   ` Rohit Agarwal
2005-07-20  6:32   ` Rohit Agarwal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050722103755.GW15048@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=rohitrules@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).