From: "Andi Kleen" <ak@suse.de>
The original check was apparently to work around some old BIOS bugs and we
just assume x86-64 machines don't have this class of problems.
Originally found by <YhLu@tyan.com>
Signed-off-by: Andi Kleen <ak@suse.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
---
25-akpm/arch/x86_64/kernel/io_apic.c | 7 -------
1 files changed, 7 deletions(-)
diff -puN arch/x86_64/kernel/io_apic.c~x86_64-remove-check-that-limited-max-number-of-io-apic arch/x86_64/kernel/io_apic.c
--- 25/arch/x86_64/kernel/io_apic.c~x86_64-remove-check-that-limited-max-number-of-io-apic 2005-01-09 23:01:35.229027480 -0800
+++ 25-akpm/arch/x86_64/kernel/io_apic.c 2005-01-09 23:01:35.233026872 -0800
@@ -1160,13 +1160,6 @@ static void __init setup_ioapic_ids_from
old_id = mp_ioapics[apic].mpc_apicid;
- if (mp_ioapics[apic].mpc_apicid >= 0xf) {
- apic_printk(APIC_QUIET,KERN_ERR "BIOS bug, IO-APIC#%d ID is %d in the MPC table!...\n",
- apic, mp_ioapics[apic].mpc_apicid);
- apic_printk(APIC_QUIET,KERN_ERR "... fixing up to %d. (tell your hw vendor)\n",
- reg_00.bits.ID);
- mp_ioapics[apic].mpc_apicid = reg_00.bits.ID;
- }
printk(KERN_INFO "Using IO-APIC %d\n", mp_ioapics[apic].mpc_apicid);
_