From: Tristan Gingold <tgingold@free.fr>
To: kvm-ia64@vger.kernel.org
Subject: Re: EFI image - SAL_DESC_PLATFORM_FEATURE bits
Date: Wed, 28 Jan 2009 10:33:59 +0000 [thread overview]
Message-ID: <20090128103359.GA6781@gingold.org> (raw)
In-Reply-To: <497F2BDD.7030307@sgi.com>
On Wed, Jan 28, 2009 at 11:22:34AM +0100, Jes Sorensen wrote:
> Tristan Gingold wrote:
>> On Wed, Jan 28, 2009 at 10:50:41AM +0100, Jes Sorensen wrote:
>>> Hi Tristan,
>>>
>>> Thanks for the info - where do I find the firmware? Is it in the Xen
>>> hg repositories?
>>
>> Yes,
>> xenbits.xensource.com/efi-vfirmware.hg
>
> [jes@leavenworth lw]$ hg clone http://xenbits.xensource.com/efi-vfirmware.hg
> requesting all changes
> abort: HTTP Error 404: Not Found
> [jes@leavenworth lw]$
>
> Is this the correct address? It's been ages since I used mercurial, so
> maybe I have gone a little rusty.
Humm, you're right. Try:
http://xenbits.xen.org/ext/efi-vfirmware.hg
>>> I was hoping it would be a walk in the park to build, but I kinda feared
>>> you would say that. Do I need a special environment to build it, like a
>>> special pre-historic version of GCC running on RHEL 3 or something like
>>> that?
>> Worse: you need a java environment.
>> Recent versions of TianoCore uses python (which must be much easier to build)
>> but I haven't time to update.
>
> Gosh, you really know how to make my day :-( I have a feeling I am going
> to regret getting into this :-)
Sorry :-)
Tristan.
next prev parent reply other threads:[~2009-01-28 10:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 15:44 EFI image - SAL_DESC_PLATFORM_FEATURE bits Jes Sorensen
2009-01-28 9:19 ` Tristan Gingold
2009-01-28 9:50 ` Jes Sorensen
2009-01-28 10:14 ` Tristan Gingold
2009-01-28 10:22 ` Jes Sorensen
2009-01-28 10:33 ` Tristan Gingold [this message]
2009-01-28 14:28 ` Jes Sorensen
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=20090128103359.GA6781@gingold.org \
--to=tgingold@free.fr \
--cc=kvm-ia64@vger.kernel.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.