This is the mail archive of the ecos-patches@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: New port for ARM Industrial Module AIM 711 - Checked byAntiVir DEM


On Wed, 2004-04-28 at 04:39, Roland Caßebohm wrote:
> Hi Andrew
> 
> Am Dienstag, 6. April 2004 16:10 schrieb Roland Caßebohm:
> > > This is the only HAL with a hal_aux.h file. Is this
> > > file named correctly? Where do other HAL put auxiliary
> > > information? Maybe in plf_io.h?
> >
> > Yes I think you are right, other platforms have such
> > things in plf_io.h, so I will do that too.
> 
> I'm now back working on the AIM 711 port. 
> 
> I have put the prototypes back to plf_io.h, but because it 
> are included over hal_io.h in vectors.S I get the folloing 
> error:
> 
> Error: bad instruction `typedef struct hal_ks32c_i2c_msg_s'
> 
> Now I remember that this was the reason why I have put them 
> in another header file.
> 
> I have searched e little bit how other platforms make this, 
> but there seems not to be a standart way. The Documentation
> says:
> 
> Auxiliary HALs contain whatever files are necessary to 
> provide the required functionality. There are no predefined 
> set of files required in an auxiliary HAL.
> 
> Maybe I could name it plf_aux.h or plf_misc.h?
> 
> For example the i386 platform have a file plf_misc.h:
> hal/i386/pc/current/include/plf_misc.h

Or, as Nick pointed out, simply protect these changes with
  #ifdef __ASSEMBLER__
     ...
  #endif

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]