From: Bret Hughes <bhughes@elevating.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: serial port discovery on a motion computing tablet
Date: Wed, 14 Mar 2007 09:29:05 -0500 [thread overview]
Message-ID: <45F806B1.3060807@elevating.com> (raw)
In-Reply-To: <20070314134323.GC1467@srcf.ucam.org>
Matthew Garrett wrote:
> On Tue, Mar 13, 2007 at 10:14:19PM -0500, Bret Hughes wrote:
>
>> 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.
>>
>
> It sounds like it ought to be exposed via ACPIPNP. If you do cat
> /sys/bus/pnp/devices/*/id, do any of them look plausibly linked to the
> tablet device? If so, add the id to drivers/serial/8250_pnp.c, build it,
> see if that binds and gives you a serial port and if so send a patch.
>
Thanks for the help.
nothing there:
[root@localhost serial]# ls -a /sys/bus/pnp/devices/
. ..
nothing loaded in drivers either:
[root@localhost serial]# ls -Ra /sys/bus/pnp/drivers/
/sys/bus/pnp/drivers/:
. .. ide parport_pc serial system
/sys/bus/pnp/drivers/ide:
. ..
/sys/bus/pnp/drivers/parport_pc:
. ..
/sys/bus/pnp/drivers/serial:
. ..
/sys/bus/pnp/drivers/system:
. ..
Is there a module I should load before this works? perhaps a kernel
recompile with some additional modules are needed?
Now that I am back at the office and looking at the kernel .config via
make xconfig I see that 8250/16550 device discovery via ACPI namespace
(SERIAL_8250_ACPI) is not enabled. Is is safe to assume that it should
be (go ahead and groan, I probably would) anything else that should be
included?
I am going to enable it and start a compile. I guess we will see what
kind of horsepower this little dude has.
Thanks again,
Bret
next prev parent reply other threads:[~2007-03-14 14:29 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 [this message]
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=45F806B1.3060807@elevating.com \
--to=bhughes@elevating.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.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.