public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Information about EFI.
Date: Tue, 05 Dec 2000 21:17:14 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205786@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205775@msgid-missing>

>>>>> On Tue, 28 Nov 2000 14:42:42 +0530, "Sapariya Manish.j" <S.Manish@zensar.com> said:

  Sapariya> Hi all, I dont know whethere this is the correct place to
  Sapariya> ask this question or not but i couldnt get it anywhere
  Sapariya> else.

  Sapariya> The question is about EFI bios32/ia64 emulator for 32 bit
  Sapariya> systems.

  Sapariya> I want to write a exception handler for my application
  Sapariya> written in EFI.  Right now i dont have access to 64 bit
  Sapariya> machine thats why i am trying it on 32 bit machine.

  Sapariya> But i could nt get any information about how could i do
  Sapariya> it.

  Sapariya> Any suggestions will be of great help.

Intel has (had?) an EFI implementation for IA-32 machines.  You put
that on a floppy disk, boot the system with it, and you get an EFI
prompt (nshell prompt, to be exact).  From there you can launch your
own EFI programs.  The GNU EFI support has support for building IA-32
EFI applications, but it hasn't been tested in a while (not since I
got IA-64 hw to play with, to be exact).  However, provided you have a
toolchain that builds valid IA-64 EFI applications, I think it's very
likely that the IA-32 side will also work, so it may be worth a try.

Hope this helps,

	--david


  reply	other threads:[~2000-12-05 21:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-28  9:24 [Linux-ia64] Information about EFI Sapariya Manish.j
2000-12-05 21:17 ` David Mosberger [this message]
2000-12-05 23:51 ` Govezensky, Yosi

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-105590678205786@msgid-missing \
    --to=davidm@hpl.hp.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