Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: priya <priya@procsys.com>
To: "linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Keyboard interface test fails
Date: Thu, 06 Jan 2005 11:01:54 +0530	[thread overview]
Message-ID: <41DCCD4A.20206AE9@procsys.com> (raw)

Hi,
Iam trying to bring up the PS/2 mouse on
a custom board based on RM5231A MIPS
processor and IT8172 companion chip.

The PS/2 mouse and keyboard are
connected to the Super IO chip IT712F-A
(version 7). The keyboard gives me
"interface failed self test" error and
the mouse events does not get
recognized.

Iam running kernel version 2.4.25.

I have dumped the status and the data
register contents when the "keyboard
interface failure" happens. The data
register content is "0x2" - which means
clock is line stuck high. But the key
presses are recognized and iam able to
work with the keyboard well.

I dont know if anyone has faced such a
problem with this particular version of
Super IO or do i have to apply  a patch
??

regards
priya

                 reply	other threads:[~2005-01-06  5:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=41DCCD4A.20206AE9@procsys.com \
    --to=priya@procsys.com \
    --cc=linux-mips@linux-mips.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