From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
Benjamin Tissoires <btissoir@redhat.com>,
Peter Hutterer <peter.hutterer@redhat.com>,
platform-driver-x86@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH 0/2] input/serio: Add a firmware_id sysfs attribute
Date: Fri, 28 Mar 2014 08:27:04 +0000 [thread overview]
Message-ID: <20140328082704.GC6801@srcf.ucam.org> (raw)
In-Reply-To: <20140328082452.GH22093@core.coreip.homeip.net>
On Fri, Mar 28, 2014 at 01:24:52AM -0700, Dmitry Torokhov wrote:
> On Fri, Mar 28, 2014 at 08:20:04AM +0000, Matthew Garrett wrote:
> > On Fri, Mar 28, 2014 at 12:56:55AM -0700, Dmitry Torokhov wrote:
> >
> > > I am still unsure if we shoudl be adding these new IDs to serio core...
> > > Can't the X driver take a peek at ACPI devices on it's own?
> >
> > In the (admittedly unlikely) event of multiple PS/2 trackpads, how do
> > you know which one corresponds to which ACPI device?
>
> So far I have not seen a single instance of a laptop with 2 touchpads
> and I doubt external PS/2 ones will ever make come back.
Right, we can hack around it based on what we've seen so far. But it
seems more attractive to fix it in such a way that we won't behave
inappropriately even if someone does do something utterly unexpected in
future. For instance, some ARM devices have i8042-like serio - if the
underlying device is exposed in device tree, it'd be nice to be able to
expose that to userspace without having to modify the core X code.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2014-03-28 8:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 10:12 [PATCH 0/2] input/serio: Add a firmware_id sysfs attribute Hans de Goede
2014-03-20 10:12 ` [PATCH 1/2] " Hans de Goede
2014-03-20 10:12 ` [PATCH 2/2] input/serio/8042: Add firmware_id support Hans de Goede
2014-03-20 17:21 ` [PATCH 0/2] input/serio: Add a firmware_id sysfs attribute Matthew Garrett
2014-03-24 1:07 ` Peter Hutterer
2014-03-28 7:56 ` Dmitry Torokhov
2014-03-28 8:12 ` Hans de Goede
2014-03-28 8:17 ` Dmitry Torokhov
2014-03-28 8:29 ` Hans de Goede
2014-03-28 8:52 ` Dmitry Torokhov
2014-03-28 9:00 ` Matthew Garrett
2014-03-28 16:04 ` Dmitry Torokhov
2014-03-28 9:05 ` Hans de Goede
2014-03-28 8:20 ` Matthew Garrett
2014-03-28 8:24 ` Dmitry Torokhov
2014-03-28 8:27 ` Matthew Garrett [this message]
2014-03-28 8:50 ` Dmitry Torokhov
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=20140328082704.GC6801@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=btissoir@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=peter.hutterer@redhat.com \
--cc=platform-driver-x86@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;
as well as URLs for NNTP newsgroup(s).