From: Nick Garnett <nickg@cygnus.co.uk>
To: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] hi NICK GARNETT - TCP/IP stack of ecos for i386 PC
Date: Fri, 26 May 2000 04:00:00 -0000 [thread overview]
Message-ID: <po4s7lh9bs.fsf@balti.cygnus.co.uk> (raw)
In-Reply-To: <001301bfc6ec$12b11580$3300000a@aftek.com>
"Avinash Dumbre" <avinashd@aftek.com> writes:
> 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.
>
> PLZ help me.
>
> Thanking u in anticipation.
>
While the TCP/IP stack would work fine on the i386 target, we do not
currently have many device drivers for ethernet hardware - this is
still a fairly new component. Currently we have drivers only for ARM
and PowerPC targets. However, one of these, for the EBSA board,
actually uses an Intel EtherPRO/100+ PCI card and so in theory would
work with minimal changes on an EtherPRO/100+ in a PC. However, we do
not have the PCI support code for the PC platform implemented yet.
Of course if you want to put in the effort to make it work, and
contribute it back to the project, we would be very pleased.
--
Nick Garnett
Cygnus Solutions, a Red Hat Company
Cambridge, UK
WARNING: multiple messages have this Message-ID
From: Nick Garnett <nickg@cygnus.co.uk>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] hi NICK GARNETT - TCP/IP stack of ecos for i386 PC
Date: Wed, 05 Sep 2001 00:10:00 -0000 [thread overview]
Message-ID: <po4s7lh9bs.fsf@balti.cygnus.co.uk> (raw)
Message-ID: <20010905001000.gu258sQf4ZhbQ3ULQFPn_8YoWUYGmQWJfYTUvtv6-cc@z> (raw)
In-Reply-To: <001301bfc6ec$12b11580$3300000a@aftek.com>
"Avinash Dumbre" <avinashd@aftek.com> writes:
> 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.
>
> PLZ help me.
>
> Thanking u in anticipation.
>
While the TCP/IP stack would work fine on the i386 target, we do not
currently have many device drivers for ethernet hardware - this is
still a fairly new component. Currently we have drivers only for ARM
and PowerPC targets. However, one of these, for the EBSA board,
actually uses an Intel EtherPRO/100+ PCI card and so in theory would
work with minimal changes on an EtherPRO/100+ in a PC. However, we do
not have the PCI support code for the PC platform implemented yet.
Of course if you want to put in the effort to make it work, and
contribute it back to the project, we would be very pleased.
--
Nick Garnett
Cygnus Solutions, a Red Hat Company
Cambridge, UK
next prev parent reply other threads:[~2000-05-26 4:00 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
2000-05-26 4:07 ` Avinash Dumbre
2000-05-26 4:00 ` Nick Garnett [this message]
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=po4s7lh9bs.fsf@balti.cygnus.co.uk \
--to=nickg@cygnus.co.uk \
--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).