Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Peter Ross <pross@xvid.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH-v2 0/3] drm/i915: interlaced mode support
Date: Wed, 18 Jan 2012 08:42:07 -0800	[thread overview]
Message-ID: <20120118084207.612c7ab4@jbarnes-desktop> (raw)
In-Reply-To: <cover.1326892931.git.pross@xvid.org>


[-- Attachment #1.1: Type: text/plain, Size: 1414 bytes --]

On Thu, 19 Jan 2012 00:29:23 +1100
Peter Ross <pross@xvid.org> wrote:

> This patch set enables enables interlaced mode output on
> generation 3 and above chipsets.
> 
> History here: https://bugs.freedesktop.org/show_bug.cgi?id=11220
> 
> It has been tested on the following hardware:
> * ASUS P5E-VM-HDMI (G35_G) and LG 32FS4D (VGA and SDVO connectors)
> * Intel DQ45CB (Q45_G) and Sony GDM 5411 (VGA connector)
> * Toshiba Portege R500 (I935_GM) and Sony GDM 5411 CRT (VGA connector)
> 
> PATCH HISTORY
> Version 1. Initial cut.
> Version 2. Set timings for gen3 and ILK/SB chipsets.
>            Allow interlaced output on HDMI connector.
> 
> Peter Ross (3):
>   drm/i915: specify vertical timings in frame units for interlaced
>     modes (gen3+)
>   drm/i915: allow interlaced mode output on the SDVO connector
>   drm/i915: allow interlaced mode output on the HDMI connector
> 
>  drivers/gpu/drm/i915/intel_display.c |   14 ++++++++++++++
>  drivers/gpu/drm/i915/intel_hdmi.c    |    2 +-
>  drivers/gpu/drm/i915/intel_sdvo.c    |    2 +-
>  3 files changed, 16 insertions(+), 2 deletions(-)

Cool, this series looks good.

Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>

Yi, can you give these patches a try with interlaced modes on SDVO and
HDMI attached displays and reply with your tested-by?

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2012-01-18 16:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-18 13:29 [PATCH-v2 0/3] drm/i915: interlaced mode support Peter Ross
2012-01-18 13:30 ` [PATCH-v2 1/3] drm/i915: specify vertical timings in frame units for interlaced modes (gen3+) Peter Ross
2012-01-18 13:30 ` [PATCH-v2 2/3] drm/i915: allow interlaced mode output on the SDVO connector Peter Ross
2012-01-18 13:30 ` [PATCH-v2 3/3] drm/i915: allow interlaced mode output on the HDMI connector Peter Ross
2012-01-18 16:42 ` Jesse Barnes [this message]
2012-01-19  9:51   ` [PATCH-v2 0/3] drm/i915: interlaced mode support Sun, Yi
2012-01-19 10:28     ` Daniel Vetter
2012-01-18 17:27 ` Eugeni Dodonov
2012-01-18 20:39 ` Paulo Zanoni
2012-01-18 20:55   ` Jesse Barnes
2012-01-20 11:24     ` Peter Ross
2012-01-22  7:14       ` Peter Ross
2012-01-22  9:38         ` Peter Ross
2012-01-19 10:29   ` Daniel Vetter
  -- strict thread matches above, loose matches on Subject: below --
2012-01-19 11:38 Peter Ross
2012-01-19 12:23 ` Paulo Zanoni

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=20120118084207.612c7ab4@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=pross@xvid.org \
    /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