From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: Enabling i915.fastboot=1 by default
Date: Wed, 6 Jun 2018 11:36:09 +0200 [thread overview]
Message-ID: <385ee284-ceaa-df5d-ca10-4f264dd87da5@linux.intel.com> (raw)
In-Reply-To: <693eabb3-7a1d-d1c9-e3a9-ff9f58ab05c0@redhat.com>
Op 06-06-18 om 11:09 schreef Hans de Goede:
> Hi All,
>
> So I'm working on making Linux boot in a complete
> flickerfree manner (no modesets, no black screens).
>
> I have this working on various machines with Intel
> gfx, but I need to pass i915.fastboot=1 on the kernel
> commandline.
>
> I know there was some talk about enabling this by
> default a while ago, but it seems that that still
> has not happened (yet?).
>
> I'm wondering what is holding this back ? Maybe we
> can change it from a bool to an int, init it to -1
> and when it is -1 have some automatic detection
> code which disables it where it is known to be
> troublesome and otherwise enables it by default?
Main reason are bugs like https://bugs.freedesktop.org/show_bug.cgi?id=103781 and our hw
readout not being perfect. On some haswell/broadwell eDP laptops we stop generating vblanks
when we fastboot, and in general we don't trust our code enough for that.
The automatic detection code is already in place, we modeset if the mode is not compatible
enough, but we don't catch all the cases where this might happen.
~Maarten
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-06-06 9:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 9:09 Enabling i915.fastboot=1 by default Hans de Goede
2018-06-06 9:36 ` Maarten Lankhorst [this message]
2018-06-06 9:54 ` Hans de Goede
2018-06-06 10:43 ` Maarten Lankhorst
2018-06-06 12:12 ` Hans de Goede
2018-06-06 18:12 ` Rodrigo Vivi
2018-06-07 9:11 ` Hans de Goede
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=385ee284-ceaa-df5d-ca10-4f264dd87da5@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=intel-gfx@lists.freedesktop.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.