From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Bret Hughes <bhughes@elevating.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: serial port discovery on a motion computing tablet
Date: Wed, 14 Mar 2007 23:25:51 +0000 [thread overview]
Message-ID: <20070314232550.GA11970@srcf.ucam.org> (raw)
In-Reply-To: <45F84103.8050803@elevating.com>
On Wed, Mar 14, 2007 at 01:37:55PM -0500, Bret Hughes wrote:
> Woo hoo! I see my device it's id is TKO0001 just like the engr told me
> it would be. At the time I had little to no idea what he was talking about.
>
> On to look at the code and see how that works.
Something like the following should work, if you haven't already got it
figured:
diff --git a/drivers/serial/8250_pnp.c b/drivers/serial/8250_pnp.c
index d3d6b82..c7b019b 100644
--- a/drivers/serial/8250_pnp.c
+++ b/drivers/serial/8250_pnp.c
@@ -340,6 +340,8 @@ static const struct pnp_device_id pnp_dev_table[] = {
{ "FUJ02B8", 0 },
{ "FUJ02B9", 0 },
{ "FUJ02BC", 0 },
+ /* TouchKO touchscreen */
+ { "TKO0001", 0 },
/* Rockwell's (PORALiNK) 33600 INT PNP */
{ "WCI0003", 0 },
/* Unkown PnP modems */
and then just make sure that you have CONFIG_8250_PNP enabled. After
that, it should just appear as a touchscreen. You may still need to
perform some handshaking in the protocol interaction to get it working,
but ideally that would be done in the X driver.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2007-03-14 23:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 3:14 serial port discovery on a motion computing tablet Bret Hughes
2007-03-14 13:43 ` Matthew Garrett
2007-03-14 14:29 ` Bret Hughes
2007-03-14 14:35 ` Matthew Garrett
2007-03-14 15:03 ` Bret Hughes
2007-03-14 15:14 ` Matthew Garrett
[not found] ` <45F817E2.1020900@elevating.com>
2007-03-14 18:37 ` Bret Hughes
2007-03-14 23:25 ` Matthew Garrett [this message]
2007-03-14 23:57 ` Bret Hughes
2007-03-15 0:09 ` Matthew Garrett
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=20070314232550.GA11970@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=bhughes@elevating.com \
--cc=linux-acpi@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.