This is the mail archive of the
ecos-patches@sources.redhat.com
mailing list for the eCos project.
Re: New port for ARM Industrial Module AIM 711 - Checked by AntiVir DEM
- From: Roland Caßebohm <roland dot cassebohm at VisionSystems dot de>
- To: Andrew Lunn <andrew at lunn dot ch>
- Cc: John Dallaway <jld at ecoscentric dot com>, ecos-patches at ecos dot sourceware dot org
- Date: Wed, 28 Apr 2004 12:39:40 +0200
- Subject: Re: New port for ARM Industrial Module AIM 711 - Checked by AntiVir DEM
- References: <200403031753.44381.roland.cassebohm@visionsystems.de> <20040406130255.GW29940@lunn.ch> <200404061610.13650.roland.cassebohm@visionsystems.de>
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
Roland
--
___________________________________________________
VS Vision Systems GmbH, Industrial Image Processing
Dipl.-Ing. Roland Caßebohm
Aspelohe 27A, D-22848 Norderstedt, Germany
http://www.visionsystems.de
___________________________________________________