- From: Frank Mori Hess <fmhess_at_speakeasy.net>
- Date: Thu, 9 Mar 2006 08:20:10 -0500
On Thursday 09 March 2006 06:52 am, Stienen, A.H.A. (CTW) wrote: > Ian, > > Why do you pick insn.n is 4? Isn't .n based on the number of sample > points you want to get back when inserting a data-read request? In the > original test programs of Klaas Gadeyne .n for the config insert was set > to 0. This turned out only to work when first a data-read or a > get-time-of-day was performed on the device, but when .n was set to 1, > it did work properly without the GTODs or data-reads. But other than > this, it seems to an irrelevant option for configuring. It uses insn.n when copying the data array from user-space to kernel-space and back. I expect the kernel would see random garbage in the data array if you set set insn.n too small. -- Frank
Attachments
- application/pgp-signature attachment: stored
Received on 2006-03-09Z13:20:10