From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Cc: jesse.barnes@intel.com
Subject: Re: [PATCH] i915: enable AVI infoframe for intel_hdmi.c [v4]
Date: Thu, 21 Oct 2010 10:36:33 +0100 [thread overview]
Message-ID: <b9dded$grr7f7@orsmga002.jf.intel.com> (raw)
In-Reply-To: <20101020194541.GC15994@hardeman.nu>
[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]
On Wed, 20 Oct 2010 21:45:41 +0200, David Härdeman <david@hardeman.nu> wrote:
> On Fri, Sep 24, 2010 at 09:44:32PM +0200, David Härdeman wrote:
> > Two questions still remain:
> >
> > I'm assuming that the sdvo hardware also stores a header ECC byte in
> > the MSB of the first dword - is this correct?
> >
> > Does the SDVOB and SDVOC handling in intel_hdmi_set_avi_infoframe()
> > look correct?
>
> Ping...
Sorry David, I thought I had replied but it never made it to the list.
I was half waiting if someone would find the answer to your questions. I
am not certain about the reg -> port conversion either, but if it works
for you, that is a major step forward.
More importantly, the patch is missing your signed-off-by, which states
that the work is yours (or at least you vouchsafe for the originality of
the work) and you are free to contribute this work to upstream.
Just reply adding your 'Signed-off-by' and I'll push the patch to -next.
Thanks,
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
[-- 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
next prev parent reply other threads:[~2010-10-21 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 19:44 [PATCH] i915: enable AVI infoframe for intel_hdmi.c [v4] David Härdeman
2010-10-20 19:45 ` David Härdeman
2010-10-21 9:36 ` Chris Wilson [this message]
2010-10-21 22:08 ` David Härdeman
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='b9dded$grr7f7@orsmga002.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jesse.barnes@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.