This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: should Ecos re-run hal init code?
- From: Aaron Richardson <aarichar at cisco dot com>
- To: "Gary D. Thomas" <gary dot thomas at mind dot be>
- Cc: eCos Discussion <ecos-discuss at sources dot redhat dot com>
- Date: Mon, 23 Jun 2003 10:45:56 -0500
- Subject: Re: [ECOS] should Ecos re-run hal init code?
- References: <200306230958.49009.aarichar@cisco.com> <2a1ofs$2u8he@sj-iport-2.cisco.com>
- Reply-to: aarichar at cisco dot com
Its not causing me a problem yet. However, I have a 21555 picbridge chip on
my platform and if the init occurs twice on it it will mess up the settings
that got put in there from the bios of the pc thatthe card is sitting in. I
will just have to figure out a way to not initialize this chip if it has
already been done. Ill start a new thread for this...
thanks,
Aaron
On Monday 23 June 2003 10:25 am, Gary D. Thomas wrote:
> On Mon, 2003-06-23 at 08:58, Aaron Richardson wrote:
> > I am getting execution of hal init code when I run my ecos application,
> > specifically my hal_hardware_init() routine. Is this normal behavior for
> > an ecos application? Is it configurable?
>
> This is normal behaviour. The extent of hardware "initialization"
> which occurs is platform specific, but in general is limited for
> non "ROM monitor" applications (i.e. normal applications will
> run through this routine, but the effects are less than when
> the platform first starts)
>
> In general this is not configurable.
>
> Is it causing you some problems?
>
> --
> Gary D. Thomas <gary.thomas@mind.be>
--
Aaron Richardson
aarichar@cisco.com
512-378-1286
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss