This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
idt mips board port question
- From: "HG" <henri at broadbandnetdevices dot com>
- To: <ecos-discuss at sources dot redhat dot com>
- Date: Fri, 21 Mar 2003 20:23:50 -0500
- Subject: [ECOS] idt mips board port question
- Organization: BND
- Reply-to: "HG" <henri at broadbandnetdevices dot com>
Hi All,
The idt79s334a platform does not have .ldi and .h files in the
include/pkgconf for use in a conventional rom startup environment (like
several of the other mips platform ) , where upon power on the code
retrieved is from 0x9fc0_0000 cached or 0xbfc0_0000 uncached.The .ldi file
in the version 2.0 release and in the cvs show the rom area at an address in
ram at 0x8020_0000.
Is this is a scheme where an existing monitor handles power up to load
redboot at this ram address prior to relocation ????
Has it been tested in the case where the ldi and h files are edited for
conventional rom startup from 0x9fc0_0000 ???? It might be less confusing to
put those files in the cvs since its common to expect rom operation to mean
that the unit actually starts from rom when power is applied .
A similar question applies to the romram configuration , where only the ram
area is shown in the .ldi file
thanks
Henri
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss