From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268735AbUHTVGb (ORCPT ); Fri, 20 Aug 2004 17:06:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S268740AbUHTVGb (ORCPT ); Fri, 20 Aug 2004 17:06:31 -0400 Received: from fw.osdl.org ([65.172.181.6]:53208 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S268735AbUHTVG3 (ORCPT ); Fri, 20 Aug 2004 17:06:29 -0400 Date: Fri, 20 Aug 2004 14:05:03 -0700 From: "Randy.Dunlap" To: Pierre Ossman Cc: linux-kernel@vger.kernel.org Subject: Re: Timer allocates too many ports Message-Id: <20040820140503.67d23479.rddunlap@osdl.org> In-Reply-To: <4126600F.4050302@drzeus.cx> References: <4126600F.4050302@drzeus.cx> Organization: OSDL X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i686-pc-linux-gnu) X-Face: +5V?h'hZQPB9kW Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 20 Aug 2004 22:33:19 +0200 Pierre Ossman wrote: | Hi! Ho- | The timer in linux allocates the io ports 0x40 to 0x5F. This is causing | some problems for me since the hardware I'm writing a driver for has its | ports at 0x4E and 0x4F. In Windows the ports 0x40 to 0x43 are used for | the timer. Why does linux allocate so many more ports? Seems reasonable to me for Linux timer driver (resource) to allocate 0x40 - 0x43 and 0x50 - 0x53 (on intel x86; only 0x40 - 0x43 for AMD x86-64). At least that's what is in some Intel specs. That would be accurate AFAIK and still leave 0x4e - 0x4f available. What kind of device uses IO addresses 0x4e - 0x4f? Is it a motherboard device? Intel ICH specs think that 0x4e - 0x4f are for LPC SIO and are forwarded to the LPC device. -- ~Randy