This is the mail archive of the
ecos-devel@sourceware.org
mailing list for the eCos project.
Possible bug with CYGSEM_REDBOOT_NETWORK_INIT_ONE_DEVICE
- From: David Fernandez <dfernandez at cct dot co dot uk>
- To: ecos-devel at ecos dot sourceware dot org
- Date: Mon, 27 Nov 2006 10:19:46 +0000
- Subject: Possible bug with CYGSEM_REDBOOT_NETWORK_INIT_ONE_DEVICE
- Organization: Concurrent Technologies, Plc
- Reply-to: dfernandez at cct dot co dot uk
Hi there,
I'was about to use the feature CYGSEM_REDBOOT_NETWORK_INIT_ONE_DEVICE,
and I've noticed that may be it doesn't work as per the description in
the cdl option:
It says that it should stop initializing network devices as soon as one
is initialized successfully. But it seems that the initialization logic
for a default interface has someway confused the things.
It tries to initialize the default interface, but if it fails, then it
seems to initialize all of them... I think there should be a break
statement within the "if (t->init())" block (net_io.c: net_init()) if
this options is active and enabled.
May be the we can get rid of CYGSEM_REDBOOT_FLASH_CONFIG condition in
CYGDAT_REDBOOT_DEFAULT_NETWORK_DEVICE (doing the appropriate changes in
net_io.c: net_init()), so we could provide a default interface if there
is no flash configured.
Anybody thinks a patch to change all this is interesting?