Hi sir,
You are absolutely correct i checked in the location and i
could able to find the idle thread there.Thanks for your valuable support.I
am facing one more problem in dm355.I am using dvtb to take a picture and i
could able to take a picture.But i am trying to take a video by using dvtb
it is hitting and error.
This is my script for video capturing using dvtb
setp vpfe width 640
setp vpfe height 480
setp vpfe format 0
setp vpfe input 2
setp engine name encodedecode
setp videnc1 codec mpeg4enc
setp videnc1 numframes 300
setp videnc1 maxWidth 640
setp videnc1 maxHeight 480
setp videnc1 targetBitRate 2000000
func videnc1 -t capture_640.mpeg4
*This is the error i am getting*
<DVTB> $ [vpfe vpfe.1:
Validation pass
DVTB-DEBUG]: dvevmStVpfe.c: vpfe->input = VID_INPUT_SENSOR
Division by zero in kernel.
Division by zero in kernel.
[DVTB-DEBUG]: dvevmStVpfe.c: V4L2 device </dev/video0> initialized
[DVTB-LOG]: dvevmStVidCapture1.c: VPFE device </dev/video0> initialized for
capture
[DVTB-LOG]: dvevmStEngine.c: Engine <encodedecode> opened. Handle d5038
@0x03e77e5e:[T:0x4131bb60] CV - VISA_delete> deleting codec
(localQueue=0xffff, remoteQueue=0xffff)
*[DVTB-ERROR]: dvevmStVidEnc1.c: Unable to initialize Video Encoder*
*[DVTB-ERROR]: dvevmStVidCapture1.c: Unable to initialize Video Encoder
<mpeg4enc>*
[DVTB-LOG]: dvevmStVidCapture1.c: Video [capture][encode] completed for
<-1> frames
[DVTB-DEBUG]: dvevmStVpfe.c: Before video device close
[DVTB-DEBUG]: dvevmStVpfe.c: After video device close
[DVTB-DEBUG]: dvevmStVpfe.c: munmap done for buffer = 0
[DVTB-DEBUG]: dvevmStVpfe.c: munmap done for buffer = 1
[DVTB-DEBUG]: dvevmStVpfe.c: munmap done for buffer = 2
[DVTB-DEBUG]: dvevmStVpfe.c: buffers free done
[DVTB-LOG]: dvevmStVidCapture1.c: Video Encoder <mpeg4enc> closed
[DVTB-LOG]: dvevmStVidCapture1.c: Engine <encodedecode> closed
[DVTB-LOG]: dvevmStVidCapture1.c: Thread Exiting...
On 14 August 2012 12:28, Sekhar Nori <[email protected]> wrote:
> On 8/13/2012 4:19 PM, venkatasubramanian P wrote:
> > Hi sir,
> > Thanks for your replay how can i put dm355 into wait for
> > interrupt mode.My kernel is 2.6.10.
>
> This should hit automatically if ARM is idle. Have a look at ARM's idle
> thread implementation in arch/arm/kernel/process.c. I looked at the
> v3.6-rc1 source. I suspect the location may not have changed in v2.6.10.
>
> Thanks,
> Sekhar
>
--
Regards,
Venkatasubramanian.p
avench systems
#105 80/1 1st Main 3rd Cross
Malleshpalaya
Bangalore - 560075
Karnataka - India
mob: +919035188170
Each man's life depends on his mental ability.
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
