Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Wu Fengguang <wfg@linux.intel.com>
To: "Wang, Zhenyu Z" <zhenyu.z.wang@intel.com>,
	"linux-gfx@linux.intel.com" <linux-gfx@linux.intel.com>,
	"xorg@lists.freedesktop.org" <xorg@lists.freedesktop.org>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: [PATCH 1/3] introduce i830_hdmi_priv.has_hdmi_sink
Date: Wed, 12 Nov 2008 16:16:03 +0800	[thread overview]
Message-ID: <1226477768.297868.8785@de> (raw)
In-Reply-To: <20081112072747.GD14627@zhen-devel.sh.intel.com>

On Wed, Nov 12, 2008 at 03:27:47PM +0800, Wang, Zhenyu Z wrote:
> On 2008.11.07 14:23:39 +0800, Wu Fengguang wrote:
> > HDMI is compatible with DVI, and we've seen many boards that
> > use HDMI port for DVI output.
> > 
> > So Zhenyu proposed this flag: i830_hdmi_priv.has_hdmi_sink
> > to indicate the presence of HDMI capable monitors.
> > 
> > Signed-off-by: Wu Fengguang <wfg@linux.intel.com>

> We should check if the symbol is available for xserver compatiblity.
> So below is updated patch for check this. 

> +
> +    if (xf86LoaderCheckSymbol("xf86MonitorIsHDMI") &&
> +	    xf86MonitorIsHDMI(edid_mon))
> +	dev_priv->has_hdmi_sink = TRUE;

I'm OK with the backward compatibility check.
The side effect is that audio output won't be enabled for old xservers.

Thanks,
Fengguang

  parent reply	other threads:[~2008-11-12  8:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-07  6:23 [PATCH 0/3] enable HDMI audio output for HDMI monitors V2 Wu Fengguang
2008-11-07  6:23 ` [PATCH 1/3] introduce i830_hdmi_priv.has_hdmi_sink Wu Fengguang
     [not found]   ` <20081112072747.GD14627@zhen-devel.sh.intel.com>
2008-11-12  8:16     ` Wu Fengguang [this message]
2008-11-07  6:23 ` [PATCH 2/3] enable Intel G45 integrated HDMI audio output Wu Fengguang
2008-11-07  6:23 ` [PATCH 3/3] enable Intel G35 SDVO " Wu Fengguang
2008-11-10 18:18 ` [PATCH 0/3] enable HDMI audio output for HDMI monitors V2 Adam Jackson
2008-11-13  2:05 ` Wang, Zhenyu Z

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=1226477768.297868.8785@de \
    --to=wfg@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-gfx@linux.intel.com \
    --cc=xorg@lists.freedesktop.org \
    --cc=zhenyu.z.wang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox