Re: [libdc] Crash behaviour change from v1 to v2
Capture and control API for IIDC compliant cameras
Brought to you by:
ddouxchamps,
gordp
From: Georg K. <gk...@ro...> - 2008-07-17 13:35:07
|
On Thu, 17 Jul 2008, Damien Douxchamps wrote: > > > Hello Georg, > > On Wed, 2008-07-16 at 21:14 +0200, Stefan Richter wrote: > > Georg Klein wrote: > > > I'm guessing this has to do with bandwidth allocation. > > > > If need be, you can peek & and poke at the bandwidth_available > > register with firecontrol. (A simple but pretty handy tool using > > libraw1394, if you didn't come across it yet; formerly called > > 1394commander.) > > You can also choose not to do any bandwidth allocation at all. The > dc1394_capture_setup() function has a flag argument for this. That would > make libdc1394 behave roughly like version 1. Ah yes, it appears that our dc1394v1 code allocated neither channel nor bandwidth. If I make the v2 code do the same (by passing zero to the flags parameter) it does indeed behave the same as v1. That's great for a drop-in replacement, thanks! But I guess running without resource allocation is probably not the polite thing to do if the bus is being used for other things as well? Regards Georg |