From: "chaithrika" <chaithrika@ti.com>
To: "'Chaithrika U S'" <chaithrika@ti.com>, <linux-media@vger.kernel.org>
Cc: <davinci-linux-open-source@linux.davincidsp.com>,
"'Manjunath Hadli'" <mrh@ti.com>,
"'Brijesh Jadav'" <brijesh.j@ti.com>
Subject: RE: [PATCH v3 0/4] ARM: DaVinci: DM646x Video: DM646x display driver
Date: Thu, 21 May 2009 11:42:57 +0530 [thread overview]
Message-ID: <03fc01c9d9db$2f9f8b20$8edea160$@com> (raw)
In-Reply-To: <1241789126-23317-1-git-send-email-chaithrika@ti.com>
Hi All,
Do you have any review comments on this patch set?
Regards,
Chaithrika
> -----Original Message-----
> From: Chaithrika U S [mailto:chaithrika@ti.com]
> Sent: Friday, May 08, 2009 6:55 PM
> To: linux-media@vger.kernel.org
> Cc: davinci-linux-open-source@linux.davincidsp.com; Manjunath Hadli;
> Brijesh Jadav; Chaithrika U S
> Subject: [PATCH v3 0/4] ARM: DaVinci: DM646x Video: DM646x display
> driver
>
> Display driver for TI DM646x EVM
>
> Signed-off-by: Manjunath Hadli <mrh@ti.com>
> Signed-off-by: Brijesh Jadav <brijesh.j@ti.com>
> Signed-off-by: Chaithrika U S <chaithrika@ti.com>
>
> These patches add the display driver support for TI DM646x EVM.
> This patch set has been tested for basic display functionality for
> Composite and Component outputs.
>
> This patch set consists of the updates based on the review comments by
> Hans Verkuil.
>
> Patch 1: Display device platform and board setup
> Patch 2: VPIF driver
> Patch 3: DM646x display driver
> Patch 4: Makefile and config files modifications for Display
>
> Some of the features like the HBI/VBI support are not yet implemented.
> Also there are some known issues in the code implementation like
> fine tuning to be done to TRY_FMT ioctl.The USERPTR usage has not been
> tested extensively.
>
> -Chaithrika
next prev parent reply other threads:[~2009-05-21 6:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 13:25 [PATCH v3 0/4] ARM: DaVinci: DM646x Video: DM646x display driver Chaithrika U S
2009-05-21 6:12 ` chaithrika [this message]
2009-05-21 14:14 ` Hans Verkuil
2009-05-22 4:36 ` chaithrika
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='03fc01c9d9db$2f9f8b20$8edea160$@com' \
--to=chaithrika@ti.com \
--cc=brijesh.j@ti.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=linux-media@vger.kernel.org \
--cc=mrh@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox