- From: Frank Mori Hess <fmhess_at_users.sourceforge.net>
- Date: Wed, 29 Jan 2003 11:52:21 -0600
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 29 January 2003 11:20 am, Herman Bruyninckx wrote: > On Wed, 29 Jan 2003, Frank Mori Hess wrote: > > [...] > > > 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. > > Okay, I begin to see some more light :-) Thanks for bearing with us. > > But this INSN_CONFIG_BLOCK_SIZE configuration is not really extremely > documented, is it? I only find a single line in de > Documentation/insn_config file, and that line is not too clear. I also > don't find any driver that already uses it. We are willing to do this > for the NI driver, but than we should get very clear information about > what the _exact_ semantics of this config option is. Can you give this? > (And include it in the documentation afterwards :-) > > Herman The cb_pcidas64.c driver is the only one that uses it. There are a few lines in the documentation file, the lines below the one you saw, describing what the elements of the data array mean. The zeroth element is just INSN_CONFIG_BLOCK_SIZE, and the next element is the block size in bytes. The driver should write back the actual block size it is using if it can't achieve exactly the block size that was requested. - -- Frank -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE+OBTV5vihyNWuA4URAtX3AKDOp987GQzcNuYZa8o7WdAJiIxs0QCgnFli NhaDR4BZtTyGMnt8aDDeI+Q= =tlJN -----END PGP SIGNATURE-----
Received on 2003-01-29Z17:52:21