Experimental Physics and
Industrial Control System

Andrew Johnson <[email protected]> · Thu, 27 Aug 1998 09:00:47 +0100

Bob Dalesio wrote:
> 
> It seems to me that there are two possible approaches to looking
> at the Industry Pac interfaces.
> 1) That each Carrier Board is the driver
>         Therefore a list of devices on the carrier board is kept
>         Driver reports are done from the carrier board perspective
> 2) Each different IP module board is the driver
>         A seperate report,init exists for each IP module supported
>         Carrier boards have no driver - but address mapping and interrupt handling routines
> 
> I am interested to hear how this was handled in the different drivers.

My drvIpac combines both of the above approaches - there are init &
report routines which are part of drvIpac and report all of the carrier
boards registered with it.  Any modules installed on a carrier are
listed by the drvIpac report function, but there is no direct link from
this to the relevent module driver, which will have its own drvET init &
report routines and uses the other services of drvIpac.

-- Andrew
   ___
 .'   `.	Andrew Johnson, Head of Electronics
/ Royal )	Royal Greenwich Observatory
\ Greenwich	Madingley Road, Cambridge, CB3 0EZ
| Observatory	Tel: +44 1223 374823   Fax: 374700
+----------	WWW: http://www.ast.cam.ac.uk/~anj

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System