xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Attilio Rao <attilio.rao@citrix.com>
To: "Ian Jackson" <Ian.Jackson@eu.citrix.com>,
	"Ian Campbell" <Ian.Campbell@citrix.com>,
	"Christoph Egger" <Christoph.Egger@amd.com>,
	"Roger Pau Monné" <roger.pau@entel.upc.edu>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] [PATCH v3] Fetch the OVMF repository from specific git mirror and enable it
Date: Mon, 19 Mar 2012 17:50:44 +0000	[thread overview]
Message-ID: <4F6771F4.1060607@citrix.com> (raw)
In-Reply-To: <4F676FA9.3090401@citrix.com>


[-- Attachment #1.1: Type: text/plain, Size: 1931 bytes --]

On 19/03/12 17:40, Attilio Rao wrote:
> On 19/03/12 16:36, Ian Jackson wrote:
>> Attilio Rao writes ("Re: [Xen-devel] [PATCH] [PATCH v3] Fetch the OVMF repository from specific git mirror and enable it"):
>>    
>>> I think I see the issue here. Are you running with i486 as an arch?
>>> This is a deficiency of the OVMF support, because it has some wrappers
>>> to build appropriately the firmware which are OS and architectures
>>> specific and it does support Linux-i686 and Linux-x86_64 but not Linux-i486.
>>> I'm not sure about what we should do here, possible options include:
>>> - Verify that, on all i486,i586,etc. we can eventually use i686 and
>>> unify the script to do that
>>>      
>> Surely it's just wanting to know roughly what architecture to build
>> for.  The difference between i686 and i486 isn't relevant here.
>> (I hope.  If it is then we have other problems because this is tested
>> at build-time and might be run on a different kernel to the one it's
>> built on.)
>>
>> So I think this is the right thing to do.
>>
>>    
>
> Here is my take on OVMF for what is needed:
> http://xenbits.xen.org/people/attilio/ovmf-xen-arches.patch 
> <http://xenbits.xen.org/people/attilio/ovmf-xen-arches.patch>
>
> This should at least fix tianocore to build on all i*86 Linux flavours.
> Unfortunately I don't have a NetBSD machine to test it out, so if 
> Christoph and/or Roger can apply this patch to ovmf and try the 
> original patch on this thread (and verify NetBSD can build ok) I'll 
> propose this patch upstream for TIANOCORE, otherwise I will just send 
> out a patch with OVMF disabled until NetBSD is not tested.
>

To be more precise, you don't even need the patch at the beginning of 
the thread, all you need to do to test you can build OVMF on NetBSD is:
- git clone git://xenbits.xen.org/ovmf.git
- apply the patch above
- cd ovmf/OvmfPkg/
- $ ./build.sh
- $ ./build.sh -a X64

Thanks,
Attilio

[-- Attachment #1.2: Type: text/html, Size: 2656 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2012-03-19 17:50 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-01 19:28 [PATCH] [PATCH v3] Fetch the OVMF repository from specific git mirror and enable it Attilio Rao
2012-03-14 12:08 ` Ian Jackson
2012-03-14 13:14   ` Attilio Rao
2012-03-17 22:33   ` Attilio Rao
2012-03-19 16:36     ` Ian Jackson
2012-03-19 17:40       ` Attilio Rao
2012-03-19 17:50         ` Attilio Rao [this message]
2012-03-20 10:06           ` Christoph Egger
2012-03-20 10:47             ` Attilio Rao
2012-03-20 11:04               ` Christoph Egger
2012-03-20 11:11                 ` Roger Pau Monné
2012-03-20 11:09             ` Attilio Rao
2012-03-20 11:57               ` Christoph Egger
2012-03-20 12:12                 ` Attilio Rao
2012-03-20 13:52                   ` Christoph Egger
2012-03-20 16:30                     ` Ian Jackson
2012-03-20 16:44                       ` Christoph Egger
2012-03-14 13:10 ` Ian Campbell
2012-03-14 13:14   ` Attilio Rao
2012-03-14 14:11   ` Ian Jackson
2012-03-14 14:21     ` Ian Campbell
2012-03-20 11:16 ` Roger Pau Monné
2012-03-20 11:28   ` Attilio Rao

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=4F6771F4.1060607@citrix.com \
    --to=attilio.rao@citrix.com \
    --cc=Christoph.Egger@amd.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=roger.pau@entel.upc.edu \
    --cc=xen-devel@lists.xensource.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).