From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: "Matsumura, Ryan" <ryan.matsumura@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: Second HDMI port not visible
Date: Wed, 7 Aug 2013 13:44:19 +0300 [thread overview]
Message-ID: <20130807104419.GR5004@intel.com> (raw)
In-Reply-To: <CAKMK7uFF9MQKjRHk09oTwcG8YarQK2+c-ok+y-sf8n8rk_6OOg@mail.gmail.com>
On Wed, Aug 07, 2013 at 09:41:39AM +0200, Daniel Vetter wrote:
> On Wed, Aug 7, 2013 at 5:10 AM, Matsumura, Ryan
> <ryan.matsumura@intel.com> wrote:
> > I have a BayTrail board with two HDMI ports and running the default Tizen 3.0M1 release. The first HDMI shows up just fine but I can't get the second screen to display anything. I tried enabling the second screen through the kernel command line parameters (video=HDMI-1:e video=HDMI-2:e) and running xrandr. This is my output from xrandr -q
>
> Iirc Baytrail still has a bunch of hardcoded ports ... Jesse?
Currently the code assumes that port C is eDP, not DP/HDMI. The specs
say that physically either port should be able to function in any role
(eDP/DP/HDMI).
Not sure if there's some way to detect which way the board is wired
(some VBT stuff like the eDP on port D on HSW?), or maybe we should
just register the DP/HDMI ports if eDP init fails?
> -Daniel
>
> >
> > Screen 0: minimum 320 x 200, current 640 x 480, maximum 8192 x 8192
> > VGA1 connected 640x480+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
> > 1024x768 60.0
> > 800x600 60.3 56.2
> > 848x480 60.0
> > 640x480 59.9*
> > HDMI1 connected 640x480+0+0 (normal left inverted right x axis y axis) 256mm x 144mm
> > 1920x1080 60.0 + 60.0 50.0 59.9 40.0
> > 1920x1080i 60.1 50.0 60.0
> > 1280x720 60.0 50.0 59.9
> > 1440x576i 50.1
> > 1440x480i 60.1 60.1
> > 720x576 50.0
> > 720x480 60.0 59.9
> > 640x480 60.0 59.9*
> > DP1 disconnected (normal left inverted right x axis y axis)
> >
> > Is there some other configuration I need? I tried this on both X and Wayland. Seems more like a DRM issue at this point.
> >
> > -Ryan
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
>
>
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2013-08-07 10:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 3:10 Second HDMI port not visible Matsumura, Ryan
2013-08-07 7:41 ` Daniel Vetter
2013-08-07 10:44 ` Ville Syrjälä [this message]
2013-08-07 15:48 ` Jesse Barnes
2013-08-07 19:15 ` Matsumura, Ryan
2013-08-07 20:29 ` Jesse Barnes
2013-08-09 12:50 ` Chris Wilson
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=20130807104419.GR5004@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ryan.matsumura@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.