On 25.04.2008 04:03, joe@settoplinux.org wrote:
I noticed this problem, if certian devices are disabled (like onboard vga for example). The other enabled devices try to use 0xfec00000 for memory allocation, causing APIC to fail.
You just need to add a Signed-Off-By as stated in the development guidelines. In the mean time I will test it and if all goes well you'll
get
my Acked-by, and then it can be commited.
Oh, I see.
Signed-off-by: Aaron Lwe aaron.lwe@gmail.com
Acked-by: Joseph Smith joe@settoplinux.org
Great job Aaron! Works great, attached is the bootlog with vga (device 2.0)
completly disabled, and coreboot is not trying to allocate the 0xfec00000 range.
commited in r3265
Can you check whether this should be applied to the v3 code as well?
Assuming, device.c has the same functions as v2 it probibly should be applied. Can someone running v3 test the patch?