Hello all,
I am porting the Davinci Linux kernel to a new architecture, Jacinto 2. I have
most everything up and running besides a few init scripts, and I was curious
how one would go about testing the kernel for stability. How was the Davinci
kernel tested for robustness? Is there some kind
Hi,
I'm trying to build DVSK 2_00_00_22, and I'm failing in it.
More precisely, it's dmai make that blame with the following line:
/mnt/lavoro/gigavision/mv_pro_5.0/montavista/pro/devkit/arm/v5t_le/bin/../lib/gcc/armv5tl-
montavista-linux-gnueabi/4.2.0/../../../../armv5tl-montavista-linux-
Hi Murali,
From: Muralidharan Karicheri a0868...@gt516km11.gt.design.ti.com
This patch adds support for setting bus parameters such as bus type
(Raw Bayer or Raw YUV image data bus), bus width (example 10 bit raw
image data bus, 10 bit BT.656 etc.), and polarities (vsync, hsync, field
etc)
Andrea Gasparini wrote:
Hi,
I'm trying to build DVSK 2_00_00_22, and I'm failing in it.
More precisely, it's dmai make that blame with the following line:
/mnt/lavoro/gigavision/mv_pro_5.0/montavista/pro/devkit/arm/v5t_le/bin/../lib/gcc/armv5tl-
Yusuf Caglar AKYUZ spiffera, alle Monday 29 June 2009 circa:
AFAIK, package.bld files are generated automatically. You need to
adjust makefiles for correct toolchains. I'm using OpenEmbedded for
DMAI builds. It has most of the patches necessary for building DMAI
and gstreamer-ti. I'm attaching
Andrea Gasparini spiffera, alle Monday 29 June 2009 circa:
Anyway, the question remains valid, DO I REALLY NEED to modify almost
ten config.bld to have the right path, or is there another, simpler way?
ok, I was too hurried in saying so.
It seems it's enough to modifiy:
Andrea Gasparini wrote:
Andrea Gasparini spiffera, alle Monday 29 June 2009 circa:
Anyway, the question remains valid, DO I REALLY NEED to modify almost
ten config.bld to have the right path, or is there another, simpler way?
ok, I was too hurried in saying so.
It seems it's enough to
Hi,
I would like to modify and reflash u-boot on DM365.
There is a sourceforge project [1] for the serial flashing tools for
various davinci processor, but not for dm365.
The dvevm PSP contains a tar.gz archive named flash_utils, but in the
top level makefile, the dm36x is commented out.
Jean_Philippe,
The reason for the DM365 serial flashing tools not being available at this
point of time is because the serial flashing tools are designed in such a way
that assumes the RBL to set the baud rate to 115200.
There is a bug in the RBL which sets it to 16/13 times of 115200.
Add support for the DA850/OMAP-L138 Evaluation Module (EVM)
from TI. The EVM has User Interface (UI) card which contains
various devices. This UI card can be connected to the base
board. Support for all the devices on the UI card and ones on
the EVM will be added in subsequent patches.
The EVM
Krzysztof,
-Original Message-
From: Krzysztof Helt [mailto:krzysztof...@poczta.fm]
Sent: Friday, June 26, 2009 10:49 AM
To: Rajashekhara, Sudhakar
Cc: linux-fbdev-de...@lists.sourceforge.net; davinci-linux-open-
sou...@linux.davincidsp.com; Steve Chen; Pavel Kiryukhin
Subject: Re:
The DA850/OMAP-L138 is a new SoC from TI in the same family as
DA830/OMAP-L137.
Major changes include better support for power management,
support for SATA devices and McBSP (same IP as DM644x).
The Techinical Reference Manual is not available publicly
as yet, but should be available soon.
snip
-static struct tvp514x_platform_data tvp5146_pdata = {
- .clk_polarity = 0,
- .hs_polarity = 1,
- .vs_polarity = 1
Clearly this patch is against neither mainline nor the
current DaVinci GIT tree... I suggest reissuing against
mainline, now that it's got most DM355
Paulraj, Sandeep a écrit :
Jean_Philippe,
The reason for the DM365 serial flashing tools not being available at this
point of time is because the serial flashing tools are designed in such a way
that assumes the RBL to set the baud rate to 115200.
There is a bug in the RBL which sets it to
Hans,
When connecting a sensor like mt9t031 to SoC like DM355, DM6446 etc, driver
also need to know which MSB of the sensor data bus connected to which host bus.
For example, on DM365, we have following connection:-
data 9 (MSB) of the sensor is connected to data 11 of the host bus. For 10 bit
Hans,
When connecting a sensor like mt9t031 to SoC like DM355, DM6446 etc,
driver also need to know which MSB of the sensor data bus connected to
which host bus. For example, on DM365, we have following connection:-
data 9 (MSB) of the sensor is connected to data 11 of the host bus. For 10
It seems very unlikely to me that someone would ever choose to e.g. zero
one or more MSB pins instead of the LSB pins in a case like this.
No case in my experience...
Or do you have examples where that actually happens?
DM365 can work with 10 bit or 12 bit sensors. DM365 CCDC that receives the
Hans,
Had hit the send by mistake. Please ignore my previous reply...
snip
It seems very unlikely to me that someone would ever choose to e.g. zero
one or more MSB pins instead of the LSB pins in a case like this.
No case in my experience...
snip
Or do you have examples where that actually
Jean-Philippe François a écrit :
Paulraj, Sandeep a écrit :
Jean_Philippe,
The reason for the DM365 serial flashing tools not being available at
this point of time is because the serial flashing tools are designed
in such a way that assumes the RBL to set the baud rate to 115200.
There is
Mani, Arun wrote:
Hi All,
Anyone tried arecord in 2.6.30. I am constantly getting a overrun error which
is blocking the capture.
Thanks,
Arun
I tried it, and it is not working for me. I see constant overruns as well. This
code was working quite well on 2.6.28, I have no idea what
Caglar,
Thanks very much. Can I get the patch against Arago tree too. That will be of
great help.
Thanks,
Arun.
-Original Message-
From: Yusuf Caglar AKYUZ [mailto:caglarak...@gmail.com]
Sent: Monday, June 29, 2009 12:01 PM
To: Mani, Arun
Cc:
Mani, Arun wrote:
Caglar,
Thanks very much. Can I get the patch against Arago tree too. That will be of
great help.
Thanks,
Arun.
Patch is attached inline. It is against Arago next branch.
Regards,
Caglar
Troy Kisky wrote:
Use the sram(iram) to avoid underrun on audio.
I will clean this up after someone says it
works for them.
Hi,
First of all, thanks for looking into this. This patch
makes audio usable again for me on 2.6.30 kernel and
overruns are gone.
What I want to ask is, there is
On Monday 29 June 2009, Karicheri, Muralidharan wrote:
snip
-static struct tvp514x_platform_data tvp5146_pdata = {
- .clk_polarity = 0,
- .hs_polarity = 1,
- .vs_polarity = 1
Clearly this patch is against neither mainline nor the
current DaVinci GIT tree... I
-Original Message-
From: Jean-Philippe François [mailto:jp.franc...@cynove.com]
Sent: Monday, June 29, 2009 12:00 PM
To: Paulraj, Sandeep
Cc: davinci-linux-open-source
Subject: Re: dm365 serial flashing tools ?
Jean-Philippe François a écrit :
Paulraj, Sandeep a écrit :
Yusuf Caglar AKYUZ wrote:
Troy Kisky wrote:
Use the sram(iram) to avoid underrun on audio.
I will clean this up after someone says it
works for them.
Hi,
First of all, thanks for looking into this. This patch
makes audio usable again for me on 2.6.30 kernel and
overruns are gone.
Hi Caglar,
I tried your patch in arago tree and still getting the overrun issues. When I
replaced the pcm_lib.c file from 1.0.20 to 1.0.19 version without your patches,
I was able to make the loopback work.
r...@arago:~# arecord -f dat -d 10 -v | aplay -f dat -d 10 -v
Recording WAVE 'stdin' :
snip
That is because, I have my first (vpfe capture version v3)
patch lined up for merge to upstream/davinci git kernel ...
NOTE: Depends on v3 version of vpfe capture driver patch
What is your suggestion in such cases?
Always submit against mainline. In the handfull of cases
that won't
On Monday 29 June 2009, Karicheri, Muralidharan wrote:
I think you didn't get my point. We have patches that are in
the pipeline waiting for merge that is neither available in
the upstream nor in the DaVinci tree.
The linux-media pipeline. Sure. I'm quite familiar with
what it means to have
AFAIK, package.bld files are generated automatically. You need to
adjust makefiles for correct toolchains.
FYI, package.bld scripts aren't typically autogenerated, they're source files
that generate cross-platform, cross-toolchain GNU makefiles (package.mak).
Chris
-Original
On Mon, Jun 29, 2009 at 18:59:02, Rajashekhara, Sudhakar wrote:
The DA850/OMAP-L138 is a new SoC from TI in the same family as
DA830/OMAP-L137.
Major changes include better support for power management,
support for SATA devices and McBSP (same IP as DM644x).
The Technical Reference Manual
31 matches
Mail list logo
