This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: warm boot detection
- From: Aaron Richardson <aarichar at cisco dot com>
- To: Jonathan Larmour <jifl at eCosCentric dot com>
- Cc: Ecos-Discuss <ecos-discuss at sources dot redhat dot com>
- Date: Mon, 23 Jun 2003 11:10:39 -0500
- Subject: Re: [ECOS] warm boot detection
- References: <200306231050.14093.aarichar@cisco.com> <3EF72535.2060208@eCosCentric.com>
- Reply-to: aarichar at cisco dot com
On Monday 23 June 2003 11:05 am, Jonathan Larmour wrote:
> Aaron Richardson wrote:
> > Is there some way that I can detect if the platform has been cold booted
> > or warm booted? It would be nice to avoid initializing several things
> > based on this. The SDRAM scrubbing and any memory testing could be
> > skipped.
>
> Normally people simply rely on the HAL startup type (ROM/RAM etc.) to
> indicate whether this instance should do the initialization. If you mean a
> non-eCos program may have done the init on the other hand...
>
> > Also any
> >
> > chips that need to be skipped during a warm boot could be(I have a 21555
> > pci bridge that needs to be skipped).
>
> Surely the best thing is to look at some register in the PCI BIOS to see
> if it's already been initialized?
>
> Or since this is an application specific customisation, just add a bit of
> memory at a common address. Look at how hal_dram_size is treated in the
> ARM arch HAL for example. Just write a magic number into that address when
> booted for the first time and use that to test if it's already been booted
> before.
Thats what I am looking for. That is how I have handled it in the past. Ill
check it out!!
thanks,
Aaron
--
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