public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bret Hughes <bhughes@elevating.com>
To: linux-acpi@vger.kernel.org
Subject: serial port discovery on a motion computing tablet
Date: Tue, 13 Mar 2007 22:14:19 -0500	[thread overview]
Message-ID: <45F7688B.8000101@elevating.com> (raw)

I am evaluating a motion computing LE1600 tablet for possible use with 
linux using Centos 4.4 since that is what we use for several servers and 
had the installation media handy.  This device uses a TouchKO serial 
touchscreen that has been used by linux in the past but the issue I am 
facing is that the bios does not expose the serial ports.  I spoke with 
an engineer at TouchKO familiar with the LE1600 project an he told me I 
would have to access the serial port via acpi.  Hmm says I, I guess I 
have some reading to do.  DO after a day or so of trying to get up to 
speed, I feel I can ask a fairly decent question or two. 

I found a lot of wacom references but as this touchscreen has ELO and 
Microtouch emulations I am hard pressed to figure out where to separate 
the detection of the port from the driver of the device.

What I need to do is get a connection to the serial port send a couple 
of commands to it to set the baud rate and emulation mode and then start 
X where the MuTouch Driver should work.

So.  Is this where I need to be asking acpi serial port questions?  I 
found a tc1100 prog somewhere but could not get it to compile 
correctly,  pacpidump compiled ok and I have the output of of acpidump 
if that helps.

Is this a doable deal?  I dled the current (2.6.9-42xxx I think) kernel 
tree from Centos as the last thing I did before leaving work today and 
will look at both how Centos (and the upstream provider) configure the 
kernel and if there are options that look like it might work. 

Googling today turned up several references to a 8250_acpi module and 
then I found a patch somewhere that indicated that it was no longer 
needed.  I wish I had looked at the kernel tree before leaving today but 
I thought i would ask for some tips to get me going and possibly add 
some known good hardware to the list before I am done.

Am I correct in thinking that I should be able to get a reference to the 
serial port through acpi on this box?  Any tips ?  Any testing that you 
guys would like done while I have this hardware?

TIA

Bret

             reply	other threads:[~2007-03-14  3:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-14  3:14 Bret Hughes [this message]
2007-03-14 13:43 ` serial port discovery on a motion computing tablet 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
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=45F7688B.8000101@elevating.com \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox