public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Frantisek Rysanek" <Frantisek.Rysanek@post.cz>
To: linux-kernel@vger.kernel.org
Subject: What pokes the ISA IO port of 0x211 ?
Date: Mon, 21 Apr 2008 13:12:41 +0200	[thread overview]
Message-ID: <480C92C9.18283.A24BB91B@localhost> (raw)

Dear Everyone,

I'm dealing with an embedded PC motherboard that contains some custom 
circuitry (GPIO), accessible via an ISA IO range between 0x200 and 
0x218.  

There's an interesting issue with this in recent Linux (tried 
2.6.22.6 and 2.6.24.2): something probes IO port 0x211 on boot, which 
happens to be an add-on buzzer control port - effectively the kernel 
boot launches an accoustic alarm :-)  

Any ideas what this could be? 

Obviously it's no problem for me to write a tiny kernel module to 
disable the alarm again, and I've actually verified the problem using 
ioperm()+outb() from user space, but still I'd be interested to know 
which particular piece of code could be probing that address...

The address decode might be implemented using some general-purpose 
features of the Winbond W83627HF SuperIO (as there's no ISA in the 
system, just ICH4 LPC) - but it seems quite unlikely that this would 
be caused by something fiddling with the W83627 config registers.
It really seems like something writes 0xFF to IO port 0x211.

Thanks for your time and attention :-)

Frank Rysanek


             reply	other threads:[~2008-04-21 11:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-21 11:12 Frantisek Rysanek [this message]
2008-04-21 15:51 ` What pokes the ISA IO port of 0x211 ? Bart Van Assche
2008-04-21 17:40   ` H. Peter Anvin
2008-04-21 20:05 ` Rene Herman
2008-04-21 20:34   ` Rene Herman
2008-04-23 12:19     ` Frantisek Rysanek
2008-04-23 13:56       ` Rene Herman

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=480C92C9.18283.A24BB91B@localhost \
    --to=frantisek.rysanek@post.cz \
    --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