Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757845AbYAAWlF (ORCPT ); Tue, 1 Jan 2008 17:41:05 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755244AbYAAWkz (ORCPT ); Tue, 1 Jan 2008 17:40:55 -0500 Received: from terminus.zytor.com ([198.137.202.10]:55334 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754925AbYAAWkz (ORCPT ); Tue, 1 Jan 2008 17:40:55 -0500 Message-ID: <477AC130.3050901@zytor.com> Date: Tue, 01 Jan 2008 14:39:44 -0800 From: "H. Peter Anvin" User-Agent: Thunderbird 2.0.0.9 (X11/20071115) MIME-Version: 1.0 To: Rene Herman CC: Alan Cox , "David P. Reed" , Rene Herman , Ingo Molnar , Paul Rolland , Pavel Machek , Thomas Gleixner , linux-kernel@vger.kernel.org, Ingo Molnar , rol@witbe.net Subject: Re: [PATCH] x86: provide a DMI based port 0x80 I/O delay override. References: <4762C551.5070003@zytor.com> <20071214210652.GB28793@elf.ucw.cz> <4763001A.1070102@zytor.com> <20071214232955.545ab809@the-village.bc.nu> <20071215080831.404cdb32@tux.DEF.witbe.net> <47638C8C.2090604@gmail.com> <476438B4.2020600@zytor.com> <476462BE.3030701@gmail.com> <4764687D.6080609@zytor.com> <476524DB.7020806@gmail.com> <20071216152250.GA21245@elte.hu> <4765D43E.1010800@gmail.com> <4765D95C.4010404@zytor.com> <4765DCB0.8030901@gmail.com> <4765EE7F.80002@zytor.com> <47667366.7010405@gmail.com> <4766AE88.4080904@zytor.com> <4766D175.7040807@reed.com> <20071217212509.5edaa372@the-village.bc.nu> <477A634C.8040000@reed.com> <20080101161557.3ce2d5f8@the-village.bc.nu> <477AAD7B.5040405@zytor.com> <477AB204.3070904@keyaccess.nl> <477AB433.5070506@zytor.com> <477AC02A.40108@keyaccess.nl> In-Reply-To: <477AC02A.40108@keyaccess.nl> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 937 Lines: 29 Rene Herman wrote: >> >> Yes, we do. It's exactly this side effect which makes this safer than >> either 0x80 or 0xED -- it's a port that *guaranteed* can't be >> reclaimed for other purposes without breaking MS-DOS compatibility. > > I see that with CR0.NE set (*) we indeed don't care about IGNNE#... > > However, I'm worried about this comment in arch/x86/kernel/i8259_32.c > > === > /* > * New motherboards sometimes make IRQ 13 be a PCI interrupt, > * so allow interrupt sharing. > */ > === > > Is it really safe to just blindly negate IRQ13 on everything out there, > from regular PC through funky embedded thingies? > It's not any IRQ 13, it's IRQ 13 from the FPU. -hpa -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/