public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: <vijay.peshkar@wipro.com>
To: <jerzy.dyrda@kontron.pl>, <ecos-discuss@ecos.sourceware.org>,
		<kgardas@objectsecurity.com>
Subject: RE: [ECOS] ixp42x NPE networking build issue.
Date: Mon, 17 Jul 2006 05:40:00 -0000	[thread overview]
Message-ID: <D6DA3A176076B2408E53467FC0B0056B0370CD7A@BLR-EC-MBX04.wipro.com> (raw)


 Hi all,

Am a newbie to ecos on ixp425 npe.
Searching my mails archive, found the below discussion.
Any pointers on availiblity of eth npe driver(if_npe.c ?)
Or I will have to write it from scratch?.

Jerzy and Karel - any pointers would be helpful.

Regards,
Vijay

-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of jerzy dyrda
Sent: Monday, January 09, 2006 3:37 PM
To: ecos-discuss@ecos.sourceware.org; Karel Gardas
Subject: Re: [ECOS] ixp42x NPE networking build issue.

Hello all,

On Wednesday 28 of December 2005 23:00, Mark Salter wrote:
> On Wed, 2005-12-28 at 22:13 +0100, Karel Gardas wrote:
> > I've also copied Jerzy's if_npe.c and now I'm fighting with various
> > compilation issues. Generaly Intel code's complaining about RebBoot
> > not enabled. Is RedBoot required for this to work? i.e. do I need to

> > build my NPE-enabled eCos app including RedBoot just to be able to
build it?
>
> Hmm, Jerzy may have had to make changes in the Intel code to get it
> all to build. RedBoot isn't the solution.
>

Sorry, but I have had vacation.

I made some modification in Intel code ( very minor ) but without their
npe
driver can't be compiled.  
Regarding MAC address - I "ported" this driver to custom board with own
mac getting mechanism ( I have special function to do it) - please don't
suggest actual state of CONFIG_ESA - it is valid only for RedBoot.

Karel :  I assume that you need to add some defines like DEBUG ( I made
mistake add counter - variable i - and forgot to remove, this problem
appears only when DEBUG is define ) or NPE_USE_INTS ( initially I tried
to use suspended thread to pool dispatcherFunc() ) which are added to
cdl file.

Best Regards,
jerzy


--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss



The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com

--
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:[~2006-07-17  5:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-17  5:40 vijay.peshkar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-26  5:59 sumanth
2006-07-26 14:57 ` Mark Salter
2006-08-01 13:15 ` sumanth
2006-08-01 15:34   ` Mark Salter
2006-07-20 10:29 vijay.peshkar
2006-07-20 13:36 ` Mark Salter
2006-07-18  3:44 vijay.peshkar
2006-07-18 14:22 ` Mark Salter
2005-12-28 16:56 Karel Gardas
2005-12-28 17:10 ` Andrew Lunn
2005-12-28 17:15 ` Mark Salter
2005-12-28 18:35   ` Karel Gardas
2005-12-28 20:39     ` Karel Gardas
2005-12-28 21:05       ` Mark Salter
2005-12-28 21:14         ` Karel Gardas
2005-12-28 21:31           ` Andrew Lunn
2005-12-28 21:51             ` Karel Gardas
2005-12-28 22:00           ` Mark Salter
2006-01-09 10:07             ` jerzy dyrda

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=D6DA3A176076B2408E53467FC0B0056B0370CD7A@BLR-EC-MBX04.wipro.com \
    --to=vijay.peshkar@wipro.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=jerzy.dyrda@kontron.pl \
    --cc=kgardas@objectsecurity.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).