- From: David Schleef <ds_at_schleef.org>
- Date: Thu, 30 Jan 2003 14:55:32 -0800
On Thu, Jan 30, 2003 at 07:34:02PM +0100, Herman Bruyninckx wrote: > On Thu, 30 Jan 2003, Frank Mori Hess wrote: > > Above you describe the behaviour of INSN_READ and INSN_WRITE. What you want > > to be doing is using a INSN_CONFIG to modify the behaviour of commands. > > > Yes, but IMHO "modify the behaviour of commands" lead to nothing but > chaos! A common structure such as Comedi is useful, but only where it > can suggest a good common API for a whole range of DAQ cards and > applications. This INSN_CONFIG thing to make an instruction "a la carte" > is something I don't like too much... The alternative is not implementing it at all. At least with extended-triggering configuration instructions, there's the possibility to extend the interface for applications that just don't fit the general model, and are too specific (to a particular application or device) to change the general model to fit it. dave...
Received on 2003-01-30Z22:55:32