From: "James H. Cloos Jr." <cloos@jhcloos.com>
To: linux-kernel@vger.kernel.org, linux-fbdev-devel@lists.sourceforge.net
Subject: dell i8100 touchstick, 2.5 input -- further info
Date: 18 Dec 2002 16:58:15 -0500 [thread overview]
Message-ID: <m3fzsvj8g8.fsf@lugabout.jhcloos.org> (raw)
I've been researching the touchstick breakage in 2.5 on the i8100.
The board appears to use a SMC lpc47n252 superIO chip for keyboard and
ps/2 support. Details on the chip are at:
http://www.smsc.com/main/datasheets/47n252.pdf
http://www.smsc.com/main/datasheets/47n252add.pdf
It has four ps/2 ports, matrix kb support and an i8051 compatible
µcore. The i8051 code, then, is responsible for muxing the four ps/2
ports to the host's 0x60/0x64 ioports.
Dell's bios upgrade tool flashes the 47n252.
I added some printk()s to i8042.c and confirmed that (unless something
else is accessing the kbc during the mux activation test) the synaptics,
et al mux protocol is not supported.
Something the 2.5 input system is doing is resetting the kbc to a
state where it no longer muxes its ps2 ports.
Obviously, a dump of the i8051 or bios code would provide all the answers.
Does anyone have any ideas on where to go from here?
Having to use the touchpad is bloody irritating. :(
-JimC
reply other threads:[~2002-12-18 21:58 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=m3fzsvj8g8.fsf@lugabout.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.