From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jesse Barnes <jbarnes@sgi.com>
Date: Wed, 19 Jan 2005 18:21:25 +0000
Subject: Re: pgprot_writecombine & shub 1.x
Message-Id: <200501191021.25589.jbarnes@sgi.com>
List-Id: <linux-ia64.vger.kernel.org>
References: <200501111200.02504.jbarnes@sgi.com>
In-Reply-To: <200501111200.02504.jbarnes@sgi.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: linux-ia64@vger.kernel.org

On Wednesday, January 19, 2005 10:16 am, Luck, Tony wrote:
> >Oh, I thought I said that in the first message, I'm talking
> >about I/O memory here.  In any event though, we shouldn't be
> >mapping anything with the WC attribute that the EFI memory
> >map doesn't allow.
>
> Does the EFI memory map help here?  Is I/O memory included
> in the efi memory map?  What about the hot-plug case ... the
> EFI memory map isn't updated for new i/o memory that appears
> when you plug in a new card?

I think it's supposed to appear as memory mapped I/O or memory mapped I/O port 
space in the EFI memory map.  Shouldn't the map be updated in the case of 
hotplug?

Jesse