> The API says "free this frame up". But it isn't being freed up for anything. Well, from a drivers point of view it makes _some_ sense. The driver can free any resources required to capture the frame at this point (but not the image data itself of course). bttv for example needs some memory for the bt848 risc controller instructions. Same goes for unlocking I/O-locked pages. Neverless it is confusing ... Gerd -- #define ENOCLUE 125 /* userland programmer induced race condition */
