From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: [PATCH 0/4] Reintroduce OVMF support Date: Wed, 16 Oct 2013 13:52:43 +0100 Message-ID: <525E8C1B.9060206@cantab.net> References: <1381855205-3329-1-git-send-email-wei.liu2@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1381855205-3329-1-git-send-email-wei.liu2@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Wei Liu Cc: ian.jackson@eu.citrix.com, ian.campbell@citrix.com, xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 15/10/13 17:40, Wei Liu wrote: > This small series reintroduces OVMF support in Xen I think somewhere in this series there needs to a brief description of what OVMF is. With the exception of the first patch this is just adding yet another component to clone and build. Why is this useful? Why isn't (effectively) --with-system-ovmf always enabled (and thus not actually needed as an option)? Isn't Xen's keenness to build it's own particular versions of stuff something that causes significant problems for distributions? David