sample dsplink appl.
Hi all, I am working on DM6446 based custom board. The dsplink module is inserted properly in to the kernel. To verify the dsplink in my board, I ran the test application provided with the dsplink source. my dsplink node is created properly, i am using montavista package of dvevm board. when i run the application, i got the following error message, ./messagegpp message.out 1 == Sample Application : MESSAGE == Entered MESSAGE_Create () Leaving MESSAGE_Create () Entered MESSAGE_Execute () ERROR! Data integrity check failed Leaving MESSAGE_Execute () Entered MESSAGE_Delete () Leaving MESSAGE_Delete () since this is a sample application that comes along with the dsplink source, many would have been already familiar with this code. Since I am not much familiar with this dsplink, please guide me where I would suspect the problem.___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: How to debug Codec server: cannot open .pjt in CCS
Brad, you're absolutely right. There's no need to open the .pjt, it just works fine opening the source files and loading the symbols. Now I'm able to debug my code, I must have been doing it in the wrong order. Thank you very much indeed, Jon Griffis, Brad escribió: When you set the breakpoint you'll either get a filled-in red circle, or just an empty circle. If it's filled-in with red then CCS understands where you're trying to set the breakpoint. There are file names embedded in the x64P file along with the symbols, etc. One thing to be careful about is the order you're doing things. You need to make sure that the ARM loads the DSP *before* you set the breakpoint. Alternatively, right-click and select toggle hardware breakpoint. Otherwise the software breakpoint might actually be overwritten by the ARM loading the code and so you'd never halt. I don't think you ever need to open a project at all. You just need to load the symbols. Brad -Original Message- From: davinci-linux-open-source-boun...@linux.davincidsp.com [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of Jon Arróspide Sent: Friday, February 20, 2009 4:23 AM To: davinci-linux-open-source@linux.davincidsp.com Subject: How to debug Codec server: cannot open .pjt in CCS Hello all, I'm trying to debug a codec server in CCS. I'm working with DM6446. I'm following the steps of the wiki, (http://wiki.davincidsp.com/index.php?title=Debugging_the_DSP_side_of_a_CE _application_on_DaVinci_using_CCS), in order to debug the codec server. I already have the application (example 'scale' from CE) running on the ARM side, and I have opened and connected the CCS, and loaded the .x64P, but my question is, how do I insert the breakpoints? If I just open the source files as the wiki says, and insert these there, they are not hit. I've read in other posts that it is necessary to open in CCS the project .pjt generated in the server package folder, but if I try to open it, I get the following error: No build tools for the target specified in this project were found. Cannot open project ...\servers.gti.scale.pjt. Please use Component Manager to ensure the appropriate project server and build tools are selected Checking the Component Manager, I do have indeed those build tools for c6000. If I open the .pjt file it looks like this: ; Code Composer Project File, Version 2.0 (do not modify or remove this line) [Project Settings] ProjectName=servers.gti.scale ProjectType=External CPUFamily=TMS320C64PXX Tool=CustomBuilder Config=Package [Source Files] Source=../main.c So, I don't know if I can do something to open this project, or if there is another way to set the breakpoints in the source files. Basically, I guess my doubt is the following: when loading the symbols of the .x64P file, how is the link done to the source files that generated it? How can I access those files in order to set the breakpoints? Please somebody help me out on how to debug codec servers in CCS, I think I'm missing something in the way... Thank you in advance, Jon ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: sample dsplink appl.
Ramesh, What bootargs are you using? Are you reserving memory from Linux for DSPLink shared memory using mem= command? http://tiexpressdsp.com/wiki/index.php?title=Changing_DSPLink_Memory_Map Regards, Mugdha From: davinci-linux-open-source-bounces+mugdha=ti@linux.davincidsp.com [mailto:davinci-linux-open-source-bounces+mugdha=ti@linux.davincidsp.com] On Behalf Of Ramesh Chandra Sent: Monday, February 23, 2009 2:12 PM To: davinci-linux-open-source@linux.davincidsp.com Subject: sample dsplink appl. Hi all, I am working on DM6446 based custom board. The dsplink module is inserted properly in to the kernel. To verify the dsplink in my board, I ran the test application provided with the dsplink source. my dsplink node is created properly, i am using montavista package of dvevm board. when i run the application, i got the following error message, ./messagegpp message.out 1 == Sample Application : MESSAGE == Entered MESSAGE_Create () Leaving MESSAGE_Create () Entered MESSAGE_Execute () ERROR! Data integrity check failed Leaving MESSAGE_Execute () Entered MESSAGE_Delete () Leaving MESSAGE_Delete () since this is a sample application that comes along with the dsplink source, many would have been already familiar with this code. Since I am not much familiar with this dsplink, please guide me where I would suspect the problem. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
can anyone test mt9t001 ok in dm355?
Dear all:
We used a FPGA which just like a CMOS Sensor for inputing raw datas to dm355,So
I want to test device_type mt9t001 on dm355 evm to verify the driver whick
capture raw data is ok. I have modify the demos encodedecode program source to
support mt9t001 for test.
..
/* Use either NTSC or PAL depending on display kernel parameter */
//std = V4L2_STD_PAL;//gblGetYFactor() == NTSCSTD ? V4L2_STD_NTSC :
V4L2_STD_PAL;
std = V4L2_STD_MT9T001_VGA_30FPS; //edit by duke 2009.2.17
if(ioctl(fd, VIDIOC_S_STD, std) == -1) {
PTRACE(LOG_ERR,VIDIOC_S_STD failed on %s (%s)\n, V4L2_DEVICE,
strerror(errno));
return FAILURE;
}
/* Set the video capture image format */
CLEAR(fmt);
fmt.type= V4L2_BUF_TYPE_VIDEO_CAPTURE;
fmt.fmt.pix.width = VGA_WIDTH;
fmt.fmt.pix.height = VGA_HEIGHT;
fmt.fmt.pix.pixelformat = V4L2_PIX_FMT_SBGGR8;//V4L2_PIX_FMT_UYVY;edit by
duke 2009.2.23
fmt.fmt.pix.field = V4L2_FIELD_INTERLACED;
/* Set the video capture format */
if (ioctl(fd, VIDIOC_S_FMT, fmt) == -1) {
PTRACE(LOG_ERR,VIDIOC_S_FMT failed on %s (%s)\n, V4L2_DEVICE,
strerror(errno));
return FAILURE;
}
.
and i haved set bootargs .for example:
setenv bootargs mem=116M console=ttyS0,115200n8 root=/dev/mtdblock3 rw
rootfstype=yaffs2 ip=dhcp
davinci_capture.device_type=0
video=davincifb:vid0=720x576x16,2500K:vid1=720x576x16,2500K:osd0=720x576x16,2025K
davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=$(videostd)
the the programer can run ok,but it cann't capture data!!
Is it hardware problem or soft problem?
I thinks dm355 only suport cvbs or svideo input,so how can i input raw datas
to mt9t001 for test in dm355 evm?
thanks all!
2009-02-23
zuowenping
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
TI DM357 H.264 format
Dear all we are working on H.264 video streaming using DM357 for video encoding. We are not sure that how many NALs and which ones constitute a complete video frame or gives us an encoded H264 frame from the DM357 output. In other words, we don't know the exact format of the encoded H.264 content from DM357. Could somebody help please? Thanks in advances. Sheldon _ Check out the new and improved services from Windows Live. Learn more! http://clk.atdmt.com/UKM/go/132630768/direct/01/___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
USB host Issue: scsi command abort
Hi,
I'm currently testing the USB host driver in DMA mode and I encounter some
issues with the use of simultaneous transfer on a MSC USB key(Common key with
no hub inside) and a WIFI dongle RT73.
My test case is the following:
- I download in WIFI mode a large amount of data which I stored on USB MSC.
- In the mean while, I try to read this data stored on the same MSC key.
After a certain time(~5minutes), I encounter a command abort in scsi glue
coming from the hub. It seems that the USB MSC key is unlinked.
I would like to know if anybody has already encounter this problem with the
last MUSB driver and also if anybody can help me to understand this abortion.
Thank you very much.
Stéphane Cerveau
-Original Message-
From: Sergei Shtylyov [mailto:sshtyl...@ru.mvista.com]
Sent: vendredi 20 février 2009 21:35
To: felipe.ba...@nokia.com; gre...@suse.de; davi...@pacbell.net
Cc: davinci-linux-open-source@linux.davincidsp.com; linux-...@vger.kernel.org
Subject: [PATCH 2/2] musb_host: fix isochronous Tx DMA
Multi-frame isochronous Tx URBs transfers in DMA mode never complete because
musb_host_tx() just doesn't restart DMA on a second frame, only emitting debug
message instead. In order to amend that, we need to factor out programming the
DMA transfer from musb_ep_program() into musb_tx_dma_program() (dropping bogus
REVISIT comment on the CPPI/TUSB DMA failure path), reorder the code at the end
of musb_host_tx() to facilitate the fallback to PIO iff DMA fails (dropping the
useless label, while at it), and add a variable to handle the buffer offset
consistently for both PIO and DMA modes. We also need to add an argument to
musb_ep_program() for the same reason (it only worked correctly with non-zero
offset of the first frame in PIO mode). Also, set the completed isochronous
frame descriptor's 'actual_length' and 'status' fields correctly in DMA mode
(in fact, the latter didn't get set at all).
Oh, and also CPPI reportedly doesn't like sending isochronous packets in the
RNDIS mode, so change the criterion for this mode to be used only on multi-
packet sends (in the single-packet case using it didn't make sense anyway)...
Signed-off-by: Pavel Kiryukhin pkiryuk...@ru.mvista.com
Signed-off-by: Sergei Shtylyov sshtyl...@ru.mvista.com
---
The patch is against the recent Linus' kernel, atop of the previosly sent patch
series; it requires the previosly posted patch to be applied too. It has only
been tested with CPPI 3.0/4.1 DMA drivers, and needs to be verified with other
DMA drivers...
drivers/usb/musb/cppi_dma.c |1
drivers/usb/musb/musb_host.c | 237 +++
2 files changed, 107 insertions(+), 131 deletions(-)
Index: linux-2.6/drivers/usb/musb/cppi_dma.c
===
--- linux-2.6.orig/drivers/usb/musb/cppi_dma.c
+++ linux-2.6/drivers/usb/musb/cppi_dma.c
@@ -579,6 +579,7 @@ cppi_next_tx_segment(struct musb *musb,
* trigger the send a ZLP? confusion.
*/
rndis = (maxpacket 0x3f) == 0
+length maxpacket
length 0x
(length % maxpacket) != 0;
Index: linux-2.6/drivers/usb/musb/musb_host.c
===
--- linux-2.6.orig/drivers/usb/musb/musb_host.c
+++ linux-2.6/drivers/usb/musb/musb_host.c
@@ -102,9 +102,8 @@
*/
-static void musb_ep_program(struct musb *musb, u8 epnum,
- struct urb *urb, unsigned int nOut,
- u8 *buf, u32 len);
+static void musb_ep_program(struct musb *musb, u8 epnum, struct urb *urb,
+ int is_out, u8 *buf, u32 ofs, u32 len);
/*
* Clear TX fifo. Needed to avoid BABBLE errors.
@@ -174,10 +173,10 @@ static void
musb_start_urb(struct musb *musb, int is_in, struct musb_qh *qh)
{
u16 frame;
- u32 len;
- void*buf;
+ u32 len, ofs = 0;
void __iomem*mbase = musb-mregs;
struct urb *urb = next_urb(qh);
+ void*buf = urb-transfer_buffer;
struct musb_hw_ep *hw_ep = qh-hw_ep;
unsignedpipe = urb-pipe;
u8 address = usb_pipedevice(pipe);
@@ -200,11 +199,10 @@ musb_start_urb(struct musb *musb, int is
case USB_ENDPOINT_XFER_ISOC:
qh-iso_idx = 0;
qh-frame = 0;
- buf = urb-transfer_buffer + urb-iso_frame_desc[0].offset;
+ ofs = urb-iso_frame_desc[0].offset;
len = urb-iso_frame_desc[0].length;
break;
default:/* bulk, interrupt */
- buf = urb-transfer_buffer;
len = urb-transfer_buffer_length;
}
@@ -217,14 +215,14 @@ musb_start_urb(struct musb *musb, int is
case
DM6446 Ethernet MAC performance
Hi to all, I've tested Linux kernel 2.6.29-rc4-davinci1 (http://git.kernel.org/?p=linux/kernel/git/khilman/linux-davinci.git;a=commit;h=582ad6bcceb7c8f0c828e71e810fd40fed7af6c3) for Ethernet performance. Kernel was compiled was done by CodeSourcery 2008q3 (gcc 4.3.2) using davinci_evm_dm644x_defconfig. After booting, iperf v2.0.4 was run on the target (DVEVM board) and on the host PC (Ubuntu 8.04) for ten seconds (using default settings): target - target (over localhost): 190Mbit/s host (connecting to) - target: 31Mbit/s target (connecting to) - host: 71Mbit/s Do the values above make sense? Can anyone confirm them? Thanks in advance. P.S. When running the same test on 2.6.28-rc6 (from http://git.kernel.org/?p=linux/kernel/git/khilman/linux-davinci.git), before PHY was refactored out from davinci_emac, the results were better: host (connecting to) - target: 73Mbit/s target (connecting to) - host: 57Mbit/s ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: DM6467 - Encoding in 1080i with DMAI
Hi Marcelo Guedes,
Change the source code of capture.c as shown below to make encoder of
DM6467 demo working for 1080I as shown below and compile it.
/* Calculate the dimensions of a video standard given a color space */
#if RES_720
if (BufferGfx_calcDimensions(VideoStd_720P_60,ColorSpace_YUV422PSEMI,
gfxAttrs.dim) 0) {
#else
if (BufferGfx_calcDimensions(VideoStd_1080I_30, ColorSpace_YUV422PSEMI,
gfxAttrs.dim) 0) {
#endif
ERR(Failed to calculate Buffer dimensions\n);
cleanup(THREAD_FAILURE);
}
/* Calculate buffer size needed of a video standard given a color space
*/
#if RES_720
bufSize = BufferGfx_calcSize(VideoStd_720P_60, ColorSpace_YUV422PSEMI);
#else
bufSize = BufferGfx_calcSize(VideoStd_1080I_30, ColorSpace_YUV422PSEMI);
#endif
if (bufSize 0) {
ERR(Failed to calculate size for capture driver buffers\n);
cleanup(THREAD_FAILURE);
}
/* Create a table of buffers to use with the device drivers */
gfxAttrs.colorSpace = ColorSpace_YUV422PSEMI;
hBufTab = BufTab_create(NUM_DRIVER_BUFS, bufSize,
BufferGfx_getBufferAttrs(gfxAttrs));
if (hBufTab == NULL) {
ERR(Failed to allocate contiguous buffers\n);
cleanup(THREAD_FAILURE);
}
/* Create capture device driver instance */
cAttrs.numBufs = NUM_CAPTURE_BUFS;
hCapture = Capture_create(hBufTab, cAttrs);
if (hCapture == NULL) {
ERR(Failed to create capture device,
720P component input connected?\n);
cleanup(THREAD_FAILURE);
}
videoStd = Capture_getVideoStd(hCapture);
/* We only support 720P capture */
#if RES_720
if (videoStd != VideoStd_720P_50 videoStd != VideoStd_720P_60) {
#else
if (videoStd != VideoStd_1080I_30 videoStd != VideoStd_1080P_30) {
#endif
ERR(Need 720P composite input to this demo\n);
cleanup(THREAD_FAILURE);
}
Then you should change the memory configuration of the encoder to work for
1080I. So please change the loadmodules.sh script as shown below before
running the encode demo.
# insert cmemk, tell it to occupy physical 120MB-200MB and create enough
# contiguous buffers for the worst case requirements of the demos.
rmmod cmemk.ko
# one times 4MB, 10 times 3.5 MB,10 times 1.5MB etc
#insmod cmemk.ko phys_start=0x8780 phys_end=0x8ba0
pools=1x4147200,10x3458400,10x1434240,11x663552,4x6
# 10 times 4MB, 1 times 3.5 MB,10 times 1.5MB etc
insmod cmemk.ko phys_start=0x8780 phys_end=0x8ba0
pools=10x4147200,1x3458400,10x1434240,11x663552,4x6
# insert dsplinkk, tell it that DSP's DDR is at physical 250MB-254MB
rmmod dsplinkk.ko
insmod dsplinkk.ko
# alter dma queue mapping for better visual performance
if [ -f mapdmaq-hd ]
then
./mapdmaq-hd
fi
# make /dev/dsplink
rm -f /dev/dsplink
mknod /dev/dsplink c `awk \\$2==\dsplink\ {print \\$1} /proc/devices` 0
This should make it working for 1080.
Currently the encoder will not encode at 30 frames persecond. I do not
remember exactly how many frames per second it can encode.
Regards,
Mahendra kumar
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
davinci audio: spin_idle
Hi all, I am trying to use the spin_idle option in the davinci audio drivers. I use the montavista LSP1 kernel. I notice that after the zeros are DMA'ed(spin mode), an echo effect is heard in the audio. Has anyone managed to get it working correctly? There is a function call davinci_clear_dma which is commented in the driver. I can not find this anywhere. Is this required for it work correctly? Any help is appreciated. Thanks. Regards, Pradeep Sriram ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: USB host Issue: scsi command abort
Ajay, Do you know where can I find the last official version of musb driver where the two patch, you sent me, are integrated. It seems that my driver misses a lot of patches. Thank you very much for your precious help. Stephane -Original Message- From: Gupta, Ajay Kumar [mailto:ajay.gu...@ti.com] Sent: lundi 23 février 2009 12:58 To: Stephane Cerveau; Sergei Shtylyov; felipe.ba...@nokia.com; gre...@suse.de; davi...@pacbell.net Cc: davinci-linux-open-source@linux.davincidsp.com; linux-...@vger.kernel.org Subject: RE: USB host Issue: scsi command abort -Original Message- From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-ow...@vger.kernel.org] On Behalf Of Stephane Cerveau Sent: Monday, February 23, 2009 5:03 PM To: Sergei Shtylyov; felipe.ba...@nokia.com; gre...@suse.de; davi...@pacbell.net Cc: davinci-linux-open-source@linux.davincidsp.com; linux-...@vger.kernel.org Subject: USB host Issue: scsi command abort Hi, I'm currently testing the USB host driver in DMA mode and I encounter some issues with the use of simultaneous transfer on a MSC USB key(Common key with no hub inside) and a WIFI dongle RT73. My test case is the following: - I download in WIFI mode a large amount of data which I stored on USB MSC. - In the mean while, I try to read this data stored on the same MSC key. After a certain time(~5minutes), I encounter a command abort in scsi glue coming from the hub. It seems that the USB MSC key is unlinked. How many endpoints are supported in your musb platform? I think it is issue when all bulk is going to one endpoint (bulk-mux). You may try below two patches. [1] http://marc.info/?l=linux-usbm=123393008601134w=2 [2] http://marc.info/?l=linux-usbm=123393015101594w=2 Regards, Ajay I would like to know if anybody has already encounter this problem with the last MUSB driver and also if anybody can help me to understand this abortion. Thank you very much. Stéphane Cerveau -Original Message- From: Sergei Shtylyov [mailto:sshtyl...@ru.mvista.com] Sent: vendredi 20 février 2009 21:35 To: felipe.ba...@nokia.com; gre...@suse.de; davi...@pacbell.net Cc: davinci-linux-open-source@linux.davincidsp.com; linux-...@vger.kernel.org Subject: [PATCH 2/2] musb_host: fix isochronous Tx DMA Multi-frame isochronous Tx URBs transfers in DMA mode never complete because musb_host_tx() just doesn't restart DMA on a second frame, only emitting debug message instead. In order to amend that, we need to factor out programming the DMA transfer from musb_ep_program() into musb_tx_dma_program() (dropping bogus REVISIT comment on the CPPI/TUSB DMA failure path), reorder the code at the end of musb_host_tx() to facilitate the fallback to PIO iff DMA fails (dropping the useless label, while at it), and add a variable to handle the buffer offset consistently for both PIO and DMA modes. We also need to add an argument to musb_ep_program() for the same reason (it only worked correctly with non-zero offset of the first frame in PIO mode). Also, set the completed isochronous frame descriptor's 'actual_length' and 'status' fields correctly in DMA mode (in fact, the latter didn't get set at all). Oh, and also CPPI reportedly doesn't like sending isochronous packets in the RNDIS mode, so change the criterion for this mode to be used only on multi- packet sends (in the single-packet case using it didn't make sense anyway)... Signed-off-by: Pavel Kiryukhin pkiryuk...@ru.mvista.com Signed-off-by: Sergei Shtylyov sshtyl...@ru.mvista.com --- The patch is against the recent Linus' kernel, atop of the previosly sent patch series; it requires the previosly posted patch to be applied too. It has only been tested with CPPI 3.0/4.1 DMA drivers, and needs to be verified with other DMA drivers... drivers/usb/musb/cppi_dma.c |1 drivers/usb/musb/musb_host.c | 237 +++ 2 files changed, 107 insertions(+), 131 deletions(-) Index: linux-2.6/drivers/usb/musb/cppi_dma.c === --- linux-2.6.orig/drivers/usb/musb/cppi_dma.c +++ linux-2.6/drivers/usb/musb/cppi_dma.c @@ -579,6 +579,7 @@ cppi_next_tx_segment(struct musb *musb, * trigger the send a ZLP? confusion. */ rndis = (maxpacket 0x3f) == 0 + length maxpacket length 0x (length % maxpacket) != 0; Index: linux-2.6/drivers/usb/musb/musb_host.c === --- linux-2.6.orig/drivers/usb/musb/musb_host.c +++ linux-2.6/drivers/usb/musb/musb_host.c @@ -102,9 +102,8 @@ */ -static void musb_ep_program(struct musb *musb, u8 epnum, - struct urb *urb, unsigned int nOut, - u8 *buf, u32 len); +static void musb_ep_program(struct musb *musb, u8 epnum, struct urb *urb, + int
Re: The problem of VGA display using ths8200 in dm355 platform
This sounds like banding. Banding can happen when you either convert from one color space to another or convert from a higher bits-per- pixel to a lower one. What format is you source image? - Brad On Feb 22, 2009, at 8:27 PM, Lori Gao wrote: Dear all; I am using ths8200 to display video and pic on PC monitor. There is contour effect on the screen especially on quite smooth and shiny object, in another word, there is color gradation loss. I wonder what had happened and who can give me some advice or help? Thanks, Best Regards. Lori Gao RD center(Shanghai) Rayco (Shanghai) Medical Products Company Limited Carestream Health Inc.___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
CHASE KIM/KR/AEKL/AAP is out of the office.
I will be out of the office starting 2009-02-23 and will not return until 2009-02-27. I will respond to your message when I return. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: USB host Issue: scsi command abort
On Monday 23 February 2009, Stephane Cerveau wrote: Do you know where can I find the last official version of musb driver where the two patch, you sent me, are integrated. They're not yet merged in any kernel I know of, outside of (presumably) TI development trees. Those two patches are candidates for 2.6.30 merge, pending review and testing ... if they resolve this problem for you, please tell us. Confirmation that a patch works will help that process. It seems that my driver misses a lot of patches. The current plan is to integrate through mainline, and maybe pre-merge patches queued for the next merge window into the DaVinci (or OMAP) trees. One way to look at that is aiming to have the MM or -next staging trees work for DaVinci (or OMAP) in the normal way. We want to get away from having DaVinci-specific patches languish in the DaVinci tree ... ditto the OMAP tree. Specific to DaVinci there are a few patches that can't yet queue to mainline, since they depend on support for new SoC chips (notably DM355) which hasn't yet been queued for mainline merge yet. I recently signed off on ten low-risk patches that I hope will be merged for 2.6.29-final ... and have about as many (including the two Ajay noted) which would be candidates for 2.6.30 (some are shoo-ins, others not). - Dave ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: [PATCH/RFC 1/2] davinci: clkdev: convert to new clkdev infrastructure
On Wednesday 11 February 2009, Kevin Hilman wrote: arch/arm/Kconfig | 1 + arch/arm/mach-davinci/clock.c | 39 ++- arch/arm/mach-davinci/clock.h | 15 + arch/arm/mach-davinci/devices.c | 4 - arch/arm/mach-davinci/dm355.c | 90 +- arch/arm/mach-davinci/dm644x.c | 87 + arch/arm/mach-davinci/dm646x.c | 67 +++- arch/arm/mach-davinci/include/mach/clkdev.h | 13 arch/arm/mach-davinci/include/mach/clock.h | 1 - arch/arm/mach-davinci/time.c | 17 +++-- drivers/i2c/busses/i2c-davinci.c | 2 +- drivers/mmc/host/davinci_mmc.c | 2 +- drivers/net/davinci_emac.c | 2 +- drivers/watchdog/davinci_wdt.c | 2 +- sound/soc/davinci/davinci-i2s.c | 6 +-- 15 files changed, 192 insertions(+), 156 deletions(-) create mode 100644 arch/arm/mach-davinci/include/mach/clkdev.h FWIW ... booted on dm6446 evm, given that second patch. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
DMAI Based GStreamer Audio Video Synchronisation?
Hello ! I am running the DMAI based gstreamer plugins r110. When I play the following file, http://www.disney.co.uk/junglebook/podcast/TrustInMe_iPod.mp4 The Audio Video synchronization is missing. Can someone give me some pointers on which areas of code to lookin, since I am not very familiar with audio video synchronization and playback mechanisms in general. thanks in advance regards -Nitin Mahajan --- On Mon, 23/2/09, Diego Dompe diego.do...@ridgerun.com wrote: From: Diego Dompe diego.do...@ridgerun.com Subject: Re: How to run DMAI Based GStreamer ? To: zhenfeng ren 1985re...@gmail.com Cc: davinci-linux-open-source@linux.davincidsp.com davinci-linux-open-source@linux.davincidsp.com Date: Monday, 23 February, 2009, 12:37 AM Hi, Gstreamer is compiled successfully except plugin mad(libid3tag.so.0 cannot find one symbol). I try many avi files, and I failed all. The video and audio files in DVEVM 1.10 cannot be played ,too. What pipelines are you trying? Without that information is hard to tell what is going wrong Can anyone give me an example how to use this gstreamer ? Or is there a commom video files used for testing? If you installed the system properly, there should be a directory with example scripts in /opt/gstreamer... Diego Dompe RidgeRun Engineering ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source New Email addresses available on Yahoo! Get the Email name you#39;ve always wanted on the new @ymail and @rocketmail. Hurry before someone else does! http://mail.promotions.yahoo.com/newdomains/aa/ ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: DMAI Based GStreamer Audio Video Synchronisation?
Nitin Mahajan wrote: Hello ! I am running the DMAI based gstreamer plugins r110. When I play the following file, http://www.disney.co.uk/junglebook/podcast/TrustInMe_iPod.mp4 The Audio Video synchronization is missing. Can someone give me some pointers on which areas of code to lookin, since I am not very familiar with audio video synchronization and playback mechanisms in general. can you confirm that this file play with good sync on the PC using the same version of gstreamer? ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
[EDMA help required] DM6446: From AEMIF to DDR memory
Hi all,
I need some help in EDMA transfer from AEMIF to DDR memory on DM6446.
Details:
I have a FPGA(16 bit interface) connected to AEMIF(CS4). I have to read
5 times, 500 words(16bit) each from my application. I have written a small char
driver
to do the DMA read operation.
Problem:
DMA transfer is done for first 500 words and from next time onwards DMA
transfer will miss
the data in chunks ok 16 or 32 words. i.e say I have application code -
/**application code **/
- Open the device then
for(i=0;i5;i++)
{
read(fd, buff, 500*2); //DMA read call
Print the buffer
}
memcpy to global buffer and send to host PC via USB
//
For i = 0; I will get the data from FPGA correctly, from i=1 onwards, data will
be missed not entire 500words but in chunks of 16/32 words
As I have also registered the callback, I am getting completion interrupt for
the everytime!
/*Configurations and driver code*/
#define FIFO 0x0600;
unsigned short *psr = (unsigned short *)FIFO;
unsigned short *pdt = NULL;
unsigned short *pdtPhy = NULL;
acnt = 2; (16bit)
bcnt = 500;
ccnt = 1;
Device_read(...)
{
pdt = (uint16_t*) kmalloc(500*2, GFP_KERNEL);
pdtPhy = virt_to_phys(pdt);
// initialise DMA
if (davinci_request_dma(0, DMATEST, davinci_edma_cb, NULL, ch,
tcc, EVENTQ_0))
{
return -1;
}
// set DMA parameters
davinci_set_dma_dest_params(ch, pdtPhy, INCR, 0);
davinci_set_dma_src_params(ch, psr, INCR, 0);
davinci_set_dma_src_index(ch, 0, 0); // args: srcbidx srccidx
davinci_set_dma_dest_index(ch, acnt, 0); // args: destbidx,
destcidx
davinci_set_dma_transfer_params(ch, acnt, bcnt, ccnt, 0, ABSYNC);
// args: acnt, bcnt, ccnt, bcntrld, sync_mode
// start DMA transfer
davinci_start_dma(ch);
copy_to_user(from Local buffer to User buffer);
davinci_request_dma(ch);
}
//
Do you think I have missed any configurations or is there a know problem with
the driver?
Note:
Also tried to move the Request Dma Channel to OPEN method and Free Dma Channel
to CLOSE method.
Still no luck!
Thanks and Regards,
Nitin Joshi
http://www.mindtree.com/email/disclaimer.html
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
DM6446 OSD flicker on CRT TV in PAL mode
Hi, I'm observing a lot of flicker on the OSD0 window on a CRT TV when configured in PAL mode. I render a basic UI on OSD0 and see a flicker. The OSD0 is configured in RGB565 mode. Are there any filters available in Davinci to eliminate (or at least reduce) the flickering. Let me know if I need to provide more data. No flicker is observed on LCD TV. When I configure the OSD0 in NTSC mode, the flicker is observed, but lesser compared to PAL. (I'm using LSP2.0 kernel) thanks tojo ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
