From: Grant Edwards <grante@visi.com>
To: Gary Thomas <gthomas@redhat.com>
Cc: Nick Barnes <Nick.Barnes@pobox.com>, ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Notes on static configuration of an eCos network inte
Date: Mon, 17 Jul 2000 10:01:00 -0000 [thread overview]
Message-ID: <20000717170227.A29756@visi.com> (raw)
In-Reply-To: <XFMail.20000717104544.gthomas@redhat.com>
On Mon, Jul 17, 2000 at 10:45:44AM -0600, Gary Thomas wrote:
> > 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.
>
> The idea was [the hope was] that the required data would be
> exactly what BOOTP provides if used. Having you mimic BOOTP
> was supposed to make this easier.
It would -- except that the boot loader code that builds the
structure containing the IP info already existed, and rather
than modify that code (it's built under DOS with ARM tools -- I
mess with it as little as possible), I just passed the IP
addresses it provides to my copy of build_bootp_record which
puts the gateway address in the bp_giaddr.s_addr feild instead
of adding it to the body with TAG_GATEWAY as it should.
The right thing to do would be:
1) Port the boot-loader over to the gnu toolset. Right now
it's a royal PITA to work with.
2) Change the boot loader so that it exports a bootp record
instead of our home-made structure -- if there's no IP info
in flash it will use DHCP to get an address, but then it
tears apart the bootp response and puts the info into the
aforementioned structure.
Then I wouldn't need my hacked version of build_bootp_record.
> I haven't looked at how the DHCP support has changed this, so
> maybe it will improve. If not, we're certainly open to
> listening to what you need.
What I really need is some spare time...
;)
--
Grant Edwards
grante@visi.com
next prev parent reply other threads:[~2000-07-17 10:01 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
2000-07-17 9:45 ` Gary Thomas
2000-07-17 10:01 ` Grant Edwards [this message]
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=20000717170227.A29756@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).