I am trying to build the encode demos from
the beta dvsdk for dm365 evm, and it fails with the following message :
cl470MV package/cfg/encode_x470MV.c ...
In file included from package/cfg/encode_x470MV.c:280:
/home/cynove/src/ARM/davinci/dvsdk_2_10_00_13/framework_components_2_23/packages/ti/sdo
Is the EDMA3_LLD_INSTALL_DIR variable in the Rules.make set to the right path
where the edma3_lld_xx package is installed? If not, please try building the
demos after setting it.
Regards,
Prem
-Original Message-
From: davinci-linux-open-source-boun...@linux.davincidsp.com
[mailto:davi
JayaKumar, PremKumar a écrit :
Is the EDMA3_LLD_INSTALL_DIR variable in the Rules.make set to the right path
where the edma3_lld_xx package is installed? If not, please try building the
demos after setting it.
Regards,
Prem
Thank you for your answer.
I think the path is ok :
# Where the EDM
Update :
If I apply the following patch, dmai builds correctly.
Index:
dvsdk_2_10_00_13/dmai_1_21_00_06/packages/ti/sdo/dmai/apps/fc_common.cfg
===
---
dvsdk_2_10_00_13.orig/dmai_1_21_00_06/packages/ti/sdo/dmai/apps/fc_common.cfg
Hi Deepaks,
Have you gotten success in entering/exit from deep sleep mode on DM355? How
to execute the assembly code Sleep.S? Please help.
Thanks,
Jeff
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
ht
Hi Jeff,
We are able to take the system into deep sleep but not fully -
Here is a link already sent to the community based on which we were working.
Just that we had some customization based on our target.
I think it should help
http://www.mail-archive.com/davinci-linux-open-source@linux.davinci
Denys Dmytriyenko wrote:
> On Fri, Jun 26, 2009 at 12:46:31AM +0300, Yusuf Caglar AKYUZ wrote:
>> Karicheri, Muralidharan wrote:
>>> We have been using the arago git tree and I don't see any of the issues
>>> that you are seeing. Could you use arago tree and Let me know if you see
>>> the same is
Hi
I wrote some question fee days ago. Now I have managed to open capture
device. It was my fault. Now it seems that capture device is initialized,
but it crash without any error message. I have compared resizer and
previewer initialization and V4L2 initialization with examples. It should be
o
Hi,
Please try attached fc_common.cfg. This is from dvsdk_2_10_00_16, it works
fine. I believe build 13 has missing ADDRSPACE module in cfg file.
I believe this image is UYVY, but the application defaults to 422P chroma
format. You can try "--iColorSpace 3". Without this option, I did not get a
Saran, Sajesh Kumar a écrit :
Hi,
Please try attached fc_common.cfg. This is from dvsdk_2_10_00_16, it works
fine. I believe build 13 has missing ADDRSPACE module in cfg file.
I believe this image is UYVY, but the application defaults to 422P chroma format. You can
try "--iColorSpace 3". With
David Brownell writes:
> From: David Brownell
>
> Remove some remnants of ancient NAND code that have been
> lingering in the DaVinci tree ... so this tree is a closer
> match to mainline.
>
> Signed-off-by: David Brownell
Thanks, pushing today.
Kevin
On Monday 22 June 2009 10:14:30 chaithrika wrote:
> Kevin,
>
> I think this patch has to be taken into DaVinci tree so that it
> can be submitted upstream. This patch has to be present in the Linux
> tree for Hans to prepare a pull request for DM646x display driver
> patches.
What are the plans
Hans Verkuil writes:
> On Monday 22 June 2009 10:14:30 chaithrika wrote:
>> Kevin,
>>
>> I think this patch has to be taken into DaVinci tree so that it
>> can be submitted upstream. This patch has to be present in the Linux
>> tree for Hans to prepare a pull request for DM646x display driver
Chaithrika U S writes:
> Platform specific display device setup for DM646x EVM
>
> Add platform device and resource structures. Also define a platform specific
> clock setup function that can be accessed by the driver to configure the clock
> and CPLD.
>
> This patch is dependent on a patch submi
Kevin Hilman writes:
> Chaithrika U S writes:
>
>> Platform specific display device setup for DM646x EVM
>>
>> Add platform device and resource structures. Also define a platform specific
>> clock setup function that can be accessed by the driver to configure the
>> clock
>> and CPLD.
>>
>> Thi
Chaithrika U S writes:
> Platform specific display device setup for DM646x EVM
>
> Add platform device and resource structures. Also define a platform specific
> clock setup function that can be accessed by the driver to configure the clock
> and CPLD.
>
> This patch is dependent on a patch submi
On Friday 26 June 2009 20:25:42 Kevin Hilman wrote:
> Hans Verkuil writes:
>
> > On Monday 22 June 2009 10:14:30 chaithrika wrote:
> >> Kevin,
> >>
> >> I think this patch has to be taken into DaVinci tree so that it
> >> can be submitted upstream. This patch has to be present in the Linux
> >>
s-paul...@ti.com writes:
> From: Sandeep Paulraj
>
> Patch updates DM365 PINMUX by adding entries for Video, SPI 1 - 4,
> PWM 0 - 3.
>
> Signed-off-by: Sandeep Paulraj
> ---
[...]
> +MUX_CFG(DM365, VOUT_FIELD, 1, 18,3,1, false)
> +MUX_CFG(DM365, VOUT_FIELD_G81, 1,
Kevin,
I see the problem.
I will have to send an update.
I will need to create multiple entries for VIN_YIN_EN.
Thanks,
Sandeep
> -Original Message-
> From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
> Sent: Friday, June 26, 2009 3:03 PM
> To: Paulraj, Sandeep
> Cc: davinci-linux
Hi All,
Anyone tried arecord in 2.6.30. I am constantly getting a overrun error which
is blocking the capture.
Thanks,
Arun
-Original Message-
From: davinci-linux-open-source-boun...@linux.davincidsp.com
[mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of
Brian
Signed-off-by: Kevin Hilman
---
drivers/usb/musb/davinci.c | 27 +--
1 files changed, 1 insertions(+), 26 deletions(-)
diff --git a/drivers/usb/musb/davinci.c b/drivers/usb/musb/davinci.c
index edc165f..10d11ab 100644
--- a/drivers/usb/musb/davinci.c
+++ b/drivers/usb/m
This series drops all davinci git local diffs w/mainline (v2.6.30) and
adds them back as patches that can be submitted upstream.
The changelog on patch 2/3 comes from the original commit of
davinci git, but clearly needs an update since lots of the
stuff from original commit has already made its w
Now that the pcf857x GPIO expanders are used for GPIOs on the dm644x
EVM board code, the GPIO numbering has changed. Update the GPIO used
for nVBUS_DRV.
Longer term, we need a better abstraction of board-specific setup in
this code so we're not hard-coding board specific GPIOs into the
driver, bu
From: David Brownell
Update musb/davinci.c and Kconfig for the newish DM355 chips:
- Support new controls:
* PHY control bits for swapping D+/D- signals, OTG powerdown
* DRVVBUS control bits
- The DM355 EVM board swaps D+/D- for better signal integrity
- Use clk_enable()/clk_disable()
David Brownell writes:
> From: David Brownell
>
> Add basic driver for the MSP430 on the DM 365 EVM; it's used
> only to report commands from an IR remote. (This assumes the
> same remote used with other DaVinci EVM boards.)
>
> Signed-off-by: David Brownell
Thanks, pushed.
Kevin
> ---
> NO
David Brownell writes:
> From: David Brownell
>
> Support DM365 GPIOs ... primarily by handling non-banked GPIO IRQs:
>
> - Flag DM365 chips as using non-banked GPIO interrupts, using a
>new soc_info field.
>
> - Replace the gpio_to_irq() mapping logic. This now uses some
>runtime inf
From: Muralidharan Karicheri
Following updates to vpfe capture driver :-
1) Adding support for camera capture using mt9t031 driver
(A patch for mt9t031 is already sent for review)
2) Use v4l2_i2c_new_subdev_board() for loading sub devices
3) Fixed a bug in s_inp
From: Muralidharan Karicheri
Re-sending adding Hans to CC
Following updates to vpfe capture driver :-
1) Adding support for camera capture using mt9t031 driver
(A patch for mt9t031 is already sent for review)
2) Use v4l2_i2c_new_subdev_board() for loading sub devices
From: Muralidharan Karicheri
Following updates to ccdc driver :-
1) Adding support for camera capture using mt9t031
2) Changed default resolution for ycbcr capture to NTSC to match
with tvp514x driver.
3) Returns proper error code from ccdc_init (comments agains
From: Muralidharan Karicheri
Following are the changes:-
1) moved i2c board specific part to sub device configuration
structure so that sub device can be loaded from vpfe capture
using the new v4l2_i2c_new_subdev_board() api
2) adding mt9t031 sub device configurati
On Fri, Jun 26, 2009 at 05:09:12PM +0300, Yusuf Caglar AKYUZ wrote:
> Denys Dmytriyenko wrote:
> > On Fri, Jun 26, 2009 at 12:46:31AM +0300, Yusuf Caglar AKYUZ wrote:
> >> Karicheri, Muralidharan wrote:
> >>> We have been using the arago git tree and I don't see any of the issues
> >>> that you ar
31 matches
Mail list logo
