Re: New buffer reading behaviour in continuous acquisition mode?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 29 January 2003 01:19 am, Herman Bruyninckx wrote:
> On Tue, 28 Jan 2003, Frank Mori Hess wrote:
> >
> > I don't see that any change in comedi's api is necessary.  All you need
> > is for end of scan events to be fixed in the driver.  Your callback
> > function can get woken up at the end of every scan, and decide to do
> > something when there are 6 samples available.
>
> Yes. But this doesn't scale nicely: if somebody wants to have a similar
> behaviour, but with buffers of 100K of samples, it seems overkill to
> have to process 100K interrupts, isn't it?
> What you suggest is indeed feasible for our particular application, and
> for the time being this is (one of the differents ways) how we adapted
> the driver. But I would _not_ like to have to maintain a non-standard
> Comedi driver, hence I'm asking what you prefer. What you suggests
> doesn't need adaptation, but it is not optimal at all.

Herman,

The API already supports interrupting after N bytes, as I mentioned in a 
previous email, the INSN_CONFIG_BLOCK_SIZE configuration insn.  So I still 
don't see any need for an api change/extension.
 
- -- 
Frank

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD4DBQE+OAYa5vihyNWuA4URAqAqAJ9BxsXsFM111Z/oWtPgLZ4E8JIdFwCYyFZ3
cxL71K8zpNVL3/4U7YAzeQ==
=eyRU
-----END PGP SIGNATURE-----

Received on 2003-01-29Z16:49:27