Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756216Ab1FFGyi (ORCPT ); Mon, 6 Jun 2011 02:54:38 -0400 Received: from mail-ww0-f44.google.com ([74.125.82.44]:49086 "EHLO mail-ww0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752108Ab1FFGyf (ORCPT ); Mon, 6 Jun 2011 02:54:35 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=E/MCABuxAYDePxVxvzCcQkcwZIz8dhDbVVCcYA4Y6Bvu3aMp7cyz/EWeF5gL/DaOJZ HmdRqRDib4gGRY0XdL61zRolVdYiKcWPaBbfmEo0FJo1L1YVdztoJ99PrtLPKQ5nfxKU 7Q+1KTBtlTL7r3irPPzaQ+wkL5VmRi60cuZC4= Message-ID: <4DEC796E.1050307@users.sourceforge.net> Date: Mon, 06 Jun 2011 09:53:34 +0300 From: Alberto Mardegan User-Agent: Mozilla/5.0 (X11; U; Linux i686; it-IT; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10 MIME-Version: 1.0 To: Bastien Nocera CC: linux-kernel@vger.kernel.org, "Javier S. Pedro" , linux-input@vger.kernel.org Subject: Re: Reporting screen/laptop orientation data to userspace References: <4DE1FA7F.3050308@users.sourceforge.net> <1307116529.2669.130.camel@novo.hadess.net> In-Reply-To: <1307116529.2669.130.camel@novo.hadess.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2409 Lines: 55 On 06/03/2011 06:55 PM, Bastien Nocera wrote: > Do you also have a discrete accelerometer with that? Or you only ever > get notification through there? There's a discrete accelerometer, but I suspect that it might be hard for its driver to get accepted into the mainline kernel, since it's directly playing with the EC I/O ports. It's this one: https://gitorious.org/iaps/iaps/blobs/master/iaps.c The coarse data OTOH comes via a clean WMI interface. > If there is a discrete accelerometer, I'd drop the extra metadata, and > send an event through udev, and expect user-space to read from the > accelerometer instead. You mean, send an event through udev when the WMI interface reports that the orientation has changed, and then expect the userspace to read the values from the accelerometer? IMHO, reporting an event with no context data, it's inefficient and ugly (because it forces the userspace to perform additional acctions in order to get the data). > If there isn't a discrete accelerometer, create a fake one, with some > hardcoded data based on the actual orientation of the device. This could be a solution in both cases (i.e., even if a discrete accelerometer is available). But it would be nice to have some flags on the input device which tell that this accelerometer is not as precise as one could desire. Is there such a thing? > The accelerometer (whether real or fake) should show 3 axis (X/Y/Z). > > As soon as it's seen some testing, I'll be showing the work I did for > GNOME support for automatic rotation based on orientation. Do you support choosing the accelerometer device to be used? The device that I wanted to create is actually something much simpler than an accelerometer; it would just report screen orientation. I believe that some computer screens might have something similar, detecting the screen orientation based on the angle formed between the screen base (or wall mount) and the screen panel... I would assume that if such information exists, this Lenovo Ideapad screen orientation should be reported in a similar way. Ciao, Alberto -- http://blog.mardy.it <-- geek in un lingua international! -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/