This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Re: DHCP shuts down Ethernet device?
- To: Anthony Massa <amassa at logici dot com>
- Subject: Re: [ECOS] Re: DHCP shuts down Ethernet device?
- From: Jonathan Larmour <jlarmour at redhat dot com>
- Date: Mon, 23 Apr 2001 20:29:24 +0100
- Cc: "eCos (E-mail)" <ecos-discuss at sourceware dot cygnus dot com>
- Organization: Red Hat UK Ltd.
- References: <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