Eric Bjorklund wrote:
> My question here is that since we're mucking with the aao record anyway,
> wouldn't
> it be better to have the record support module allocate the buffer during
> pass 0
> based on NELM and FTVL? Then the only device support change would be to
> *remove*
> the buffer allocation code. We would, of course, have to be sure that FTVL was
> set correctly in each of the records -- for me that would be no problem (and I
> suspect it wouldn't be for Timor either at this point).
Will this work with all device support attached to aao?
It sounds like the best solution if it works. Unless someone out there objects I
say use this solution. It does mean any device support has to be changed, but
this can be stated in the release notes.
Marty
- Replies:
- Re: aao record behaviour Korhonen Timo
- References:
- Re: aao record behaviour Korhonen Timo
- Re: aao record behaviour Eric Bjorklund
- Navigate by Date:
- Prev:
Re: aao record behaviour Eric Bjorklund
- Next:
Arbitrary waveform generator Garrett D. Rinehart
- 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: aao record behaviour Eric Bjorklund
- Next:
Re: aao record behaviour Korhonen Timo
- 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
|