RE: [ECOS] eb40/eb40a platform hals

["Koeller, T." <Thomas dot Koeller at baslerweb dot com>]

You need var/current/include/var_io.h. It is in my patch.
tk

> -----Original Message-----
> From: Tim Drury [mailto:tdrury@siliconmotorsports.com]
> Sent: Thursday, June 27, 2002 5:22 AM
> To: ecos-discuss@sources.redhat.com
> Subject: Re: [ECOS] eb40/eb40a platform hals
> 
> 
> > I have a question about plf_io.h.  This file is in 
> var/current/include
> > and has all the at91 registers, which seems right.  But it also can
> > be found in eb40/current/include where it is empty.  And my version,
> > eb40a/current/include has my LED #defines.  My version doesn't
> > seem to make it into the redboot build tree.  Are they supposed to
> > be merged somehow, or am I supposed to rename my plf_io.h to
> > something else (plf_io_eb40a.h)?
> 
> Actually its the other way around.  The redboot tree has my eb40a/
> current/include/plf_io.h which has my LED #defines but the var/
> current/include/plf_io.h which has all the register #defines 
> is missing.
> 
> What is the correct way to fix this so that both platforms (var and
> eb40a) can have their own platform definitions - var for the common
> at91 stuff and eb40* for the eval board specific definitions?
> 
> -tim
> 
> 
> -- 
> Before posting, please read the FAQ: 
> http://sources.redhat.com/fom/ecos
> and search the list archive: http://sources.redhat.com/ml/ecos-discuss
> 
----------------------------------------------- 
Thomas Koeller, Software Development 

Basler Vision Technologies 
An der Strusbek 60-62 
22926 Ahrensburg 
Germany 

Tel +49 (4102) 463-390 
Fax +49 (4102) 463-46390

mailto:Thomas.Koeller@baslerweb.com 
http://www.baslerweb.com 



-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss