From: Grant Edwards <grante@visi.com>
To: Gary Thomas <gthomas@redhat.com>
Cc: ecos-discuss@sourceware.cygnus.com, Nick Barnes <Nick.Barnes@pobox.com>
Subject: Re: [ECOS] Notes on static configuration of an eCos network inte
Date: Mon, 17 Jul 2000 09:29:00 -0000 [thread overview]
Message-ID: <20000717163022.A29604@visi.com> (raw)
In-Reply-To: <XFMail.20000717100312.gthomas@redhat.com>
> > Right now, I'm building a fake bootp record and passing it to
> > init_net(). This seems to be way more work than it's worth
> > (especially since it's not right), so I'm going to throw out
> > all of the fake bootp stuff and just duplicate the code in
> > net_init(), passing the right IP addresses in the ioctl() calls.
> >
> > It will end up being a lot smaller and simpler that way. Is
> > there any reason I shouldn't do that?
>
> The reason that init_net() is based on BOOTP now is for flexibility.
> By having the numbers hard coded [somehow] in the routine, you loose
> all of that.
The numbers aren't hard-coded. I have a structure that
contains the ip address, subnet mask, and default gateway. This
data was constructed by my boot loader code.
> I always vote for flexible; I've been bitten by "fixed"
> implementations too many times in the past.
>
> As for your pain:
> * why do you think the current way of creating BOOTP data is more
> work than coding the values directly?
Perhaps I've misjudged, but at first glance it looked like
constructing a fake bootp frame and then parsing it is more
work than making the ioctl calls directly -- and then I don't
need to keep the routines to first assemble then dissassemble a
bootp frame (not that they're very big, but a few K here and
there add up).
> * how is what you are using different than the code in "init_all_network..."
> when non-BOOTP mode is selected?
It isn't. The code I'm using is mostly copied from
init_all_network and build_bootp_record. It looks like
build_bootp_record and init_all_network_interfaces don't
configure the default route based on the gateway address passed
to build_bootp_record().
> * if things aren't working, ask for help. Nick [Barnes] seems to be
> getting quite a lot [of feedback at least] by doing so.
I realized that the routing wasn't working this morning. By
the time I realized something was wrong, Nick had already
pointed out what it was (he must have borrowed Guido van
Rossum's time machine).
--
Grant Edwards
grante@visi.com
next prev parent reply other threads:[~2000-07-17 9:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-17 5:45 [ECOS] Notes on static configuration of an eCos network interface Nick Barnes
2000-07-17 6:59 ` Bart Veer
2000-07-17 7:07 ` [ECOS] Notes on static configuration of an eCos network inte Gary Thomas
2000-07-18 5:52 ` [ECOS] Notes on static configuration of an eCos network interface Nick Barnes
2000-07-18 8:03 ` Grant Edwards
2000-07-17 8:52 ` Grant Edwards
2000-07-17 9:03 ` [ECOS] Notes on static configuration of an eCos network inte Gary Thomas
2000-07-17 9:28 ` Andrew Lunn
2000-07-17 9:40 ` Grant Edwards
2000-07-17 9:47 ` Andrew Lunn
2000-07-17 9:29 ` Grant Edwards [this message]
2000-07-17 9:45 ` Gary Thomas
2000-07-17 10:01 ` Grant Edwards
2000-07-17 9:45 ` [ECOS] Notes on static configuration of an eCos network interface Hugo 'NOx' Tyson
2000-07-20 7:00 ` Hugo 'NOx' Tyson
2000-07-20 9:57 ` Bart Veer
2000-07-20 11:00 ` Hugo 'NOx' Tyson
2000-07-20 11:19 ` Bart Veer
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=20000717163022.A29604@visi.com \
--to=grante@visi.com \
--cc=Nick.Barnes@pobox.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=gthomas@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).