Experimental Physics and
Industrial Control System

Am I right in thinking that the routine  locationProbe  in devlib returns 
SUCCESS to indicate that the given address does *not* respond to VME accesses of 
any size?  I presume the aim here is to indicate that this area of the memory 
map is currently not used.

Should I be using this in my driver to check that a board is present?  The older 
drivers use vxMemProbe, which returns OK if something responds.  It seems wrong 
to expect an error code (S_dev_addressOverlap) as the status return indicating 
success (ie board found), which is what I would have to do if I used the  
locationProbe  routine.

Are there plans to modify the existing drivers to use the devLib facilities?

- Andrew

          ,_}\_.        Andrew Johnson, Technology Division
         /      \       Royal Greenwich Observatory
~~~~~~~~| ,--/;. )~~~~  Madingley Road, Cambridge, UK
    .,  |/  (/  U       Phone: +44 (0)1223 374823
  .`., /_\ . .          Net: [email protected]
     wwWWWww'           WWW: http://cast0.ast.cam.ac.uk/~anj/

Navigate by Date:

Prev: get_convert_table and DBF_STRING sources mcgehee

Next: Re: devLib, locationProbe routine Andrew Johnson

Index: <1994>  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 

Navigate by Thread:

Prev: Re: get_convert_table and DBF_STRING sources Marty Kraimer

Next: Re: devLib, locationProbe routine Andrew Johnson

Index: <1994>  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024