From owner-freebsd-current@freebsd.org Tue Apr 3 20:48:26 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CC8B2F7F1FD for ; Tue, 3 Apr 2018 20:48:26 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: from mail-lf0-f47.google.com (mail-lf0-f47.google.com [209.85.215.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3550C7332D for ; Tue, 3 Apr 2018 20:48:26 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: by mail-lf0-f47.google.com with SMTP id u3-v6so22128659lff.5 for ; Tue, 03 Apr 2018 13:48:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ZtCHwn9TnY2PqHIEmq9Z29+H92r2Cs230tk0ZSOEMdM=; b=cJ3W5eZzHs+7a4jCg71eypzIRhI7kE/QCt0psbpn+Kz1Xc/cgVa+erUN4I8frO41U0 soH0BqjKLwVEeeR3HbNUEb1za+lh37f0cgwNA5RQean9LjvmMyBDa8S14rslAChpYn0N 0gYC+8WtkQT9rdsIvPQG+acwvbJnYr2ECJTdF/CyTEwcSJmK2Qb4E1gtEC+lvowG7d3K PL69pLFbzmo4HJDPXFEr3MQSPr8ktXoPR4bg3PuIw9VYIbhVtErUFkvaA/yNj73PoSiW mnoTWDFVJQJ0C9Vw/AUyzFJd11fjaq91CNFO4GtxzoJU7N24/pyFghDJGpqk4pB76amH 5lZg== X-Gm-Message-State: ALQs6tAM6zoEJlJXtGWobbm4qrS4NBjpYnjD0oEAcstk7aKiPl+fl+Ul elg6aSgTkaSKFWj8rsyZw2UmSXmY X-Google-Smtp-Source: AIpwx48EFZddkG19/y8aSAgfABexpT17n2UlE+dJSW7+gW0dqZRu3UmShKPrGfGAWmakwUMR+SBszg== X-Received: by 2002:a19:511d:: with SMTP id f29-v6mr9216464lfb.39.1522788504021; Tue, 03 Apr 2018 13:48:24 -0700 (PDT) Received: from mail-lf0-f48.google.com (mail-lf0-f48.google.com. [209.85.215.48]) by smtp.gmail.com with ESMTPSA id f24sm613610ljj.76.2018.04.03.13.48.23 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Apr 2018 13:48:23 -0700 (PDT) Received: by mail-lf0-f48.google.com with SMTP id q9-v6so2630179lfk.9 for ; Tue, 03 Apr 2018 13:48:23 -0700 (PDT) X-Received: by 2002:a19:b516:: with SMTP id e22-v6mr9597809lff.47.1522788503674; Tue, 03 Apr 2018 13:48:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.129.90 with HTTP; Tue, 3 Apr 2018 13:48:03 -0700 (PDT) In-Reply-To: References: <5f663141-433c-951d-a350-7369b004415f@alvermark.net> <20180322225644.1480251c4547ce30f3d88de9@dec.sakura.ne.jp> <20180401213831.1535c7511c1d95a258318bc7@dec.sakura.ne.jp> From: Kyle Evans Date: Tue, 3 Apr 2018 15:48:03 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Call for Testing: UEFI Changes To: Zaphod Beeblebrox Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Apr 2018 20:48:27 -0000 On Tue, Apr 3, 2018 at 3:17 PM, Kyle Evans 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. >