From: Pierre Ossman <drzeus-list@drzeus.cx>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Timer allocates too many ports
Date: Fri, 20 Aug 2004 23:25:49 +0200 [thread overview]
Message-ID: <41266C5D.7000908@drzeus.cx> (raw)
In-Reply-To: <20040820140503.67d23479.rddunlap@osdl.org>
Randy.Dunlap wrote:
>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.
>
>
Unfortunately the driver allocates 0x40-0x5f as can be seen in
/proc/ioports:
0040-005f : timer
I do not know which file contains this allocation so I haven't been able
to change it. Any ideas?
>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.
>
>
>
>
The device is a SD/MMC card reader which is indeed an LPC device. The
ports in question are needed to identify the chip and determine which
resources it has. Actual usage is done on higher ports.
Rgds
Pierre
next prev parent reply other threads:[~2004-08-20 21:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 20:33 Timer allocates too many ports Pierre Ossman
2004-08-20 21:05 ` Randy.Dunlap
2004-08-20 21:25 ` Pierre Ossman [this message]
2004-08-20 21:41 ` Randy.Dunlap
2004-08-21 8:58 ` Pierre Ossman
2004-08-21 17:49 ` Randy.Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41266C5D.7000908@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox