All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Wedgwood <cw@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] (2.4.21-bjorn-bk) Minimalist PAL mapping for SN2
Date: Tue, 22 Jul 2003 21:26:24 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105890923804797@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105832171829546@msgid-missing>

On Wed, Jul 16, 2003 at 08:22:37AM -0700, Luck, Tony wrote:

> I tried some similar code for Tiger a while ago, but ran into a
> problem as there is other code in the same granule, that isn't
> covered by the address range for PAL routines (I think that the
> other code was the EFI loaded FPSWA code, but I didn't look too
> closely at the time this happened).

Can you send me the memmap for this situation if possible please?

I have an algorithmic approach that should work everywhere but
obviously this requires that *ANY* code executed WB in the same
granule be visible in the EFI memory map so I can be sure to include
those when trying to find the minimum suitable TR to use.

The kicker here of course is that if some code is omitted (not
delcared) in the EFI memory map but actively used...  does anyone do
this?



  --cw

      parent reply	other threads:[~2003-07-22 21:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-16  2:14 [PATCH] (2.4.21-bjorn-bk) Minimalist PAL mapping for SN2 Christopher Wedgwood
2003-07-16 15:22 ` Luck, Tony
2003-07-16 18:23 ` Christopher Wedgwood
2003-07-17 17:42 ` Bjorn Helgaas
2003-07-17 17:57 ` Christopher Wedgwood
2003-07-17 22:52 ` Bjorn Helgaas
2003-07-18  2:22 ` Christopher Wedgwood
2003-07-18 16:13 ` Bjorn Helgaas
2003-07-19  1:05 ` Christopher Wedgwood
2003-07-22  1:38 ` Bjorn Helgaas
2003-07-22 21:26 ` Christopher Wedgwood [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-105890923804797@msgid-missing \
    --to=cw@sgi.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 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.