Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 14 Mar 2002 18:14:32 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 14 Mar 2002 18:14:22 -0500 Received: from lightning.swansea.linux.org.uk ([194.168.151.1]:41221 "EHLO the-village.bc.nu") by vger.kernel.org with ESMTP id ; Thu, 14 Mar 2002 18:14:11 -0500 Subject: Re: IO delay, port 0x80, and BIOS POST codes To: kerndev@sc-software.com (John Heil) Date: Thu, 14 Mar 2002 23:29:45 +0000 (GMT) Cc: alan@lxorguk.ukuu.org.uk (Alan Cox), hpa@zytor.com (H. Peter Anvin), linux-kernel@vger.kernel.org In-Reply-To: from "John Heil" at Mar 14, 2002 02:39:56 PM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: Alan Cox Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > > We've got one. Its 0x80. It works everywhere with only marginal non > > problematic side effects > > > > Ok, cool but does that mean you agree or disagree with a configurable > override for those of us in the minority? If we put every single requested obscure fix for one or two boxes into the kernel configuration you'd be spending weeks wading through "Handle weird APM on Dave's homebrew mediagx" and other questions. Let me suggest something else. For any kernel built with TSC assumed (586TSC +) initialize the udelay loop to something guaranteed to be at least too long for any conceivable processor and use udelay() for the I/O delay timing. Alan - 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/