From: Alex Deucher <alexdeucher@gmail.com>
To: Boszormenyi Zoltan <zboszor@pr.hu>
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 10:05:41 -0400 [thread overview]
Message-ID: <CADnq5_OhUKzj76XuDqCL4B_tC8eVifp3S4imkJpXVV+n6dG=Jg@mail.gmail.com> (raw)
In-Reply-To: <2a39d6ca-afdd-bccf-264f-132736313d2b@pr.hu>
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.
Alex
next prev parent reply other threads:[~2017-04-13 14:05 UTC|newest]
Thread overview: 8+ 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 [this message]
2017-04-13 15:03 ` Boszormenyi Zoltan
2017-04-13 15:36 ` Alex Deucher
2017-04-13 15:37 ` Ilia Mirkin
2017-04-13 16:20 ` Ville Syrjälä
2017-04-13 17:32 ` 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='CADnq5_OhUKzj76XuDqCL4B_tC8eVifp3S4imkJpXVV+n6dG=Jg@mail.gmail.com' \
--to=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zboszor@pr.hu \
/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;
as well as URLs for NNTP newsgroup(s).