On Thursday 15 October 2009 01:09:04 Steve Ressler wrote:
Hi,
Hi,
Is your mail client sending html messages by default?
I'm trying to get my boot time down under 2 seconds. I have followed the
steps listed at
http://wiki.davincidsp.com/index.php?title=All_This_For_1_Second_Boot and
Activate CONFIG_PRINTK_TIME kernel option, so that you can see a nice
timing in front of all your printk. I don't know if it is available in MV 2.6.10
kernel, but it is in MV 2.6.18.
Initial ramdisk initialisation can take some times too.
Also consider that printk messages are printed when the
we have made our own custom board DM6446 with 256MB but when the kernel boots
up it is uanble to make the partions can anyone help me in resolving this
issue.Here is my bootup msg
Starting kernel ...
From: Sudhakar Rajashekhara sudhakar@ti.com
Currently DaVinci EDMA driver supports multiple EDMA channel
controller instances. edma_alloc_channel() api returns a 32
bit value which has the channel controller number in MSB and
the EDMA channel number in LSB. The variables which store the
Nori, Sekhar nsek...@ti.com writes:
On Fri, Oct 09, 2009 at 00:58:30, Kevin Hilman wrote:
Sergei Shtylyov sshtyl...@ru.mvista.com writes:
There have accumulated quite a lot of them after the code
reorganizations...
In several cases I had to replace #include linux/dma-mapping.h which
This series of patches provide support for the TVP7002 decoder in DM365.
Support
includes:
* Inclusion of the chip in v4l2 definitions
* Definition in board specific data structures
* Linking within the VPFE architecture
* Definition of TVP7002 specific data structures
* Kconfig and Makefile
From: Santiago Nunez-Corrales santiago.nu...@ridgerun.com
This patch adds support for TVP7002 in the DM365 VPFE inteface.
Added video modes.
Signed-off-by: Santiago Nunez-Corrales santiago.nu...@ridgerun.com
---
drivers/media/video/davinci/vpfe_capture.c |9 +
1 files changed, 9
From: Santiago Nunez-Corrales santiago.nu...@ridgerun.com
This patch provides required chip identification definitions
within v4l2. Removed HD and control defines.
Signed-off-by: Santiago Nunez-Corrales santiago.nu...@ridgerun.com
---
include/media/v4l2-chip-ident.h |6 ++
1 files
From: Santiago Nunez-Corrales santiago.nu...@ridgerun.com
This patch provides menu configuration options for the TVP7002
decoder driver in DM365.
Signed-off-by: Santiago Nunez-Corrales santiago.nu...@ridgerun.com
---
drivers/media/video/Kconfig | 32
From: Santiago Nunez-Corrales santiago.nu...@ridgerun.com
This patch provides support for TVP7002 in architecture definitions
within DM365.
Signed-off-by: Santiago Nunez-Corrales santiago.nu...@ridgerun.com
---
arch/arm/mach-davinci/board-dm365-evm.c | 170 ++-
1
From: Santiago Nunez-Corrales santiago.nu...@ridgerun.com
This patch provides the required definitions for the TVP7002 driver
in DM365.
Signed-off-by: Santiago Nunez-Corrales santiago.nu...@ridgerun.com
---
drivers/media/video/tvp7002_reg.h | 150 +
From: Santiago Nunez-Corrales santiago.nu...@ridgerun.com
This patch provides the implementation of the TVP7002 decoder
driver for DM365.
Signed-off-by: Santiago Nunez-Corrales santiago.nu...@ridgerun.com
---
drivers/media/video/tvp7002.c | 1585 +
1
Sekhar Nori nsek...@ti.com writes:
This patch fixes the following warning seen when building with default
config:
arch/arm/mach-davinci/board-da830-evm.c:371: warning: 'da830_evm_devices'
defined but not used
Tested on DA830 EVM with and without CONFIG_DA830_UI_NAND enabled.
Sekhar Nori nsek...@ti.com writes:
Remove ifdefs inside da830_evm_init function since they are
discouraged in Documentation/SubmittingPatches section 2.2
Use the method outlined in that document for fixing it.
Tested on DA830 EVM.
Signed-off-by: Sekhar Nori nsek...@ti.com
Thanks, pushing
Sekhar Nori nsek...@ti.com writes:
This patch supports runtime detection of DA830 UI card and
eliminates the need for DA830_UI config option. Successful
probe of GPIO expander present on the UI card is used to
detect its presence. For this reason, GPIO_PCF857X is auto-
selected when DA830
This patch series re-structures DaVinci USB initialization and configuration
infrastructure. In DaVinci devices both VBUS control and PHY modules
reside external to MUSB module and their implementation is device dependant.
VBUS and PHY control implementation has been moved to board,
platform
This patch implements the support for USB VBUS, PHY control, DM644x USB memory
maps, IRQ, USB Mode. It initializes for a single instance of MUSB controller.
Signed-off-by: Swaminathan S swami.i...@ti.com
---
arch/arm/mach-davinci/board-dm644x-evm.c| 46 +-
This patch implments the support for USB VBUS, PHY control, DM646x
USB memory map, IRQ, USB Mode. It initializes for a single instance
of MUSB controller.
Signed-off-by: Ravi B ravib...@ti.com
---
arch/arm/mach-davinci/board-dm646x-evm.c| 72 +
This patch implements the generic DaVinci platform USB configuration
infrastructure. Re-structure's usb.c to subscribe for plaform resources for
the configured instances of controller. Adds phy_config data member in musb.h
to enable generic conrol of platform specific USB PHY functionality.
Updating the Leopard board USB configuration to align with new DaVinci USB
platform infrastructure.
Signed-off-by: Swaminathan S swami.i...@ti.com
---
arch/arm/mach-davinci/board-dm355-leopard.c | 18 +-
1 files changed, 17 insertions(+), 1 deletions(-)
diff --git
Chaithrika U S chaithr...@ti.com writes:
Add cpufreq support to MMC driver. The clock dividervalue has to be
modified according to the controller input frequency.
Signed-off-by: Chaithrika U S chaithr...@ti.com
---
This patch applies to DaVinci GIT tree as the driver is not yet present in
Updating the DM355 USB platform implementation to subscribe to the new
DaVinci USB infrastructure.
Signed-off-by: Swaminathan S swami.i...@ti.com
---
arch/arm/mach-davinci/board-dm355-evm.c| 28 ++-
arch/arm/mach-davinci/dm355.c | 75
This patch re-structures davinci.c file to use the USB VBUS, PHY controls from
platform specific implementation. All DaVinci related platform dependancies
w.r.t USB VBUS, PHY controls have been moved out of this file into arch/arm/
mach-davinci paltform specific implementation.
Signed-off-by:
Updating the SFFSDR board USB configuration to aling with the new DaVinci USB
configuration infrastructure. Based on current implementation initialize the
MUSB config to support Peripheral mode alone configuration.
Signed-off-by: Swaminathan S swami.i...@ti.com
---
Chaithrika U S chaithr...@ti.com writes:
In the McASP clock definition add a flag to indicate that the peripheral clock
belongs to ASYNC3 clock domain.
Signed-off-by: Chaithrika U S chaithr...@ti.com
Thanks, pushing today, and queuing in for-next.
Kevin
---
arch/arm/mach-davinci/da850.c
Hi Kevin,
2009/10/10 liukun.kevin liukun.ke...@gmail.com:
Who can tell me
where to get RTSC Codec Package Wizard and RTSC Server Package Wizard ?
I have a 1.10 dvevm and a 1.20 dvevm. Neither of them has the ceutils.
And I cannot open the address
On Thursday 15 October 2009 16:42:52 santiago.nu...@ridgerun.com wrote:
From: Santiago Nunez-Corrales santiago.nu...@ridgerun.com
This patch provides required chip identification definitions
within v4l2. Removed HD and control defines.
Signed-off-by: Santiago Nunez-Corrales
From: Santiago Nunez-Corrales santiago.nu...@ridgerun.com
This patch provides menu configuration options for the TVP7002
decoder driver in DM365.
Signed-off-by: Santiago Nunez-Corrales santiago.nu...@ridgerun.com
---
drivers/media/video/Kconfig | 32
From: Santiago Nunez-Corrales santiago.nu...@ridgerun.com
This patch provides required chip identification definitions
within v4l2. Changed order of THS7353.
Signed-off-by: Santiago Nunez-Corrales santiago.nu...@ridgerun.com
---
include/media/v4l2-chip-ident.h |9 +
1 files changed,
On Thursday 15 October 2009 16:43:54 santiago.nu...@ridgerun.com wrote:
From: Santiago Nunez-Corrales santiago.nu...@ridgerun.com
This patch provides the implementation of the TVP7002 decoder
driver for DM365.
Signed-off-by: Santiago Nunez-Corrales santiago.nu...@ridgerun.com
---
Jayakrishnan,
Please check this:
http://wiki.davincidsp.com/index.php/Troubleshooting_DSPLink_configuration_issues#Problem:_PROC_attach_failed_with_DSP_EALREADYCONNECTED_error
Thanks and Regards,
Deepali Uppal
DSP/BIOS Link
Platform Support Products
-Original Message-
From:
Swaminathan S swami.i...@ti.com writes:
This patch series re-structures DaVinci USB initialization and configuration
infrastructure. In DaVinci devices both VBUS control and PHY modules
reside external to MUSB module and their implementation is device dependant.
Hi Swami,
What tree does
Swaminathan S swami.i...@ti.com writes:
This patch implements the support for USB VBUS, PHY control, DM644x USB memory
maps, IRQ, USB Mode. It initializes for a single instance of MUSB controller.
Signed-off-by: Swaminathan S swami.i...@ti.com
A couple minor comments below...
---
santiago.nu...@ridgerun.com writes:
From: Santiago Nunez-Corrales santiago.nu...@ridgerun.com
This patch provides support for TVP7002 in architecture definitions
within DM365.
Signed-off-by: Santiago Nunez-Corrales santiago.nu...@ridgerun.com
---
arch/arm/mach-davinci/board-dm365-evm.c |
Hemant Pedanekar hema...@ti.com writes:
Note that configuration option CONFIG_DAVINCI_RESET_CLOCKS should _not_ be
selected if kernel is being built for DM646x PCI target. Slecting this option
will disable the PCI PSC during kernel boot, thus preventing any access to PCI
backend configuration
I will be out of the office starting 16-10-2009 and will not return until
17-10-2009.
I will respond to your message when I return.
__
This email has been scanned by the MessageLabs Email Security System.
For more information
Hemant Pedanekar hema...@ti.com writes:
The driver code is organized in two parts, DM646x specific part and 'generic'
part which could be easily adopted on other platform/SoCs having same PCI core
as in DM6467.
First of all, sorry for the *huge* delay in reviewing this series.
It's been 2
I would like to ask if DM365's Red Color output is not perform so well?
There are 2 ISPs to compare.
1 is DM365 , 2 is made by FPGA.
They connect to the same input (lens and sensor) , the same output (TV).
And of course , parameter setup is the same.
( Sensor: same analog gain , shutter ,
Hemant Pedanekar hema...@ti.com writes:
Performs pinmux and gpio handling for switching to PCI mode on EVMs with
workaround as described on
http://wiki.davincidsp.com/index.php/Pinmux_Switching_from_NAND_to_PCI. Skips
setting pinmux if already set (e.g., by hardware).
Signed-off-by: Hemant
Hemant Pedanekar hema...@ti.com writes:
[...]
--- a/arch/arm/mach-davinci/Makefile
+++ b/arch/arm/mach-davinci/Makefile
@@ -8,6 +8,7 @@ obj-y := time.o clock.o serial.o io.o
psc.o \
gpio.o dma.o usb.o common.o sram.o
neilsi...@ti.com writes:
From: Neil Sikka neilsi...@ti.com
This has platform and board setup changes to support the vpfe capture
driver for DM365 EVMs.
Reviewed-by: Muralidharan Karicheri m-kariche...@ti.com
Mandatory-Reviewer: Hans Verkuil hverk...@xs4all.nl
Mandatory-Reviewer: Kevin
Hello
I want to make a device that communicates with davinci through VLYNQ
but I don't really know how VLYNQ works, specially how the link is
stablished.
SPRUE36.pdf seems to have an incomplete VLYNQ protocol specification.
Thanks,
___
A good reference code would be any 1.6x DSPLink release (you can look at the
latest - 1.63:
https://www-a.ti.com/downloads/sds_support/targetcontent/link/index.html)
We support a connection between DRX416 ARM and DM6437 over VLYNQ in these
versions.
Regards,
Mugdha
-Original
43 matches
Mail list logo
