From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Ilia Mirkin <imirkin@alum.mit.edu>
Cc: lkml <linux-kernel@vger.kernel.org>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: KMS question
Date: Thu, 13 Apr 2017 19:20:31 +0300 [thread overview]
Message-ID: <20170413162031.GW30290@intel.com> (raw)
In-Reply-To: <CAKb7Uvj+iqw3yBj6GHeWuHNP6kU=9U+t_oAGtBt2co6jc1A0nA@mail.gmail.com>
On Thu, Apr 13, 2017 at 11:37:45AM -0400, Ilia Mirkin wrote:
> On Thu, Apr 13, 2017 at 11:36 AM, Alex Deucher <alexdeucher@gmail.com> wrote:
> > On Thu, Apr 13, 2017 at 11:03 AM, Boszormenyi Zoltan <zboszor@pr.hu> wrote:
> >> 2017-04-13 16:05 keltezéssel, Alex Deucher írta:
> >>>
> >>> On Thu, Apr 13, 2017 at 9:03 AM, Boszormenyi Zoltan <zboszor@pr.hu> wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>> how can I disable the behaviour in the KMS drivers
> >>>> that enables all outputs at once?
> >>>>
> >>>> It is very annoying that on a POS machine with an
> >>>> 1024x768 LVDS and a 800x480 secondary monitor (both built-in)
> >>>> the KMS driver wakes up both. Then the framebuffer console
> >>>> and plymouth use both screens, making the primary output
> >>>> very odd with only the top-left part used by the boot splash.
> >>>>
> >>>> I would like the boot splash to be shown only on the primary
> >>>> output at its full resolution instead of on all outputs using
> >>>> the smallest common rectangle.
> >>>>
> >>>> Is there a kernel command line configuration that achieves this?
> >>>>
> >>>> The device in question uses the gma500 kernel driver but the same
> >>>> behaviour is observed with the i915 and radeon drivers.
> >>>>
> >>>
> >>> The problem is fbdev is not multi-head aware. The fbdev emulation in
> >>> the KMS drivers attempts to light up all monitors so that something
> >>> shows up on all heads. If you really want different per head
> >>> configurations, you need to use the KMS API directly. As a
> >>> workaround, you can use the kernel command line to disable the output
> >>> you don't want to be lit up. See:
> >>> https://wiki.archlinux.org/index.php/kernel_mode_setting
> >>> for more info. basically add video=TV-1:d to disable the output in
> >>> question. Replace TV-1 with whatever connector you want to disable.
> >>
> >>
> >> I tried adding video=DVI-D-1:d to the kernel command line.
> >>
> >> The effect is while the second output is indeed disabled, the
> >> framebuffer console still takes the second output's resolution
> >> into account and the boot splash is still using only the top-left
> >> 800x480 part of the 1024x768 primary screen.
> >>
> >> Also, the secondary screen got disabled also in X which is not desired.
> >> Can I wake it up under X somehow? This device is using the modesetting
> >> DDX driver.
> >
> > Can you enable it via randr?
>
> I think the video= based disable forces the connector to be disabled
> irrevocably.
# echo detect > /sys/class/drm/<whatever>/status
--
Ville Syrjälä
Intel OTC
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Ilia Mirkin <imirkin@alum.mit.edu>
Cc: Alex Deucher <alexdeucher@gmail.com>,
lkml <linux-kernel@vger.kernel.org>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: KMS question
Date: Thu, 13 Apr 2017 19:20:31 +0300 [thread overview]
Message-ID: <20170413162031.GW30290@intel.com> (raw)
In-Reply-To: <CAKb7Uvj+iqw3yBj6GHeWuHNP6kU=9U+t_oAGtBt2co6jc1A0nA@mail.gmail.com>
On Thu, Apr 13, 2017 at 11:37:45AM -0400, Ilia Mirkin wrote:
> On Thu, Apr 13, 2017 at 11:36 AM, Alex Deucher <alexdeucher@gmail.com> wrote:
> > On Thu, Apr 13, 2017 at 11:03 AM, Boszormenyi Zoltan <zboszor@pr.hu> wrote:
> >> 2017-04-13 16:05 keltezéssel, Alex Deucher írta:
> >>>
> >>> On Thu, Apr 13, 2017 at 9:03 AM, Boszormenyi Zoltan <zboszor@pr.hu> wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>> how can I disable the behaviour in the KMS drivers
> >>>> that enables all outputs at once?
> >>>>
> >>>> It is very annoying that on a POS machine with an
> >>>> 1024x768 LVDS and a 800x480 secondary monitor (both built-in)
> >>>> the KMS driver wakes up both. Then the framebuffer console
> >>>> and plymouth use both screens, making the primary output
> >>>> very odd with only the top-left part used by the boot splash.
> >>>>
> >>>> I would like the boot splash to be shown only on the primary
> >>>> output at its full resolution instead of on all outputs using
> >>>> the smallest common rectangle.
> >>>>
> >>>> Is there a kernel command line configuration that achieves this?
> >>>>
> >>>> The device in question uses the gma500 kernel driver but the same
> >>>> behaviour is observed with the i915 and radeon drivers.
> >>>>
> >>>
> >>> The problem is fbdev is not multi-head aware. The fbdev emulation in
> >>> the KMS drivers attempts to light up all monitors so that something
> >>> shows up on all heads. If you really want different per head
> >>> configurations, you need to use the KMS API directly. As a
> >>> workaround, you can use the kernel command line to disable the output
> >>> you don't want to be lit up. See:
> >>> https://wiki.archlinux.org/index.php/kernel_mode_setting
> >>> for more info. basically add video=TV-1:d to disable the output in
> >>> question. Replace TV-1 with whatever connector you want to disable.
> >>
> >>
> >> I tried adding video=DVI-D-1:d to the kernel command line.
> >>
> >> The effect is while the second output is indeed disabled, the
> >> framebuffer console still takes the second output's resolution
> >> into account and the boot splash is still using only the top-left
> >> 800x480 part of the 1024x768 primary screen.
> >>
> >> Also, the secondary screen got disabled also in X which is not desired.
> >> Can I wake it up under X somehow? This device is using the modesetting
> >> DDX driver.
> >
> > Can you enable it via randr?
>
> I think the video= based disable forces the connector to be disabled
> irrevocably.
# echo detect > /sys/class/drm/<whatever>/status
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2017-04-13 16:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 13:03 KMS question Boszormenyi Zoltan
2017-04-13 14:05 ` Alex Deucher
2017-04-13 14:05 ` Alex Deucher
2017-04-13 15:03 ` Boszormenyi Zoltan
2017-04-13 15:03 ` Boszormenyi Zoltan
2017-04-13 15:36 ` Alex Deucher
2017-04-13 15:36 ` Alex Deucher
2017-04-13 15:37 ` Ilia Mirkin
2017-04-13 15:37 ` Ilia Mirkin
2017-04-13 16:20 ` Ville Syrjälä [this message]
2017-04-13 16:20 ` Ville Syrjälä
2017-04-13 17:32 ` Boszormenyi Zoltan
2017-04-13 17:32 ` Boszormenyi Zoltan
2017-04-13 15:48 ` Boszormenyi Zoltan
2017-04-13 15:48 ` Boszormenyi Zoltan
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=20170413162031.GW30290@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=imirkin@alum.mit.edu \
--cc=linux-kernel@vger.kernel.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 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.