From: Ondrej Zary <linux@rainbow-software.org>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Charles-Edouard Ruault <ce@idtect.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: IO port conflict between timer & watchdog on PCISA-C800EV board ?
Date: Mon, 07 Feb 2005 18:57:22 +0100 [thread overview]
Message-ID: <4207AC02.8010407@rainbow-software.org> (raw)
In-Reply-To: <420797DE.6030904@osdl.org>
Randy.Dunlap wrote:
[...]
> /proc/ioports timer assignments have now been split up like this:
> 0040-0043 : timer0
> 0050-0053 : timer1
>
> However, port 0x43 is still assigned to timer0, so your request_region
> call will still fail. What system board timer resource assignments
> should be used for that VIA chipset? If the chipset timer only needs
> 0x40-0x42, e.g., leaving 0x43 available, then it would be possible
> to do some kind of workaround (maybe not real clean, but possible).
The timer uses ports 0x40-0x43. However, port 0x43 is defined as WO
(write-only) - it's timer command register.
--
Ondrej Zary
next prev parent reply other threads:[~2005-02-07 17:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-07 9:29 IO port conflict between timer & watchdog on PCISA-C800EV board ? Charles-Edouard Ruault
2005-02-07 16:31 ` Randy.Dunlap
2005-02-07 17:00 ` linux-os
2005-02-07 17:33 ` Charles-Edouard Ruault
2005-02-07 17:32 ` Charles-Edouard Ruault
2005-02-07 17:57 ` Ondrej Zary [this message]
2005-02-15 17:04 ` Alan Cox
2005-02-21 13:06 ` [PATCH] Reserve only needed regions for PC timers on i386 and x86_64 Charles-Edouard Ruault
2005-02-23 7:23 ` Marcelo Tosatti
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=4207AC02.8010407@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=ce@idtect.com \
--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