From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Timer allocates too many ports
Date: Fri, 20 Aug 2004 14:05:03 -0700 [thread overview]
Message-ID: <20040820140503.67d23479.rddunlap@osdl.org> (raw)
In-Reply-To: <4126600F.4050302@drzeus.cx>
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
next prev parent reply other threads:[~2004-08-20 21:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 20:33 Pierre Ossman
2004-08-20 21:05 ` Randy.Dunlap [this message]
2004-08-20 21:25 ` Pierre Ossman
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=20040820140503.67d23479.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®