Hi,we are working on the Kevin Hilman 2.6.34 kernel version.This is the driver we found over there and we had to drive a parallel RGB LCD which was not supported.We understood we had to work on this branch (see for instance:
2010/6/14 Kieran Bingham kieranbing...@gmail.com
Hi Raffaele,
I'm afraid I'm only using the USB in Host Mode - I have not looked at
anything in gadget mode.
Have you tried using the Arago Tree yet ?
--
Regards
Kieran
I made a test with Arago tree and evaluation board with usb slave and
On Monday 14 June 2010 07:38:03 pm Karicheri, Muralidharan wrote:
Hi,
Why are you trying to fix this old fb driver when TI India is already
working on to up port the latest Arago fb and v4l2 drivers?
Do you have any schedule about when are you going to submit VPBE drivers?
To be honest,
Mike,
DSPLink does not use CMEM internally.
Deepali
-Original Message-
From: davinci-linux-open-source-bounces+deepali=ti@linux.davincidsp.com
[mailto:davinci-linux-open-source-bounces+deepali=ti@linux.davincidsp.com]
On Behalf Of Mike Williamson
Sent: Friday, May 28, 2010
Hi Caglar,
On Tue, Jun 15, 2010 at 12:54:54, Caglar Akyuz wrote:
On Monday 14 June 2010 07:38:03 pm Karicheri, Muralidharan wrote:
Hi,
Why are you trying to fix this old fb driver when TI India is already
working on to up port the latest Arago fb and v4l2 drivers?
Do you have any
On Fri, Jun 11, 2010 at 07:24:51PM +0530, Sudhakar Rajashekhara wrote:
On DA830/OMAP-L137 and DA850/OMAP-L138 SoCs, the McASP peripheral
has FIFO support. This FIFO provides additional data buffering. It
also provides tolerance to variation in host/DMA controller response
times. More details
1. RE: [PATCH 0/3] davinci: spi: replace existing SPI driver
(Brian
Brian,
Just wanted to say that I'm glad you posted the patch here to fixe many bugs in
the Davinci SPI driver to the Davinci GIT kernel tree. I am using the Davinci
GIT kernel but with your equivalent SPI patches from
Hi,
On Tue, Jun 15, 2010 at 00:43:06, Brian Niebuhr wrote:
I have compiled with the davinci_all_defconfig, but I don't
have EVMs
for the other davinci platforms to test with.
I was testing this series on OMAP-L137, OMAP-L138 and DM365 EVMs and I
found that on all these EVMS,
Hi Marc-Andre,
On Tue, Jun 15, 2010 at 16:14:18, Marc-Andre Chenier wrote:
1. RE: [PATCH 0/3] davinci: spi: replace existing SPI driver
(Brian
Brian,
Just wanted to say that I'm glad you posted the patch here to fixe many bugs
in the Davinci SPI driver to the Davinci GIT kernel
Kieran Bingham wrote:
This patch was created by pulling in the code required from the Arago Tree.
This patch probably needs better description than that...
Checked by running on a Spectrum Digital DM365EVM Revision C.
Signed-off-by: Kieran Bingham kbing...@mpc-data.co.uk
[...]
diff
Krunal,
I have not experienced this so I cannot offer any advice other than
debugging methods, which you already know. Maybe you can cat /proc/mtd
to make sure it agrees with what you expect.
Steve
On 06/11/2010 12:41 PM, Krunal Patil wrote:
Steve,
Thanks for the reply. I have solved
Did you get this answered? As I remember, if you look in the H.264
spec, you can find the initial elements that describe the bitstream and
just paste those on the front. You could do this manually as long as
those parameters are constant in your system. I could probably look
those up again
Can you define what you mean by get the raw data?
On 06/03/2010 04:06 AM, shaofeng zhang wrote:
Hi, all
My platform have the FPGA modules as the video source, and I could get
the video stream as the BT 656 format, and It works very well.
Now I want to capturing the video stream as the Raw Data
I didn't get any answer for this ... As per your mail, we have to copy the
initial elements (File Header) and paste.
But we need the header information no of byes need to copy ...
Thanks Regards,
Raghu Ramaraj
From: Steve Poulsen
14 matches
Mail list logo
