From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
by finch.gentoo.org with esmtp (Exim 4.60)
(envelope-from <gentoo-dev+bounces-52801-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1Shw22-0002tO-2j
for garchives@archives.gentoo.org; Fri, 22 Jun 2012 05:03:42 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 2221CE0D04;
Fri, 22 Jun 2012 05:03:29 +0000 (UTC)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
by pigeon.gentoo.org (Postfix) with ESMTP id 47CC1E0CED
for <gentoo-dev@lists.gentoo.org>; Fri, 22 Jun 2012 05:02:35 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp.gentoo.org (Postfix) with ESMTP id CEC501B400B
for <gentoo-dev@lists.gentoo.org>; Fri, 22 Jun 2012 05:02:34 +0000 (UTC)
X-Virus-Scanned: by amavisd-new using ClamAV at gentoo.org
X-Spam-Flag: NO
X-Spam-Score: -2.484
X-Spam-Level:
X-Spam-Status: No, score=-2.484 tagged_above=-999 required=5.5
tests=[AWL=-0.572, BAYES_00=-1.9, SPF_HELO_PASS=-0.001,
SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from smtp.gentoo.org ([127.0.0.1])
by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id D4ymzCHF_7oH for <gentoo-dev@lists.gentoo.org>;
Fri, 22 Jun 2012 05:02:28 +0000 (UTC)
Received: from plane.gmane.org (plane.gmane.org [80.91.229.3])
(using TLSv1 with cipher AES256-SHA (256/256 bits))
(No client certificate requested)
by smtp.gentoo.org (Postfix) with ESMTPS id 478791B4019
for <gentoo-dev@gentoo.org>; Fri, 22 Jun 2012 05:02:27 +0000 (UTC)
Received: from list by plane.gmane.org with local (Exim 4.69)
(envelope-from <lnx-gentoo-dev@m.gmane.org>)
id 1Shw0k-0002KF-96
for gentoo-dev@gentoo.org; Fri, 22 Jun 2012 07:02:22 +0200
Received: from ip68-231-22-224.ph.ph.cox.net ([68.231.22.224])
by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
id 1AlnuQ-0007hv-00
for <gentoo-dev@gentoo.org>; Fri, 22 Jun 2012 07:02:22 +0200
Received: from 1i5t5.duncan by ip68-231-22-224.ph.ph.cox.net with local (Gmexim 0.1 (Debian))
id 1AlnuQ-0007hv-00
for <gentoo-dev@gentoo.org>; Fri, 22 Jun 2012 07:02:22 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: gentoo-dev@lists.gentoo.org
From: Duncan <1i5t5.duncan@cox.net>
Subject: [gentoo-dev] Re: Killing UEFI Secure Boot
Date: Fri, 22 Jun 2012 05:02:13 +0000 (UTC)
Message-ID: <pan.2012.06.22.05.02.14@cox.net>
References: <4FE0F922.2090807@gentoo.org>
<CAGfcS_kY8S_M28jYbgeB-N+4gSD45OFJ74LhOOfUZSDt32T+yw@mail.gmail.com>
<4FE1230D.8090502@gentoo.org>
<1a28c6af40914cf5b6b5559bd0195a1b@HUBCAS1.cs.stonybrook.edu>
<4FE24BB7.3000904@gentoo.org> <pan.2012.06.21.08.08.39@cox.net>
<4FE2EA62.1090407@gentoo.org>
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
X-Complaints-To: usenet@dough.gmane.org
X-Gmane-NNTP-Posting-Host: ip68-231-22-224.ph.ph.cox.net
User-Agent: Pan/0.138 (Der Geraet; GIT f50ed2b
/usr/src/portage/src/egit-src/pan2)
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt: 94ed9c0d-f3c5-45ee-8b86-73e14a2e55a5
X-Archives-Hash: 6aa85237295cd091501df6adc6110113
Richard Yao posted on Thu, 21 Jun 2012 05:33:22 -0400 as excerpted:
> A firmware replacement for the BIOS does not need to worry about floppy
> drives, hard drives, optical drives, usb devices, isa devices, pci
> devices and pci express drives, etcetera, because those live on buses,
> which the kernel can detect.
But you have to be able to load the kernel first, before it can do all=20
that detection. And to load it, you need to be able to read the device=20
it's located on, which in a modern x86 system (as contrasted with mips/
arm) generally means detection of what's there, some mechanism to choose=20
which available devices to check for a kernel or boot loader or whatever,=
=20
and some way to dynamically configure it, since many devices are simply=20
(device info probable) bricks until configured, these days.
Sure, you can boot directly to a Linux kernel /as/ your firmware (as Ian=20
S suggested), but then you're back to hard-configuring it in ordered to=20
do so, thus losing all that extra flexibility that's part of what makes=20
x86 different. Which was the question that I was addressing.
--=20
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman