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 22:30:05 +0100	[thread overview]
Message-ID: <20130819213005.GA30211@srcf.ucam.org> (raw)
In-Reply-To: <1376946411.5087.2.camel@shinybook.infradead.org>

On Mon, Aug 19, 2013 at 10:06:51PM +0100, David Woodhouse wrote:

> You effectively seem to be suggesting that nothing will ever get better
> on the UEFI side, and the only benefit of the plugfest is that we get to
> see the latest brokenness and try to come up with a workaround for it
> before the consumers are afflicted with it?

Pretty much. There's a decent chance that board vendors already have the 
broken code before we end up testing against it.

> That's a really pessimistic view, and I'd really like us to be a little
> more optimistic. Things can't be, or at least can't *stay*, that bad.
> Surely?

Most vendors don't care about testing against Linux, and we can't make 
them care. What they're more likely to test against is the SCT, and 
extending that to cover a wider range of test cases (such as exhausting 
variable space) is much more likely to result in things being caught 
before anything is shipped - but even then, board vendors are going to 
take IBV code, perform "value add", never run a test suite and just make 
sure it boots Windows.

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

  reply	other threads:[~2013-08-19 21:30 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
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 [this message]
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=20130819213005.GA30211@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).