This is the mail archive of the
mailing list for the eCos project.
Re: Porting question
- From: Andrew Lunn <andrew at lunn dot ch>
- To: Gary Parnes <GaryP at logicpd dot com>
- Cc: 'Andrew Lunn' <andrew at lunn dot ch>,"'ecos-devel at sources dot redhat dot com'" <ecos-devel at sources dot redhat dot com>
- Date: Tue, 2 Dec 2003 19:01:46 +0100
- Subject: Re: Porting question
- References: <4D9A0AA4D1393D4D8791FD2985D37E3DBBEC72@lpdsrv04.logicpd.com>
> It seems to me that the header file hal_ebsa285.h contains a rich amount of
> information specific to the SA-110 processor, not the EBSA285 platform.
> Couldn't we make the case that much of the header information -- and
> possibly some code, such as hal_clock_initialize() & hal_clock_reset() --
> should be in the directory ../hal/arm/sa110/var, with the ebsa285
> platform-specific stuff (e.g. initialization of the 21285) residing in
You could, but in practice i think its pointless. The 21285 companion
chip is virtual undispensible. I would be surprised if anybody used
the sa110 without the 21285. Also, Intel only produced the one decide
around the sa110 as far as i know.