From: Alberto Navatta
Sent: Thursday, May 21, 2009 6:42 PM
Hi Kevin,
in general you are right, but in this case is the execution of the
bootloader to fail and there's no way to address the problem after
reboot.
I think there's a problem in the logic implemented in the cfi flash
driver:
On Thu, 2009-05-21 at 22:43 -0700, Troy Kisky wrote:
Rajashekhara, Sudhakar wrote:
Rajashekhara, Sudhakar wrote:
Troy,
I tried this patch on DM644x EVM and following are my observations:
1. Playback works fine.
2. Record has some issues. Recorded stream has Loud volume on
the
Previewer is very fast and I am sure it can complete previewing within 40ms. So
there must be some other delay in the application.
Thanks,
Brijesh Jadav
From: Ondrej Pindroch [mailto:opindr...@softhard.sk]
Sent: Thursday, May 21, 2009 7:25 PM
To: Jadav, Brijesh
Hi everyone,
I created a JPEG encoder demo on my DM355 custom EVM, the source is from
TVP5146 and its format is YUV422TLE, But I found a problem of it. When I
captured a still scene, the JPEG encoder worked fine; When I captured dynamic
scene, the JPEG encoder worked bad and the saved file is
Ring, Chris cr...@ti.com writes:
Just a quick can we talk through this patch a bit note...
I _think_ there are existing codecs on some DaVinci platforms
(e.g. DM365) that are already using this SRAM memory. The current
[easy] solution to their use case was to keep this memory out of the
Yes, there will definitely be Linux support coming. I haven't heard the exact
dates, but I understand it should be soon (this year?). I hear the main
hang-up is the emulation drivers (i.e. from Spectrum Digital and Blackhawk).
-Original Message-
From:
Rajashekhara, Sudhakar wrote:
Troy,
I tried this patch on DM644x EVM and following are my observations:
1. Playback works fine.
2. Record has some issues. Recorded stream has Loud volume on
the right side, and on the left, volume is very low.
This was because of my faulty Line-In cable.
I did not get the problem like you , the jpeg encoder with using image
engine works fine on my board .
- Original Message -
From: Jammy Dane
To: davinci-linux-open-source
Sent: Friday, May 22, 2009 10:36 PM
Subject: JPEG Problem on DM355
Hi everyone,
I created a
-Original Message-
From: davinci-linux-open-source-boun...@linux.davincidsp.com
[mailto:davinci-linux-open-source-boun...@linux.davincidsp.com
] On Behalf Of Kevin Hilman
Sent: Friday, May 22, 2009 8:11 AM
To: Ring, Chris
Cc: davinci-linux-open-source@linux.davincidsp.com; David
On Friday 22 May 2009, Tivy, Robert wrote:
I think the way codecs are going to request SRAM is by
asking for all of it,
Yeech. I hope that's on the list of bugs to fix!
which means that if the audio driver takes any of it
through sram_alloc(), codecs won't have any. And if
codecs take
-Original Message-
From: David Brownell [mailto:davi...@pacbell.net]
On Friday 22 May 2009, Tivy, Robert wrote:
I think the way codecs are going to request SRAM is by
asking for all of it,
Yeech. I hope that's on the list of bugs to fix!
AFAIK, it's not, nor is it a bug.
Brad:
who should know the date of Linux support version for CCS4? Where should I ask?
Moreover, where I can purchase the XDS510 cable(JTAG cable) other than TI. the
TI's quote is quite expensive.
Thanks
J.J.
--- On Fri, 5/22/09, Griffis, Brad bgrif...@ti.com wrote:
From: Griffis, Brad
Ring, Chris cr...@ti.com writes:
-Original Message-
From: David Brownell [mailto:davi...@pacbell.net]
On Friday 22 May 2009, Tivy, Robert wrote:
I think the way codecs are going to request SRAM is by
asking for all of it,
Yeech. I hope that's on the list of bugs to fix!
elbert shiang wrote:
Brad:
who should know the date of Linux support version for CCS4? Where should
I ask?
TI, but so far I have heard little.
Moreover, where I can purchase the XDS510 cable(JTAG cable) other than
TI. the TI's quote is quite expensive.
That's the price, I doubt you get
On Friday 22 May 2009, Vladimir Pantelic wrote:
Moreover, where I can purchase the XDS510 cable(JTAG cable) other than
TI. the TI's quote is quite expensive.
That's the price, I doubt you get it cheaper anywhere else
There are other JTAG options than the xds510 and friends,
but many of
-Original Message-
From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
All of this discussion isn't relevant to the need for an in-kernel
SRAM allocator upstream. What is being discussed here is various ways
of using or not using it. IMHO, this discussion isn't relevant to
[ removing linux-arm-kernel ]
Ring, Chris cr...@ti.com writes:
-Original Message-
From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
All of this discussion isn't relevant to the need for an in-kernel
SRAM allocator upstream. What is being discussed here is various ways
of
New thread, as requested...
I like Rob/David's suggestion of adding calls to
request_mem_region()/release_mem_region() in each allocator (SRAM and CMEM)
when they're given this SRAM memory to manage to help catch collisions. CMEM
added this recently too, so at least we'd get a nice error msg
Ring, Chris wrote:
New thread, as requested...
I like Rob/David's suggestion of adding calls to
request_mem_region()/release_mem_region() in each allocator (SRAM and CMEM)
when they're given this SRAM memory to manage to help catch collisions. CMEM
added this recently too, so at least
On Friday 22 May 2009, Ring, Chris wrote:
Assuming the SRAM allocator is pushed, can we talk through
what happens when the audio driver (or any other driver!)
requests this SRAM and either no SRAM is available,
That's all driver-specific fault handling policy.
If DaVinci gets power management
Troy Kisky wrote:
Rajashekhara, Sudhakar wrote:
Troy,
I tried this patch on DM644x EVM and following are my observations:
1. Playback works fine.
2. Record has some issues. Recorded stream has Loud volume on
the right side, and on the left, volume is very low.
This was because of my
FYI, I just added one other topic and an updated block diagram as well:
http://tiexpressdsp.com/index.php?title=Configuring_GPIO_Interrupts
Kevin, I saw some mention of level-sensitive interrupts in one of your patches
for GPIO. Could you elaborate on what you're talking about there? To my
Hi,
I will be coming up with an updated patch for this (3/3) early next week to
address -
1. Corrections to eccpos[]
2. Comments from Troy
Thanks
Sneha
-Original Message-
From: David Brownell [mailto:davi...@pacbell.net]
Sent: Wednesday, May 20, 2009 8:38 PM
To:
On 23-05-09 01:15, Ring, Chris wrote:
New thread, as requested...
I like Rob/David's suggestion of adding calls to
request_mem_region()/release_mem_region() in each allocator (SRAM and CMEM)
What's the plan for getting CMEM upstream? I've been asking that
question to TI engineers for a
24 matches
Mail list logo
