public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: rpai@it.iitb.ac.in
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] lwip eth doubt........
Date: Wed, 25 May 2005 07:53:00 -0000	[thread overview]
Message-ID: <33253.10.129.11.162.1116958423.squirrel@www.it.iitb.ac.in> (raw)

  hello...

         we are in way of creating a firewall application... we are doing
with lwip stack..   .as there is no routing support we are way to
make it..
     we are unable to find , how the 2 eths are to be initalized as done
in bsd ..

     can u tell me is there any flag to b removed to get 2 eths initalized
.. this came into mind when we were looking this function in init.c
file in net/lwip/src directory...

 the code is as........
*************************
static void
init_hw_drivers(void)
{

  cyg_netdevtab_entry_t *t;

  for (t = &__NETDEVTAB__[0]; t != &__NETDEVTAB_END__; t++) {
        diag_printf("H/W device name:%s\n",t->name);
  if (t->init(t)) {
      t->status = CYG_NETDEVTAB_STATUS_AVAIL;
    } else {
      // What to do if device init fails?
      t->status = 0;            // Device not [currently] available
    }
  }

}

*************8
this loop is executing only once.....
can u tlell me the logic behind and wht to do to get it move 2 times to
detect eth1 also...

   if this is also over the routing part my project will b over....

  some doucmentation also will b usefule to us

plze....... do help..

    Regards
        Pai





-- 
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-05-24 18:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-25  7:53 rpai [this message]
2005-05-25 12:44 ` [ECOS] " Jani Monoses

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=33253.10.129.11.162.1116958423.squirrel@www.it.iitb.ac.in \
    --to=rpai@it.iitb.ac.in \
    --cc=ecos-discuss@sources.redhat.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).