public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Narayanan, Anita (CTS)" <Nanita@DBSS.COM>
To: Fabrice Gautier <Fabrice_Gautier@sdesigns.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] RE: ethernet support in ecos
Date: Sun, 03 Dec 2000 20:56:00 -0000	[thread overview]
Message-ID: <8F1D166D08ACD41196EE00B0D020944B3434EF@CTSINENTSXUB> (raw)

I have already included the package "common ethernet support". Iam sorry i
forgot to add that in my previous mail when i was describing the steps i
have taken to install the ethernet support.

Is there anything else which is missing? 

----------------------------------------------------------------------------
-----------------------
Anita Harish
Telecom Software Group
Cognizant Technology Solutions, India Ltd.
Chennai 600020
2541281 (Ext 4437) 
mailto: nanita@chn.cts-corp.com

> -----Original Message-----
> From:	Fabrice Gautier [SMTP:Fabrice_Gautier@sdesigns.com]
> Sent:	Saturday, December 02, 2000 12:46 AM
> To:	'Narayanan, Anita (CTS)'
> Cc:	ecos-discuss@sourceware.cygnus.com
> Subject:	RE: ethernet support in ecos
> 
> > -----Original Message-----
> > From: Narayanan, Anita (CTS) [ mailto:Nanita@DBSS.COM ]
> > Subject: ethernet support in ecos
> > 
> > 
> > For this we have, 
> > 1)have downloaded and added the package for the networking support.
> > 2)have downloaded the ethernet driver (written by Fabrice 
> > Gautier)  "eCos
> > i82559 (intel Pro100) ethernet driver for i386pc platform"
> > 
> > 
> > However, even after adding these packages the option 
> > "Intel PRO/100+ ethernet driver" doesn't get enabled in the ecos
> > configuration tool.
> > 
> > ( there is a dependency on CYGPKG_IP_ETH_DRIVERS macro)
> 
> You probably need (at least) to add the "Common ethernet support" package.
> 
> Regards,
> 
> -- 
> Fabrice Gautier
> fabrice_gautier@sdesigns.com 
This e-mail and any files transmitted with it are for the sole use 
of the intended recipient(s) and may contain confidential and privileged information. 
If you are not the intended recipient, please contact the sender by reply e-mail and 
destroy all copies of the original message. Any unauthorised review, use, disclosure, 
dissemination, forwarding, printing or copying of this email or any action taken in 
reliance on this e-mail is strictly prohibited and may be unlawful.

		Visit us at http://www.cognizant.com

             reply	other threads:[~2000-12-03 20:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-03 20:56 Narayanan, Anita (CTS) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-12-04 14:26 Fabrice Gautier
2000-12-04 12:04 Natarajan, Mekala (CTS)
2000-12-01 11:16 Fabrice Gautier

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=8F1D166D08ACD41196EE00B0D020944B3434EF@CTSINENTSXUB \
    --to=nanita@dbss.com \
    --cc=Fabrice_Gautier@sdesigns.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).