public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Charles-Edouard Ruault <ce@idtect.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: IO port conflict between timer & watchdog on PCISA-C800EV board ?
Date: Mon, 07 Feb 2005 10:29:00 +0100	[thread overview]
Message-ID: <420734DC.4020900@idtect.com> (raw)

Hi All,

i wrote a driver for the watchdog timer provided by a small form factor 
board from IEI ( the PCISA-C800EV : 
http://www.iei.com.tw/en/product_IPC.asp?model=PCISA-C800 ).
This board has a Via Apollo PLE133 ( VT8601A and VT82C686B ) chipset.
The watchdog uses two registers at addresses 0x43 and 0x443, therefore 
my driver tries to get bot addresses for its own use calling
request_region(0x43, 1, "watchdog" ) and request_region(0x443, 1, 
"watchdog").
The first call to request 0x43 fails because the address has already 
been allocated to the timer ( /proc/ioports shows 0040-005f : timer ).

So my questions are :
- Why is the generic timer using this address ? isn't it reserving a too 
wide portion of IO ports ? Should it be modified for this board ?
-  If there's a good reason for the timer to request this address, is  
there a clean way to share it with the timer ?

Thanks for your answers.
Regards.
PS: Please CC me to your replies, i'm not on the list.

-- 
Charles-Edouard Ruault
Idtect SA
115 rue Reaumur - 75002, Paris, France
Tel: +33-1-55-34-76-65
Fax: +33-1-55-34-76-75
Web: http://www.idtect.com


             reply	other threads:[~2005-02-07  9:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-07  9:29 Charles-Edouard Ruault [this message]
2005-02-07 16:31 ` IO port conflict between timer & watchdog on PCISA-C800EV board ? 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
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=420734DC.4020900@idtect.com \
    --to=ce@idtect.com \
    --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