From: Jonathan Larmour <jlarmour@redhat.com>
To: Anthony Massa <amassa@logici.com>
Cc: "eCos (E-mail)" <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] Re: DHCP shuts down Ethernet device?
Date: Mon, 23 Apr 2001 12:29:00 -0000 [thread overview]
Message-ID: <3AE48294.6C00FA4C@redhat.com> (raw)
In-Reply-To: <281963D01A08D511A5D700A0C9AC979A04EEDD@EXCHANGE>
Anthony Massa wrote:
>
> >> I am running RedBoot on an MBX board and downloading my eCos
> >application
> >> with networking support.
> >>
> >> I noticed your post about the Ethernet device shutdown and
> >was wondering if
> >> I could possibly be running
> >> into the same problem.
> >
> >Only if you don't have a DHCP server on your net and you're
> >trying to use
> >the ethernet driver for other purposes than the TCP/IP stack.
>
> I have a DHCP server on my net. However, my confusion comes with the fact
> that I have RedBoot coming up using BOOTP, which I have a server for as
> well. So, RedBoot gets its IP address. Is this address then passed onto
> the application, or is the application layer supposed to get its own, new
> address?
>
> I'm a little confused about how the RedBoot and eCos app layer stack coexist
> on my target. I am using the RedBoot Ethernet for debugging the
> application.
They each get their own addresses. Or one can be static and the other
dynamic, or whatever you want. Think of them as completely separate.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
next prev parent reply other threads:[~2001-04-23 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-23 12:25 Anthony Massa
2001-04-23 12:29 ` Jonathan Larmour [this message]
2001-04-24 6:00 ` Hugo Tyson
-- strict thread matches above, loose matches on Subject: below --
2001-04-23 11:49 Anthony Massa
2001-04-23 12:22 ` Jonathan Larmour
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=3AE48294.6C00FA4C@redhat.com \
--to=jlarmour@redhat.com \
--cc=amassa@logici.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).