From: Pavel Machek Date: Wed, 26 Nov 2008 16:15:27 +0000 (+0100) Subject: aperture_64.c: clarify that too small aperture is valid reason for this code X-Git-Tag: v2.6.29-rc1~587^2~2^2~5 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=8caac56305cef98f9357b060a77939d17699937d;p=profile%2Fivi%2Fkernel-x86-ivi.git aperture_64.c: clarify that too small aperture is valid reason for this code Impact: update comment Clarify that too small aperture is valid reason for this code. Signed-off-by: Pavel Machek Signed-off-by: Ingo Molnar --- diff --git a/arch/x86/kernel/aperture_64.c b/arch/x86/kernel/aperture_64.c index 9a32b37..676debf 100644 --- a/arch/x86/kernel/aperture_64.c +++ b/arch/x86/kernel/aperture_64.c @@ -1,8 +1,9 @@ /* * Firmware replacement code. * - * Work around broken BIOSes that don't set an aperture or only set the - * aperture in the AGP bridge. + * Work around broken BIOSes that don't set an aperture, only set the + * aperture in the AGP bridge, or set too small aperture. + * * If all fails map the aperture over some low memory. This is cheaper than * doing bounce buffering. The memory is lost. This is done at early boot * because only the bootmem allocator can allocate 32+MB.