Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754893AbYAQNgT (ORCPT ); Thu, 17 Jan 2008 08:36:19 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751263AbYAQNgI (ORCPT ); Thu, 17 Jan 2008 08:36:08 -0500 Received: from hawking.rebel.net.au ([203.20.69.83]:41769 "EHLO hawking.rebel.net.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750953AbYAQNgH (ORCPT ); Thu, 17 Jan 2008 08:36:07 -0500 Message-ID: <478F59CC.8050907@davidnewall.com> Date: Fri, 18 Jan 2008 00:06:12 +1030 From: David Newall User-Agent: Thunderbird 2.0.0.6 (X11/20071022) MIME-Version: 1.0 To: Alan Cox CC: "David P. Reed" , David Woodhouse , Rene Herman , Zachary Amsden , "H. Peter Anvin" , Christer Weinigel , Ondrej Zary , Bodo Eggert <7eggert@gmx.de>, Ingo Molnar , Paul Rolland , Pavel Machek , Thomas Gleixner , linux-kernel@vger.kernel.org, Ingo Molnar , rol Subject: Re: [linux-kernel] Re: [PATCH] x86: provide a DMI based port 0x80 I/O delay override. References: <9BdU5-1YW-9@gated-at.bofh.it> <200801081810.58904.linux@rainbow-software.org> <4783B1B2.6070005@reed.com> <200801081838.16241.linux@rainbow-software.org> <4783C4A6.9060402@reed.com> <20080108185120.3ff7ed18@lxorguk.ukuu.org.uk> <4783CBD9.7020709@reed.com> <1199847162.7369.323.camel@bodhitayantram.eng.vmware.com> <47845972.9090803@zytor.com> <1199915614.7369.367.camel@bodhitayantram.eng.vmware.com> <47854916.4080703@reed.com> <1200015388.6192.22.camel@bodhitayantram.eng.vmware.com> <4786DD05.20804@keyaccess.nl> <47877ECD.9060408@reed.com> <1200347847.2647.97.camel@shinybook.infradead.org> <478BE08B.3090306@reed.com> <478E1668.9040404@davidnewall.com> <20080116145515.6d84dc7b@lxorguk.ukuu.org.uk> <478E57C8.2080403@davidnewall.com> <20080116200829.26040351@lxorguk.ukuu.org.uk> <478EF4C9.8030406@davidnewall.com> <20080117120227.3d09baf5@lxorguk.ukuu.org.uk> In-Reply-To: <20080117120227.3d09baf5@lxorguk.ukuu.org.uk> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1250 Lines: 28 Alan Cox wrote: >> This is a timing issue, isn't it? How are we synchronising, other than >> by delaying for a (bus-dependant) period? The characteristics of each >> bus are known so a number can be assigned for "one bus cycle", without >> having to use the bus. >> > > The characteristics of the bus are not known. It could be anything > between 6 and about 16MHz. In the early days of clone PCs, as you know but perhaps many on this list might not, the bus speed could be changed, but this was user-selectable. For such a machine, delay values can be pre-calculated for each bus speed, and a kernel parameter set accordingly. Or are you saying that the characteristics of the bus on a given machine vary for reasons other than user selection? The fact that busses run at different speeds on different machines is not a problem because the delay value can be determined for each given machine. The question is, for a given machine, can we determine a delay value instead of using a junk I/O? -- 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/