Re: Call for Testing: UEFI Changes

From: Kyle Evans <kevans_at_freebsd.org>
Date: Tue, 3 Apr 2018 15:48:03 -0500
On Tue, Apr 3, 2018 at 3:17 PM, Kyle Evans <kevans_at_freebsd.org> wrote:
> Hi,
>
> Right- so, `gop set 0` should've immediately cleared your screen and
> put it into 1920x1080, full stop. If it did not, I think that's
> indicative of some kind of interestingly broken firmware...
>
> Regardless! We're clearly bad at trying to set a mode before the
> kernel starts, so r331904 sets the default max resolution in such a
> way that we just don't change the resolution by default anymore and
> interested parties can bump that up if they want to try it. This
> Thursday's snapshots should have this included.

After reviewing the video again and discussing it with manu, I don't
think that commit's going to solve your problem at all... we'll need
to re-think this one a bit more.

> I think if we're going to change modes as a default, we should have
> some way for vt/efifb to use EFIRT or be notified by EFIRT of
> supported resolutions so that vt/efifb can hopefully just handle it
> all and do it properly. This approach would be more similar I guess to
> how KMS drivers operate, and less fragile than what we're seeing with
> these different approaches we've taken.
>
Received on Tue Apr 03 2018 - 18:48:26 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:15 UTC