All of lore.kernel.org
 help / color / mirror / Atom feed
From: Attilio Rao <attilio.rao@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Keir Fraser <keir.xen@gmail.com>, "Tim (Xen.org)" <tim@xen.org>,
	"g@phlegethon.org" <g@phlegethon.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Build failure in OVMF
Date: Thu, 22 Mar 2012 14:48:44 +0000	[thread overview]
Message-ID: <4F6B3BCC.9080704@citrix.com> (raw)
In-Reply-To: <1332425282.8817.82.camel@zakaz.uk.xensource.com>

On 22/03/12 14:08, Ian Campbell wrote:
> On Thu, 2012-03-22 at 13:58 +0000, Keir Fraser wrote:
>    
>> On 22/03/2012 13:15, "Tim Deegan"<tim@xen.org>  wrote:
>>
>>      
>>> At 13:07 +0000 on 22 Mar (1332421679), Attilio Rao wrote:
>>>        
>>>> Actually CONFIG_OVMF should be disabled by default, can you please check
>>>> how is in your case?
>>>>          
>>> whitby:xen-unstable.hg$ grep CONFIG_OVMF Config.mk
>>> CONFIG_OVMF ?= $(CONFIG_Linux)
>>>
>>>    changeset:   25077:6bf50858c3c5
>>>    user:        Attilio Rao<attilio.rao@citrix.com>
>>>    date:        Thu Mar 22 10:26:03 2012 +0000
>>>    summary:     Fetch the OVMF repository from specific git mirror and enable
>>> it
>>>
>>>        
>>>> Also, did you apply the OVMF v4 patch for enabling the CONFIG_OVMF on?
>>>>          
>>> Nope, AFAICT I have no local patches.
>>>        
>> I applied the OVMF-enable patch this morning, hence Tim's problem. I might
>> have applied v3 rather than v4 though? Please check.
>>      
> I think that was supposed to be an RFC pending a build fix getting
> committed to OVMF upstream.
>
>    

Yes, we need v4 which also contains explicit showstopping informations 
based on a OVMF patch pending.

Thus, likely we should revert v3 inclusion, wait another couple of days 
for Tianocore people to reply, eventually push the tianocore patch in 
our mirror and in the end apply v4.

Attilio

  reply	other threads:[~2012-03-22 14:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22 12:59 Build failure in OVMF Tim Deegan
2012-03-22 13:07 ` Attilio Rao
2012-03-22 13:15   ` Tim Deegan
2012-03-22 13:58     ` Keir Fraser
2012-03-22 14:08       ` Ian Campbell
2012-03-22 14:48         ` Attilio Rao [this message]
2012-03-22 15:23       ` Attilio Rao
2012-03-22 14:55 ` Tim Deegan
2012-03-22 15:04   ` Ian Campbell
2012-03-22 15:16     ` Tim Deegan
2012-03-26  9:37       ` Ian Campbell
2012-03-22 15:20   ` Attilio Rao
2012-04-02 19:07 ` Jordan Justen

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=4F6B3BCC.9080704@citrix.com \
    --to=attilio.rao@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=g@phlegethon.org \
    --cc=keir.xen@gmail.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.