This is the mail archive of the
ecos-devel@sources.redhat.com
mailing list for the eCos project.
Re: Targets with overrides
- From: Gary Thomas <gary at mlbassoc dot com>
- To: Andrew Lunn <andrew at lunn dot ch>
- Cc: eCos development <ecos-devel at sources dot redhat dot com>
- Date: 03 Oct 2003 06:20:37 -0600
- Subject: Re: Targets with overrides
- Organization: MLB Associates
- References: <1065098680.9737.603.camel@hermes> <20031003112951.GA20447@lunn.ch>
On Fri, 2003-10-03 at 05:29, Andrew Lunn wrote:
> On Thu, Oct 02, 2003 at 06:44:41AM -0600, Gary Thomas wrote:
> > I'd like to add some targets to ecos.db which contain explicit CDL
> > overrides (e.g. to force a particular board configuration). I know
> > in the past we avoided doing this because the public tools might not
> > handle it, but it's now many years on and the tools are all new enough.
>
> ".. in the past..", was before my time and im not sure i understand
> what you mean. Could you give a concrete example.
>
Yes, long ago, we had some internal work that supported targets with
additional "configury". It would look something like this:
target viper2_866 {
alias { "A&M Viper PPC866T board" viper866 }
packages { CYGPKG_HAL_POWERPC
CYGPKG_HAL_POWERPC_MPC8xx
CYGPKG_HAL_POWERPC_VIPER
CYGPKG_HAL_QUICC
CYGPKG_IO_SERIAL_POWERPC_QUICC_SMC
CYGPKG_DEVS_ETH_POWERPC_FEC
CYGPKG_DEVS_ETH_POWERPC_VIPER
CYGPKG_DEVS_FLASH_VIPER
CYGPKG_DEVS_FLASH_AMD_AM29XXXXX
}
set_value CYGHWR_HAL_POWERPC_MPC8XX "866T"
set_value CYGHWR_HAL_POWERPC_VIPER_I 0
set_value CYGHWR_HAL_POWERPC_VIPER_II 1
set_value CYGHWR_HAL_POWERPC_BOARD_SPEED 133
description "
This target provides the packages needed to run
eCos on a A&M Viper PPC866 board."
}
The point would be that "ecosconfig new viper2_866" would create a
configuration with the model 866T and it's supporting options set
properly.
Sadly, this crashes 'ecosconfig' (when I tried it today). I guess I
should have tested this before asking opinions.
Oh well...
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates