Re: [PATCH]Fix broken VMI in 2.6.27-rc..

["H. Peter Anvin" <hpa@kernel.org>]

Zachary Amsden wrote:
> 
> That can't be done until we know the size of the hole to relocate, which
> isn't known until we probe in the first meg of memory to find the
> associated ROM.  It used to be the case that other things that poked
> around with platform specific memory and checking ROM areas lived around
> here in setup.c, so it was a nice place to put it.  With all the
> abstraction and combination and overifdeffing going on here, that might
> no longer be the case.
> 
> We could move it earlier, but then we'd need another hook to call in
> after max_low_pfn is known.
> 
> Or we could remove the dependency on max_low_pfn and just create a
> liberal linear to physical mapping for lomem which spans all possible
> low memory; then it doesn't matter so much where it is called.
> 

Okay, you lost me about halfway through that... could you perhaps 
describe the problem from the beginning, exactly what you're trying to do?

	-hpa