On Tue 10 Nov 2009 15:13:18 Davidsaver, Michael wrote:
[...]
Of course, this is a non-issue unless the devLib VME api recognizes the
possibility of having more than one VME bridge. This would mean
changing the signatures of all VME functions to take an extra argument
to identify which bus was being referred to. So a particular VME
register would be identified by the triplet bus/space/address.
However, most people will only deal with systems having a single VME
bridge (bus #0). The question is if it is worthwhile to change the api
for a corner case?
By keeping the old API as macros calling the new API functions for bus
#0, you could keep the simple calls for the simple cases, right?
Ralph
- References:
- devLib ruminations Davidsaver, Michael
- Navigate by Date:
- Prev:
devLib ruminations Davidsaver, Michael
- Next:
Re: devLib ruminations Andrew Johnson
- Index:
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:
devLib ruminations Davidsaver, Michael
- Next:
Re: devLib ruminations Andrew Johnson
- Index:
2002
2003
2004
2005
2006
2007
2008
<2009>
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|