Thread: [libdc] Power management in CMU 1394cmdr, Windows 7
Capture and control API for IIDC compliant cameras
Brought to you by:
ddouxchamps,
gordp
From: Mike K. <mi...@kl...> - 2015-04-15 16:46:08
|
Hi list, We use the CMU 1394 driver/DLL combo, version 6.4.6, on Windows 7 and have found that the 1394cmdr driver fails Windows’ Driver Verifier on initial loading due to incorrect handling of STATUS_PENDING. Inspecting the code (power.c) shows that it appears not to handle numerous cases recommended (or required) by Windows driver power management. None of the other system or device drivers fail Driver Verifier. We are looking at this because after some hours of constant streaming from a 1394 camera the driver appears to hang, or lose connection with the camera, or similar issues, and it happens more often with newer, faster hardware. (Detailed symptoms vary, but the underlying error code is the same — ntdll.dll, exception code 0xc0000005.) We have no driver expertise and are looking for alternatives such as libdc1394, but since libdc1394 on Windows relies on the CMU driver code it may have similar issues. Has anyone here run into similar issues? |
From: Damien D. <dd...@do...> - 2015-05-07 14:44:20
|
Hi Mike, On Wed, 2015-04-15 at 08:29 -0700, Mike Klein wrote: > Hi list, > > We use the CMU 1394 driver/DLL combo, version 6.4.6, on Windows 7 and > have found that the 1394cmdr driver fails Windows’ Driver Verifier on > initial loading due to incorrect handling of STATUS_PENDING. > Inspecting the code (power.c) shows that it appears not to handle > numerous cases recommended (or required) by Windows driver power > management. None of the other system or device drivers fail Driver > Verifier. > > We are looking at this because after some hours of constant streaming > from a 1394 camera the driver appears to hang, or lose connection with > the camera, or similar issues, and it happens more often with newer, > faster hardware. (Detailed symptoms vary, but the underlying error > code is the same — ntdll.dll, exception code 0xc0000005.) > > We have no driver expertise and are looking for alternatives such as > libdc1394, but since libdc1394 on Windows relies on the CMU driver > code it may have similar issues. > > Has anyone here run into similar issues? I vaguely remember running into a similar problem on win7 about two years ago. IIRC the application would stop working after some time, but I didn't dig deeper. I tried to contact the CMU team at the time for other reasons but I did not get any answer from them so I'm not sure the driver is still maintained... Damien -- Damien 高原 Douxchamps http://damien.douxchamps.net/ |