This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Should there be conflicts in a template of an EcosPro release?
- From: "Andrew Voelkel" <andy at bushtaxi dot com>
- To: <ecos-discuss at sources dot redhat dot com>,<ecos-discuss at ecos dot sourceware dot org>
- Date: Tue, 13 Sep 2005 22:07:23 -0700
- Subject: [ECOS] Should there be conflicts in a template of an EcosPro release?
This is a newbie question. I am trying to figure out why there are disabled
(grayed out) text boxes in the ConfigTool when I open the Redboot template
of an EcosPro release. I'm guessing it has something to do with resolving
conflicts, and indeed when I open the template it complains about unresolved
conflicts. So I am about to teach myself how to diagnose such things.
But it occurs to me that maybe there shouldn't be conflicts in a template
for a commercial product such as EcosPro, delivered for a specific eval
board. Is this an expected state of affairs?
My immediate goal is to enter a default IP address for Redboot, but I can't
get there from here.
Any help would be appreciated!
- Andy Voelkel
Al Mann Foundation
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss