Ryan Talbot wrote:
OK, but now that I've tried it, the vpfe_capture driver in 2.6.28
doesn't seem to support USERPTR I/O. It doesn't look like the latest
version of vpfe_capture does, either. And yet, using MMAP I/O is broken
because CMEM can't translate the mmap'd addresses... surely this is
Hello Everyone,
I am currently working on building codec_engine examples for evmDM6446 target
provided along with dvsdk_1_30_01_41 version.
Following build instructions in codec_examples folder, I was able to perfrom
"gmake" successfully in
folder "codecs", "extensions".
And when I did same in
On Fri, Jun 12, 2009 at 01:56:38, Kevin Hilman wrote:
> Hello,
>
> DaVinci git has been update to v2.6.30 as well as the merging of basic
support for dm365 and da830.
>
I tried booting this kernel on DA830 using da830_omapl137_defconfig but
booting hangs at:
...
Load Address: c0008000
That's right! He has done this and it seems it is working fine for him.
Regards,
Gopal Sukumar.
Tivy, Robert wrote:
The CMEM module does not need to be loaded for the application link stage. If you get
"undefined reference to CMEM_init" then that just means that you're not
correctly referenci
Chaithrika,
On Fri, Jun 05, 2009 at 06:28:40AM -0400, Chaithrika U S wrote:
> Adds driver support for the two instances of McASP on TI's DM646x.
In patch #3 you removed struct evm_snd_platform_data:
> -struct evm_snd_platform_data {
> - int tx_dma_ch;
> - int rx_dma_ch;
> -};
That struc
Kevin,
If you look at the Kconfig , I do not see ARCH_DAVINCI_DMx being selected for
DM365. Shouldn't that be the case?
Thanks,
Sandeep
> -Original Message-
> From: davinci-linux-open-source-boun...@linux.davincidsp.com
> [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com]
I followed the "Filesystem in NOR or NAND" info on the davincidsp wiki
site: http://wiki.davincidsp.com/index.php/Filesystem_in_NOR_or_NAND and
setup my kernel like it instructed.
Then, I erased the flash clean in u-boot and boot up that kernel.
I then used "flash_eraseall -version" to get it
> -Original Message-
> From: David Brownell [mailto:davi...@pacbell.net]
> Sent: Thursday, June 11, 2009 3:18 PM
> To: Tivy, Robert
> Cc: davinci-linux-open-source@linux.davincidsp.com; Andrea Gasparini
> Subject: Re: EDMA with user provided virtual addresses.
>
> On Thursday 11 June 2009
On Thursday 11 June 2009, Tivy, Robert wrote:
> > That kind of logic is easy to wrap in utility functions.
> > (If it were wrapped, would non-DSP code really need CMEM?)
>
> ... the requirement for phys contig buffers is mostly for HW
> accelerators that address memory w/o the benefit of an MMU
> o
> -Original Message-
> From: David Brownell [mailto:davi...@pacbell.net]
> Sent: Thursday, June 11, 2009 1:09 PM
> To: Tivy, Robert
> Cc: davinci-linux-open-source@linux.davincidsp.com; Andrea Gasparini
> Subject: Re: EDMA with user provided virtual addresses.
>
> On Thursday 11 June 2009
Hello,
DaVinci git has been update to v2.6.30 as well as the merging of basic
support for dm365 and da830.
Kevin
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/da
s-paul...@ti.com writes:
> The patch adds Support for new TI SOC DM365
>
> Signed-off-by: Sandeep Paulraj
Thanks, merging this series today.
Kevin
> ---
> arch/arm/mach-davinci/dm365.c| 700
> ++
> arch/arm/mach-davinci/include/mach/cputype.h |8 +
On Thursday 11 June 2009, m-kariche...@ti.com wrote:
> VPFE Capture driver for DaVinci Media SOCs :- DM355 and DM6446
>
> This is the version v2 of the patch series. This is the reworked
> version of the driver based on comments received against the last
> version of the patch.
I'll be glad to se
On Thursday 11 June 2009, m-kariche...@ti.com wrote:
> + I2C_BOARD_INFO("tvp5146", TVP5146_I2C_ADDR),
Minor nit: just use "0x5d" instead of defining TVP5146_I2C_ADDR.
Fix in a v3, iff you make one.
___
Davinci-linux-open-source mailing l
m-kariche...@ti.com writes:
> From: Muralidharan Karicheri
>
> Remove outdated driver files from davinci git tree
Can you add another patch that removes the old Kconfig/Makfile entries
as well (of course, this only applied to davinci git and not mainline.)
Also, can't we drop the Kconfig/Makefi
On Thursday 11 June 2009, Tivy, Robert wrote:
> EDMA requires physically contiguous buffers,
> so in addition to needing to know the physical address,
> you also must ensure that your buffers are contiguous physically,
Not really. The usual way to handle that sort of thing is
to make what
TI's Codec Engine Linux Utils module CMEM can do what you want, but I don't
know if it's even a possibility for you. EDMA requires physically contiguous
buffers, so in addition to needing to know the physical address, you also must
ensure that your buffers are contiguous physically, and CMEM pr
The CMEM module does not need to be loaded for the application link stage. If
you get "undefined reference to CMEM_init" then that just means that you're not
correctly referencing cmem.a in your link.
Regards,
- Rob
From: davinci-linux-open-source-boun...@linu
On Thursday 11 June 2009, Andrea Gasparini wrote:
> So, the question is: is there a way to use EDMA with (at least one) user
> space address?
No.
> Can I know (and how) a physical address given the userspace one?
Yes, there are standard utilities for that ... but I don't recall
their names. T
On Thursday 11 June 2009, Ottavio Campana wrote:
> * what must the value of I2C_DRIVERID_TVP5150 be?
probably just remove it; most of those I2C_DRIVERID values
are useless so they've slowly been getting removed.
___
Davinci-linux-open-source mailing l
On Thu, Jun 11, 2009 at 09:49:19PM +0800, zhenfeng ren wrote:
> hi,everyone:
>
> I see that dm6446 contains a 300Mhz ARM and a C64x+ DSP, while
> omap3530 contains a 600Mhz ARM and a C64x+ DSP.
> Dm6446's DSP is a little stronger than omap 3530.
> DM6446 is much expensive than omap 3530, is it rig
s-paul...@ti.com writes:
> Patch updates the Kconfig for the various DaVinci EVMs
> This is being done based on a comment received when
> DM365 patches were reviewed.
> Each EVM defaults to be enabled whenever the SOC is enabled
My suggestion was to only have the EVMs enabled, but you enabled
all
Chaithrika U S writes:
> 1) Registers the platform devices for ASP on dm355, dm644x and dm646x so that
> the machine driver can probe to get ASP related platform data.
> 2) Move towards definition of the asp clocks using physical name(for dm355 and
> dm644x)
Why do you want to move towards the c
David Brownell writes:
> CC arch/arm/mach-davinci/sram.o
> arch/arm/mach-davinci/sram.c: In function 'sram_init':
> arch/arm/mach-davinci/sram.c:63: warning: comparison of distinct pointer
> types lacks a cast
>
> Signed-off-by: David Brownell
Thanks, pushing today.
Kevin
> ---
> arc
From: Muralidharan Karicheri
common voss module for video drivers
This is a new module added for vpss library functions that are
used for configuring vpss system module. All video drivers will
include vpss.h header file and call functions defined in this
module to configure vpss system module.
From: Muralidharan Karicheri
Remove outdated driver files from davinci git tree
No change from last patch
Reviewed By "Hans Verkuil".
Reviewed By "Laurent Pinchart".
Signed-off-by: Muralidharan Karicheri
---
Applies to Davinci GIT Tree
drivers/media/video/ccdc_davinci.c | 124
drivers
From: Muralidharan Karicheri
DM644x platform and board setup
This adds plarform and board setup changes required to support
vpfe capture driver on DM644x
Added registration of vpss platform driver based on last comment
Reviewed By "Hans Verkuil".
Reviewed By "Laurent Pinchart".
Signed-off-by:
From: Muralidharan Karicheri
common types used across CCDC modules
No change from last version
Reviewed By "Hans Verkuil".
Reviewed By "Laurent Pinchart".
Signed-off-by: Muralidharan Karicheri
---
Applies to v4l-dvb repository
include/media/davinci/ccdc_types.h | 43 ++
From: Muralidharan Karicheri
Makefile and config files for the driver
This adds Makefile and Kconfig changes to build vpfe capture driver.
Added configuration variable for vpss driver based on last review
Reviewed By "Hans Verkuil".
Reviewed By "Laurent Pinchart".
Signed-off-by: Muralidharan
From: Muralidharan Karicheri
DM355 platform and board setup
This has platform and board setup changes to support vpfe capture
driver for DM355 EVMs.
Added registration of vpss platform driver based on last review
Reviewed By "Hans Verkuil".
Reviewed By "Laurent Pinchart".
Signed-off-by: Mural
From: Muralidharan Karicheri
CCDC hw device header file
Adds ccdc hw device header for vpfe capture driver
Incorporated review comments against previous patch
Reviewed By "Hans Verkuil".
Reviewed By "Laurent Pinchart".
Signed-off-by: Muralidharan Karicheri
---
Applies to v4l-dvb repository
From: Muralidharan Karicheri
DM355 CCDC hw module
Adds ccdc hw module for DM355 CCDC. This registers with the bridge
driver a set of hw_ops for configuring the CCDC for a specific
decoder device connected to vpfe.
Following are some of the major comments addressed :-
1) removed vpss con
From: Muralidharan Karicheri
Resending to have all patches together since I had to resend couple of
them earlier and had to fix few issues...
VPFE Capture driver for DaVinci Media SOCs :- DM355 and DM6446
This is the version v2 of the patch series. This is the reworked
version of the driver bas
From: Muralidharan Karicheri
DM644x CCDC hw module
This is the hw module for DM644x CCDC. This registers with the
vpfe capture driver and provides a set of hw_ops to configure
CCDC for a specific decoder device connected to the VPFE
Following are some of the major comments addressed :-
On Thu, 2009-06-11 at 18:32 +0530, Santosh Singh wrote:
> -Original Message-
> From: Steve Chen [mailto:sc...@mvista.com]
> Sent: Thursday, June 11, 2009 5:57 PM
> To: Santosh Singh
> Cc: davinci-linux-open-source@linux.davincidsp.com
> Subject: Re: Need help for missing sound after some ti
>On Wed, 10 Jun 2009, Karicheri, Muralidharan wrote:
>
>> So how do I know what frame-rate I get? Sensor output frame rate depends
>> on the resolution of the frame, blanking, exposure time etc.
>
>This is not supported.
>
I am still not clear. You had said in an earlier email that it can support
>
>> - video streaming devices like the davinci videoports where you can hook
>> up HDTV receivers or FPGAs: here you definitely need a new API to setup
>> the streaming parameters, and you want to be able to do that from the
>> application as well. Actually, sensors are also hooked up to these
>d
Hi,
In our experience, I have following cases where we need to set the device to
capture/display at certain resolution and fps.
Capture side
-
1) IP Netcam applications. If the solution uses Micron sensors such as
MT9T001/031/P031 etc, application will require to do streaming at var
hi,everyone:
I see that dm6446 contains a 300Mhz ARM and a C64x+ DSP, while
omap3530 contains a 600Mhz ARM and a C64x+ DSP.
Dm6446's DSP is a little stronger than omap 3530.
DM6446 is much expensive than omap 3530, is it right? But I think
omap3530 is better than dm6446.
Could someone give me a ex
The patch adds Support for new TI SOC DM365.
Patch is similar to v3 of the patch.
The calculation for the PLL output frequency is different in the
DM365. This is being addressed in this version of the patch.
Signed-off-by: Sandeep Paulraj
---
arch/arm/mach-davinci/clock.c|5 +
>> Why force all platforms to set it if the driver is perfectly capable do
>> this itself? As I said - this is not a platform-specific feature, it's
>> chip-specific. What good would it make to have all platforms using
>> mt9t031 to specify, that yes, the chip can use both falling and rising
>> p
-Original Message-
From: Steve Chen [mailto:sc...@mvista.com]
Sent: Thursday, June 11, 2009 5:57 PM
To: Santosh Singh
Cc: davinci-linux-open-source@linux.davincidsp.com
Subject: Re: Need help for missing sound after some time in /dev/dsp
On Thu, 2009-06-11 at 14:17 +0530, Santosh Singh wr
Hello All,
I have a Blackhawk JTAG Emulator (USB560M). Using this I can debug DSP side
(C64x) program. Can I use the same to debug the ARM side program?
With best regards,
Venkatachala Upadhya| Extn: 65395|
--
http://www.mindtree.com/email/disclaimer.html
_
Hello Everyone,
I am currently working on building codec_engine examples for evmDM6446 target
provided along with dvsdk_1_30_01_41 version.
Following build instructions in codec_examples folder, I was able to perfrom
"gmake" successfully in
folder "codecs", "extensions".
And when I did same in
On Thu, 2009-06-11 at 14:17 +0530, Santosh Singh wrote:
> Hi All,
>
> We are writing small application on TI's DM6446 evaluation board.
>
> I am facing sound related problem i.e., with /dev/dsp.
>
> When we are playing some .wav file using na_play ,I could hear the sound for
> a longer period
Hi,
Have you find the patches? I started an inquiry within Monta Vista.
Unfortunately, it took this long to find the patches that are
accidentally deleted from the server. Please let me know if you still
need the patches.
Regards,
Steve
___
Davinci
Hello,
I wanted to check whether the latest ti-gst plugins(from omap-zoom) support
decoding of MPEG-4 video? I have a .mp4 file with MPEG-4 video and MPEG-4 AAC
audio, when I play through the plugins only Audio plays.
Here is the pipeline
gst-launch --gst-debug-no-color filesrc location=/dem
Hi,
I'm coding a module that takes from userspace an address pointer, and uses
it to fill the memory with some EDMA process.
My problem is that EDMA (fairly) wants a physical address: I usually use
dma_map_single() to have returned a physical pointer to do this kind of
stuff, but in this case,
>
>
> On 06/11/2009 11:33 AM, Hans Verkuil wrote:
>>>
>>> On 06/11/2009 10:35 AM, Hans Verkuil wrote:
>
>
>
>>> Hmm,
>>>
>>> Why would we want the *application* to set things like this *at all* ?
>>> with sensors hsync and vsync and other timing are something between
>>> the bridge and the sensor
>
>
> On 06/11/2009 10:35 AM, Hans Verkuil wrote:
>>> Karicheri, Muralidharan a écrit :
>> We need
>> streaming capability in the driver. This is how our driver works
>> with mt9t031 sensor
>>raw-bus (10 bit)
>> vpfe-capture - mt9t031 driver
>>
Hi Ondrej,
This means linking cmem to your app has failed. Ensure that you have loaded the
cmem module.
Thanks,
Gopal Sukumar.
Ondrej Pindroch wrote:
Hi
How can I use CMEM and all it's API. In my application. I need to get one buffer with
size almost 10MB, which will be continous in virtual
Hi
How can I use CMEM and all it's API. In my application. I need to get one
buffer with size almost 10MB, which will be continous in virtual and
physical memory space. I have tried link cmem.a to my project but it told me
"undefined reference to CMEM_init" and so on.
Thanks for your answer
On
Hi All,
We are writing small application on TI's DM6446 evaluation board.
I am facing sound related problem i.e., with /dev/dsp.
When we are playing some .wav file using na_play ,I could hear the sound for a
longer period without any problem.
But from a C routine when we are executing a shell s
Ottavio Campana wrote:
Ottavio Campana wrote:
Kevin Hilman wrote:
FYI I've added this series to a staging branch of DaVinci git
after some minor compile updates for the new kernel.
See branch 'staging/vpfe'.
cool. I think I'll try it in a few days.
I tried it today. It seems not to wor
> Karicheri, Muralidharan a écrit :
>>
We need
streaming capability in the driver. This is how our driver works
with mt9t031 sensor
raw-bus (10 bit)
vpfe-capture - mt9t031 driver
||
V
Karicheri, Muralidharan a écrit :
We need
streaming capability in the driver. This is how our driver works
with mt9t031 sensor
raw-bus (10 bit)
vpfe-capture - mt9t031 driver
||
V
56 matches
Mail list logo
