public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "Greg.Chandler@wellsfargo.com" <Greg.Chandler@wellsfargo.com>,
	linux-kernel@vger.kernel.org,
	linux-input@atrey.karlin.mff.cuni.cz
Subject: Re: Touchscreen hardware hacking/driver hacking.
Date: Thu, 26 Oct 2006 23:47:01 +0100	[thread overview]
Message-ID: <20061026224701.GA19534@srcf.ucam.org> (raw)
In-Reply-To: <d120d5000610260929n6239772bka1a9cce971cfa133@mail.gmail.com>

On Thu, Oct 26, 2006 at 12:29:18PM -0400, Dmitry Torokhov wrote:

> I don't recall anything in ACPI spec that would help determining type
> of PS/2 device connected, but then I did not read the latest version.
> Anyway, I would not hold my breath...

It's possible for PnP devices to have multiple identifiers associated 
with them. One of these probably identifies a PS/2 mouse device as a 
mouse device, but it's possible that there's a second identifier that 
indicates that it's something else as well.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2006-10-26 22:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-25 20:08 Touchscreen hardware hacking/driver hacking Greg.Chandler
2006-10-25 20:55 ` Dmitry Torokhov
2006-10-26  8:48   ` Matthew Garrett
2006-10-26 16:29     ` Dmitry Torokhov
2006-10-26 22:47       ` Matthew Garrett [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-10-18 18:45 Greg.Chandler
2006-10-17 22:48 Greg Chandler
2006-10-18  2:30 ` Greg Chandler
2006-10-18  3:42   ` Kyle Moffett
2006-10-17 21:46 Greg.Chandler
2006-10-17 21:28 Greg.Chandler
2006-10-18  2:14 ` Lee Revell
2006-10-17 20:30 Greg.Chandler
2006-10-17 21:05 ` Andreas Mohr
2006-10-17 21:12 ` Dmitry Torokhov
2006-10-18  7:39 ` 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=20061026224701.GA19534@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=Greg.Chandler@wellsfargo.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox