linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	"John W. Linville" <linville@tuxdriver.com>,
	linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org
Subject: Re: UEFI Plugfest 2013 -- New Orleans
Date: Mon, 19 Aug 2013 21:19:52 +0100	[thread overview]
Message-ID: <20130819201952.GA28740@srcf.ucam.org> (raw)
In-Reply-To: <1376942994.2322.39.camel@shinybook.infradead.org>

On Mon, Aug 19, 2013 at 09:09:54PM +0100, David Woodhouse wrote:

> Do we really want to declare that we can only use 50% of the available
> NV storage space for *ever* more, just because some muppet thought they
> could squeeze some non-upstream "value add" into their implementation of
> the flash management? You seem to be suggesting that we should
> retrospectively write that limitation into the UEFI spec, which is a
> completely insane suggestion.

We only reserve 3K now, and testing this in the existing UEFI test kit 
would be entirely achievable. Including the ability to remove this check 
from the kernel is just an invitation for someone to build a kernel 
without it and then be surprised when their machine fucks up.

> We absolutely want to be able to draw a line under it and declare that
> any firmware built after $SOMEDATE is expected to be fixed, so we don't
> have to do these stupid workarounds, and we can make full use of the
> available space.

We have no way to guarantee that. Most board vendors don't turn up to 
the plugfests and aren't going to run anything we ship.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2013-08-19 20:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-16 15:20 UEFI Plugfest 2013 -- New Orleans John W. Linville
2013-08-17  0:44 ` James Bottomley
2013-08-19  8:25 ` David Woodhouse
2013-08-19 12:55   ` Matthew Garrett
2013-08-19 15:22     ` James Bottomley
2013-08-19 16:00       ` Matthew Garrett
2013-08-19 17:02         ` James Bottomley
2013-08-19 17:21           ` Matthew Garrett
2013-08-19 17:38             ` James Bottomley
2013-08-19 17:47               ` Matthew Garrett
2013-08-19 20:09               ` David Woodhouse
2013-08-19 20:19                 ` Matthew Garrett [this message]
2013-08-19 20:21                   ` David Woodhouse
2013-08-19 20:39                     ` Matthew Garrett
2013-08-19 21:06                       ` David Woodhouse
2013-08-19 21:30                         ` Matthew Garrett
2013-09-02  6:23                 ` Matt Fleming
2013-08-19 15:17   ` Borislav Petkov

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=20130819201952.GA28740@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).