linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Gamari <bgamari.foss@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>, opensource@dell.com
Cc: linux-input@vger.kernel.org,
	Seth Forshee <seth.forshee@canonical.com>,
	Andrew Skalski <askalski@gmail.com>,
	Jiri Kosina <jkosina@suse.cz>, Vojtech Pavlik <vojtech@suse.cz>,
	Neil Brown <neilb@cse.unsw.edu.au>,
	Sebastian Kapfer <sebastian_kapfer@gmx.net>
Subject: Re: New Alps protocol in the wild?
Date: Tue, 31 Jul 2012 16:50:11 -0400	[thread overview]
Message-ID: <877gtju03g.fsf@gmail.com> (raw)
In-Reply-To: <20120731060156.GA32327@core.coreip.homeip.net>

Dmitry Torokhov <dmitry.torokhov@gmail.com> writes:

> Given how unwilling they are to share details of their protocol I would
> not be surprised if they tried to detect virtual environment on purpose.
>
Sadly, you very well could be right.

That being said, I don't know what they could be checking for. I'm
passing "-cpu host" to qemu which should eliminate the CPUID
hint. Otherwise, the only obvious hint I can find is the hard drive
which mentions Qemu in its vendor string. Taking a quick look at the
apfiltr.sys I can't find any strings that might imply it's looking at
device/vendor strings. Perhaps they could be using ACPI tables (although
I see no ACPI-ish strings in the driver)? I guess SMBIOS and DMI are
also targets although I know little about their implementation.

Anyways, I suppose at this point it is probably time to bring this
discussion over to the qemu list to discuss future directions for
virtualization. Unfortunately, it becomes very difficult to maintain
motivation on problems like this when Alps will likely render whatever
reverse engineering knowledge gained now obsolete in the next iteration
of hardware. It seems clear that the only sustainable way to get
open-source support for these and future Alps devices is with some
cooperation from Alps and/or a major customer. It seems that Dell is in
an ideal position to help here.

Cheers,

- Ben


  reply	other threads:[~2012-07-31 20:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-27 16:18 New Alps protocol in the wild? Ben Gamari
2012-07-27 16:52 ` Seth Forshee
2012-07-27 17:17   ` Ben Gamari
2012-07-27 19:15     ` dturvene
2012-07-30  8:43       ` Jiri Kosina
2012-07-30 16:19 ` Ben Gamari
2012-07-31  5:19   ` Ben Gamari
2012-07-31  6:01     ` Dmitry Torokhov
2012-07-31 20:50       ` Ben Gamari [this message]
2012-07-31 19:17     ` Ben Gamari
2012-08-14 10:35     ` James
2012-08-14 16:01       ` Ben Gamari
2012-08-14 16:15         ` Seth Forshee
     [not found]         ` <20120814160519.GC12473@artemis.panaceas.org>
2012-08-15  5:49           ` Ben Gamari
2012-08-16  5:04             ` Ben Gamari
2012-08-17 16:46               ` dturvene
2012-08-17 17:04                 ` Ben Gamari
2012-09-08 12:51                   ` dturvene
2012-09-10 20:35                     ` Ben Gamari
2012-09-15 20:49                     ` dturvene
     [not found]                       ` <CAPtp-N_PbGABwC7PtNtEe7bitc=yg1oV2M6cK6Wb1PkVq6wa9A@mail.gmail.com>
2012-09-30 17:33                         ` dturvene

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=877gtju03g.fsf@gmail.com \
    --to=bgamari.foss@gmail.com \
    --cc=askalski@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    --cc=opensource@dell.com \
    --cc=sebastian_kapfer@gmx.net \
    --cc=seth.forshee@canonical.com \
    --cc=vojtech@suse.cz \
    /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).