This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: PID ROM and eCos
- To: Jonathan Larmour <jlarmour at redhat dot com>
- Subject: Re: [ECOS] PID ROM and eCos
- From: Gary Thomas <gthomas at cambridge dot redhat dot com>
- Date: Wed, 24 Jan 2001 12:20:20 -0700 (MST)
- Cc: Dave Airlie <airlied at parthus dot com>,ecos-discuss at sources dot redhat dot com, Grant Edwards <grante at visi dot com>
- Organization: Red Hat, Inc.
On 24-Jan-2001 Jonathan Larmour wrote:
> Gary Thomas wrote:
>>
>> Look at the startup code for the Cirrus Logic EDB7xxx boards. They
>> support this configuration where the image in ROM (FLASH or whatever)
>> is linked at an address different from where they are stored. If
>> this case is detected, the ROM code simply gets copied to RAM at
>> startup time. Look in the file:
>> hal/arm/edb7xxx/current/include/hal_platform_setup.h
>
> Why was it done this way, and not with a more explicit ROMRAM startup type?
> If you have a separate startup type it is more under user control.
>
It has been this way for more than 18 months - long before the new CDL and
the tools to make adding new/different startup types simple. Also, I only
did it in a moment since running some code on that platform did not perform
adequately from FLASH, but would from RAM.
> Anyway, you can also refer to the way the mips vrc4373 or sh edk7708 do it,
> which use an explicit ROMRAM startup.
And all the trappings [read details and troubles] that go with it.