Raffaele,
>vpfe-capture vpfe-capture: input information not found for the subdev
Did you add your sub device information for adv7180 in the board setup similar
to tvp5146 sub device?
Does vpfe_capture register your sub device?
Murali Karicheri
Software Design Engineer
Texas Instruments Inc.
Ger
Hi Karicheri,
there is an optional info that I think is interesting.
evm-dm365 and bmx board have 128MB DDR2 RAM.
but vpfe_capture.bufsize=4147200 works on evm, but in our board gives this
allocation problem:
(setting instead vpfe_capture.bufsize=1147200 we obtain the situation of the
previous mai
Recalcati [mailto:lamiapost...@gmail.com]
Sent: Tuesday, March 30, 2010 12:24 PM
To: Karicheri, Muralidharan
Cc: davinci-linux-open-source
Subject: Re: isif - debugging on dm365
Hi Karicheri,
there is an optional info that I think is interesting.
evm-dm365 and bmx board have 128MB DDR2 RAM.
but vpfe_captu
yes, see the logs below and the attached board file.
in evm-dm365 vpfe_capture0 interrupts numbers rise during the grabbing, instead
in our board it doesn't happen.
VDINT0 is zero in both boards, but looking documentation seems it should
contain the number of lines to be received in order to tr
>
> [MK] 0 means the interrupt happens right at VD pulse. 1 means after one
> line. You might want to check the signals received from ADV to input of VPFE
> to see if adv is doing what it is configured to do.
>
My colleague has found how to make the vpfe_isr interrupt working with
adv7180.
He has
Raffaele,
[MK] 0 means the interrupt happens right at VD pulse. 1 means after one line.
You might want to check the signals received from ADV to input of VPFE to see
if adv is doing what it is configured to do.
My colleague has found how to make the vpfe_isr interrupt working with adv7180.
He
...@linux.davincidsp.com] On Behalf Of
Karicheri, Muralidharan
Sent: Thursday, April 01, 2010 2:09 PM
To: Raffaele Recalcati
Cc: davinci-linux-open-source
Subject: RE: isif - debugging on dm365
Raffaele,
[MK] 0 means the interrupt happens right at VD pulse. 1 means after one line.
You might want to
I ll send a patch tuesday. Today i am on holyday
2010/4/1, Karicheri, Muralidharan :
> Raffaele,
>
> [MK] 0 means the interrupt happens right at VD pulse. 1 means after one
> line. You might want to check the signals received from ADV to input of VPFE
> to see if adv is doing what it is configure
I was adding isif_cfg.y_c_swap variable, but it need a modification inside
arch/arm/mach-davinci/dm365.c that I think is not the right direction.
I mean, the "isif" platform data is not board related, but it is cpu
related.
I'd like to use isif_set_hw_if_params, but I'm not sure that it is really
Raffaele Recalcati a écrit :
I was adding isif_cfg.y_c_swap variable, but it need a modification
inside arch/arm/mach-davinci/dm365.c that I think is not the right
direction.
I mean, the "isif" platform data is not board related, but it is cpu
related.
sensor or decoder connection to the isif
Hi Jean-Philippe,
I finally create my patch against f5cef8f45739db4c0c1c346296922cac274c87eb
in attachment, but the problem is that isif_set_hw_if_params is not called
by gstreamer.
If I set in drivers/media/video/davinci/isif.c (and not in
drivers/media/video/davinci/dm365_ccdc.c as I don't have
I suppose it does not work, because isif_set_hw_if params is only called
if the user applications is doing a VIDIOC_S_INPUT.
based on your log, it seems gstreamer does not do that.
I don't know if the driver or the application should be corrected.
May be there is a command switch to gstreamer th
e Recalcati [mailto:lamiapost...@gmail.com]
Sent: Monday, April 12, 2010 4:46 AM
To: Jean-Philippe François
Cc: Karicheri, Muralidharan; davinci-linux-open-source
Subject: Re: isif - debugging on dm365
Hi Jean-Philippe,
I finally create my patch against f5cef8f45739db4c0c1c346296922cac274c87eb in
atta
13 matches
Mail list logo
