From owner-freebsd-arch@freebsd.org Mon Jun 25 15:47:53 2018 Return-Path: Delivered-To: freebsd-arch@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 9C73910142FD for ; Mon, 25 Jun 2018 15:47:53 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3719D826EB for ; Mon, 25 Jun 2018 15:47:53 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id EBAEA10142FC; Mon, 25 Jun 2018 15:47:52 +0000 (UTC) Delivered-To: arch@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 D9F1310142FB for ; Mon, 25 Jun 2018 15:47:52 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 57DC7826EA for ; Mon, 25 Jun 2018 15:47:52 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTP id w5PFlelU048986; Mon, 25 Jun 2018 18:47:43 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w5PFlelU048986 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w5PFleEw048985; Mon, 25 Jun 2018 18:47:40 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 25 Jun 2018 18:47:40 +0300 From: Konstantin Belousov To: Warner Losh Cc: Poul-Henning Kamp , "freebsd-arch@freebsd.org" Subject: Re: UEFI Plans / Shifts -- RFC Message-ID: <20180625154740.GF2430@kib.kiev.ua> References: <19341.1529917294@critter.freebsd.dk> <20180625091844.GC2430@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.0 (2018-05-17) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2018 15:47:53 -0000 On Mon, Jun 25, 2018 at 07:37:19AM -0600, Warner Losh wrote: > On Mon, Jun 25, 2018 at 3:18 AM, Konstantin Belousov > wrote: > > > On Mon, Jun 25, 2018 at 09:01:34AM +0000, Poul-Henning Kamp wrote: > > > -------- > > > In message > gmail.com> > > > , Warner Losh writes: > > > > > > >So here's my open questions: > > > >(1) Do I need to parse boot.conf? > > > > > > I can't see how it would add any value on top of UEFI and reading it > > > will just keeping old workarounds alive another decade for no good > > reason. > > > > An obvious values is to have serial console earlier than loader.conf is > > parsed. At least on typical desktop motherboards which do not have > > serial bios redirection, this is important. > > > > This won't work until AFTER we add ACPI to the boot loader. Why ?