This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: ioctl failure with LANCEPCI

From: Magnus Ekhall <koma at lysator dot liu dot se>
To: iztok dot zupet at vsr dot si,Gary Thomas <gthomas at ecoscentric dot com>
Cc: eCos Discussion <ecos-discuss at sources dot redhat dot com>
Date: Fri, 06 Dec 2002 15:30:15 +0100
Subject: Re: [ECOS] ioctl failure with LANCEPCI
References: <5.1.1.6.0.20021206124937.02d75ab0@imap.lysator.liu.se><1039099906.5545.11113.camel@hermes.chez-thomas.org><5.1.1.6.0.20021206124937.02d75ab0@imap.lysator.liu.se>

> There is no simple workaround, is there?

You can try to build the eCos with a fixed IP etc., to avoid DHCP. It used to
work for me when I did the tests lately.

Anyhow, use a fixed IP other than RedBoots.

Iztok

I am running eCos with static IPs. It looks as if eCos pretends that it gets my statically entered IPs in a BOOTP frame: Even though I have static IPs, eCos prints out the DHCP debug information.
The code seems to hang in "in.c" during some ioctl-operation.

Magnus

--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

References:
- Re: ioctl failure with LANCEPCI
  - From: Magnus Ekhall
- Re: ioctl failure with LANCEPCI
  - From: Gary Thomas
- Re: ioctl failure with LANCEPCI
  - From: Iztok Zupet

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]