On Wednesday 29 April 2009, Subbrathnam, Swaminathan wrote:
You would have to implement a UVC gadget on DM355
Linux platform to enable PC to see the DM355 product as a
USB Webcam.
Another option is to work with the userspace PTP code
(built over usbfs) that's recently been posted on
Hi all,
I am writing a code to display a video using V4l2 drivers (On OMAPEVM ).
When I run the code.. It is giving an error message that .. memory could
not be allocated.
This error I am getting when I am calling dispaly application from a QT
application,(QT internally uses /dev/fb0 ).
But
-linux-open-source
-- next part --
An HTML attachment was scrubbed...
URL:
http://linux.omap.com/pipermail/davinci-linux-open-source/attachments/20090430/ba55f9f9/attachment-0001.htm
--
Message: 2
Date: Thu, 30 Apr 2009 09:55:36 +0800
From: Liu
Hi,all
sorry for last email, there is something wrong with it, the flash I used now is
K9F4G08U0A not K9F1208U0A.
Date: Thu, 30 Apr 2009 20:14:43 +0800
From: Jammy Dane benxuelan0...@gmail.com
Subject: dm355 no output in UART
To: davinci-linux-open-source
Hi Steve,
I have tried setting PINMUX3 to 0x3F as well as 0x00. In both the cases I
get the same error frame sync not detected
Below is the code snippet where I get this error:
pcrtemp = PCR;
/*Enable the transmitters pins as GPIO*/
PCR = PCR | RIOENABLE;
/*Wait for the first
Dear Liu,
I am using following configuration for McBSP0
#define MCBSP_DXR 0x01E02004
#define MCBSP_DRR 0x01E02000
static audio_stream_t output_stream = {
.id = FM11 out,
.dma_dev = DAVINCI_DMA_MCBSP_TX,
.input_or_output = FMODE_WRITE,
.mcbsp_id = 0
};
static audio_stream_t
Hi All,
Does GIT kernel support DM355?
If it supports DM355 then where will I find all codes related to McBSP?
I downloaded the latest git kernel. When I do make menuconfig it gives
error as below:
Makefile:317: warning: overriding commands for target
`/home/azam/work/Linux'
Makefile:115:
Hi all,
I am developing an application based on the scale example in the
codec_engine_1_10_01 package. The changes made are essentially adding
elements to the ISCALE_Params struct in the codecs/iscale.h file.
When I run the application it gives remote node creation failure. The
logs obtained are
Vipin Bhandari vipin.bhand...@ti.com writes:
The scatterlist traversal is made proper. The patch has some minor
comments modification and also sets the value written to the
DAVINCI_MMCTOR register properly. The timeout calculation is made
proper by deriving it from the clock values.
This
Mark A. Greer mgr...@mvista.com writes:
From: Mark A. Greer mgr...@mvista.com
The offset for the compare register used by the davinci
time code are passed in via the cmp_off member of the
'davinci_timer_instance' structure. Therefore, the
offset defined in time.c are not necessary.
Can you run your app with the CE_DEBUG env var set to 2 or 3?
http://tiexpressdsp.com/index.php?title=CE_DEBUG
Looks like you're DSP load is ok, but something's going wrong locating or
starting the remote alg. CE_DEBUG=3 will increase the amount of trace, as well
as provide the DSP-side
On Thursday 30 April 2009, Kevin Hilman wrote:
As one can see by the logs below, linux sees the IDE device (ide0), but not
the
partitions, and will not let me connect to them. Has anyone had this
problem,
or knows what I am doing wrong?
I have seen this problem as well, but have
Hi Mark,
Sorry for the review lag and the lack of attention to the da830 stuff.
I've been focusing on getting DaVinci core code reworked and submitted
upstream for the next merge window.
Mark A. Greer mgr...@mvista.com writes:
From: Mark A. Greer mgr...@mvista.com
The da830/omap l137 is a
David Brownell davi...@pacbell.net writes:
On Thursday 30 April 2009, Kevin Hilman wrote:
As one can see by the logs below, linux sees the IDE device (ide0), but
not the
partitions, and will not let me connect to them. Has anyone had this
problem,
or knows what I am doing wrong?
Hi,
I am having build issues and/or boot up issues with uImage built from latest
DaVinci GIT for DM355. I believe it had worked fine earlier - probably couple
of commits earlier.
Did anything change in the baseport that broke DM355 build?
make davinci_dm355_defconfig gives the following error
On Thursday 30 April 2009, Kevin Hilman wrote:
Indeed after loading pcf857x the disk itself is detected:
:)
Certain things can't be done without initializing those
GPIOs ... the defconfig should get updated to link that
driver statically.
Hmm, and since newer EVMs use Intel flash chips instead
On Thursday 30 April 2009, Narnakaje, Snehaprabha wrote:
arch/arm/kernel/sys_oabi-compat.o
: In function 'sys_oabi_epoll_wait':
/arm/kernel/sys_oabi-compat.c:288: error: implicit declaration of function
'kmalloc'
/arm/kernel/sys_oabi-compat.c:288: error: 'GFP_KERNEL' undeclared (first
-Original Message-
From: David Brownell [mailto:davi...@pacbell.net]
Sent: Thursday, April 30, 2009 5:36 PM
To: davinci-linux-open-source@linux.davincidsp.com
Cc: Narnakaje, Snehaprabha
Subject: Re: DM355 build on davinci-git
On Thursday 30 April 2009, Narnakaje, Snehaprabha
David Brownell davi...@pacbell.net writes:
On Thursday 30 April 2009, Narnakaje, Snehaprabha wrote:
arch/arm/kernel/sys_oabi-compat.o
: In function 'sys_oabi_epoll_wait':
/arm/kernel/sys_oabi-compat.c:288: error: implicit declaration of function
'kmalloc'
David Brownell davi...@pacbell.net writes:
On Thursday 30 April 2009, Kevin Hilman wrote:
Indeed after loading pcf857x the disk itself is detected:
:)
Certain things can't be done without initializing those
GPIOs ... the defconfig should get updated to link that
driver statically.
Hmm,
On Thursday 30 April 2009, Kevin Hilman wrote:
Certain things can't be done without initializing those
GPIOs ... the defconfig should get updated to link that
driver statically.
Hmm, and since newer EVMs use Intel flash chips instead
of the original AMD ones, maybe
On Wed, Apr 29, 2009 at 09:50:59AM -0500, Ambrose, Martin wrote:
On Tue, Apr 28, 2009 at 16:39:26, Mark A. Greer wrote:
On Wed, Apr 22, 2009 at 12:58:12, Ambrose, Martin wrote:
Where are you downloading the uImage?
TFTP from VMWare server running FC10.
Oops, I meant where as in what
On Wed, Apr 29, 2009 at 12:54:00PM -0500, Ambrose, Martin wrote:
On Tue, Apr 28, 2009 at 11:15:04, Ambrose, Martin wrote:
On Wed, Apr 22, 2009 at 12:58:12, Ambrose, Martin wrote:
I did some further digging. Note that my problem persists
with the v4 patches -- no surprise here I think
On Thursday 30 April 2009, Mark A. Greer wrote:
I use arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2008q3-72) 4.3.2
for now.
I rebuilt using this version and success! Thanks David for the nudge.
I was using 2007q3-51 4.2.1. I guess I could investigate what changed
which was
From: David Brownell dbrown...@users.sourceforge.net
Remove dm6446-specific SRAM allocator, as preparation for a
more generic replacement.
Signed-off-by: David Brownell dbrown...@users.sourceforge.net
---
Nothing in-kernel uses this...
arch/arm/mach-davinci/Makefile |2
From: David Brownell dbrown...@users.sourceforge.net
Provide a generic SRAM allocator using genalloc, and vaguely
modeled after what AVR32 uses. This builds on top of the
static CPU mapping set up in the previous patch, and returns
DMA mappings as requested (if possible).
Compared to its OMAP
From: David Brownell dbrown...@users.sourceforge.net
Package on-chip SRAM. It's always accessible from the ARM, so
set up a standardized virtual address mapping into a 128 KiB
area that's reserved for platform use.
In some cases (dm6467) the physical addresses used for EDMA are
not the same as
Tom,
Are you sure there are no other changes you needed to do to get dm9000 ethernet
working?
After doing these changes, I do not even get the link.
Thanks
Sneha
From: davinci-linux-open-source-boun...@linux.davincidsp.com
Hi Chris,
I tried with some code changes and observe that the application runs
successfully when I disable the memory allocations added in
SCALE_TI_Alloc() function in scale_ti_impl.c file. So there is some
problem it seems with the memory allocation.
Another problem I am facing is with
Hi Tom,
Tom Wheeler twhee...@control4.com writes:
Enabling LOCKDEP and applying the dm9000 IRQ handler bugfix were
insufficient to correct the problems that I was seeing. This is a
patch against the 2.6.28 rc8 kernel which configures the direct
GPIO IRQ for use with the dm9000. The dm9000
30 matches
Mail list logo
