public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Alex Schuilenburg" <alexs@redhat.com>
To: "Avinash Dumbre" <avinashd@aftek.com>
Cc: <ecos-discuss@sourceware.cygnus.com>
Subject: RE: [ECOS] hi NICK GARNETT - TCP/IP stack of ecos for i386 PC
Date: Fri, 26 May 2000 03:21:00 -0000	[thread overview]
Message-ID: <NCBBKJPHEKGAJNNFGNBLCEDHEPAA.alexs@redhat.com> (raw)
In-Reply-To: <001301bfc6ec$12b11580$3300000a@aftek.com>

> HI,
>
> Can I use the current ecos version with the beta release
> of the TCP/IP stack for a target platform of i386 PC
>
> Can the TCP/IP stack work on i386 platform since the
> doc for tcp/ip says nothing about the stack implementation
> for i386.
>

Yes you can use the TCPIP stack on the i386, but you will need a device
driver for your ethernet card.  If you check the list archives you will see
that there is a problem in the stack where it currently only operates in
loopback mode if there is a device driver.  From your previous message, it
looks like you are going to need one anyway if that is what you have to
demonstrate.


> PLZ help me.
>
> Thanking u in anticipation.
>
> Sincerely,
>
> Avinash

And before you ask, no, we do not currently have any i386 ethernet device
drivers and are not working on any.  I do also not know of any existing work
in this area either, maybe someone else on this list can help :-)

If not, then you will have to write one yourself.  Documentation exists on
the web explaining how to write a device driver (I do not have the ref
handy).  And of course you are encouraged to submit any such work back to
the community ;-)

-- Alex

  reply	other threads:[~2000-05-26  3:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-26  1:33 Avinash Dumbre
2000-05-26  3:21 ` Alex Schuilenburg [this message]
2000-05-26  4:07   ` Avinash Dumbre
2000-05-26  4:00 ` Nick Garnett
2001-09-05  0:10   ` Nick Garnett
2001-09-05  1:01 Nixon, Roger
2001-09-05  1:30 ` Gary Thomas

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=NCBBKJPHEKGAJNNFGNBLCEDHEPAA.alexs@redhat.com \
    --to=alexs@redhat.com \
    --cc=avinashd@aftek.com \
    --cc=ecos-discuss@sourceware.cygnus.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).