public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Erdfelt <jerdfelt@valinux.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] ELI now on sourceforge
Date: Fri, 03 Mar 2000 18:21:09 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678204976@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678204973@msgid-missing>

On Fri, Mar 03, 2000, Andreas Schwab <schwab@suse.de> wrote:
> Johannes Erdfelt <jerdfelt@valinux.com> writes:
> 
> |> I've taken ELI and created a project on sourceforge.net for it.
> |> 
> |> ELI is a boot loader for EFI based systems. It was developed for, and
> |> currently only works for, Linux on ia64 systems.
> |> 
> |> I've also made a new release which mostly cleans up the allocations
> |> before exiting. It's not finished yet, for instance, ACPI data isn't
> |> freed yet, but will come soon.
> 
> I couldn't get this to compile: FPSWA_PROTOCOL is undefined.  Where and
> how is this supposed to be defined?

I had defined it in my gnu-efi/inc/efiprot.h file.

I forgot I had done that, but that raises the question where is this
supposed to be defined?

But, for right now, this patch will work:

--- eli.h.orig	Fri Mar  3 10:18:25 2000
+++ eli.h	Fri Mar  3 10:18:46 2000
@@ -1,6 +1,14 @@
 #ifndef lilo_h
 #define lilo_h
 
+#ifndef FPSWA_PROTOCOL
+/*
+ *  FPSWA library protocol
+ */
+#define FPSWA_PROTOCOL \
+	{ 0xc41b6531, 0x97b9, 0x11d3, {0x9a, 0x29, 0x0, 0x90, 0x27, 0x3f, 0xc1, 0x4d }}
+#endif
+
 static inline EFI_STATUS
 check_abort(EFI_SYSTEM_TABLE *systab)
 {

I've checked this in already to CVS

JE




      parent reply	other threads:[~2000-03-03 18:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-02 22:00 [Linux-ia64] ELI now on sourceforge Johannes Erdfelt
2000-03-03 17:41 ` Andreas Schwab
2000-03-03 18:21 ` Johannes Erdfelt [this message]

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=marc-linux-ia64-105590678204976@msgid-missing \
    --to=jerdfelt@valinux.com \
    --cc=linux-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox