public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Daoud <alex.daoud-ee4meeAH724@public.gmane.org>
To: One Thousand Gnomes
	<gnomes-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Intel lynx point designware issue
Date: Mon, 02 Feb 2015 16:08:41 +0000	[thread overview]
Message-ID: <0NJ5000Y0JIKT300@st11p00mm-asmtp001.mac.com> (raw)

Hi Alan,

You are right that there are issues with the touchpad, I'm referring to the touchscreen however (which works fine with i2c-hid on Linux).

The issue with the touchpad, if I recall correctly, was that the rmi4 drivers were taking priority over the hid-generic ones (which they should), however rmi4 was broken in recent kernel builds. This is what I've heard, I haven't actually installed Linux on the device myself.

AlexOn 2 Feb 2015 15:53, One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk> wrote:
>
> On Fri, 30 Jan 2015 16:36:27 +0000 
> Alexandre Daoud <alex.daoud@mac.com> wrote: 
>
> > Hey Linux-i2c, 
> > 
> > I have a bit of an unorthodox question for this mailing list but you guys seem like the only people who could help me at this point. 
> > 
> > I have a Dell Venue 11 Pro tablet with the Lynxpoint I2C busses (INT33C2, INT33C3), one of which drives an i2c-hid touchscreen device. 
>
> Last time I looked the Venue 11 Pro touchpad didn't work in Linux either. 
>
> Alan 

             reply	other threads:[~2015-02-02 16:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 16:08 Alexandre Daoud [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-01-30 16:36 Intel lynx point designware issue Alexandre Daoud
     [not found] ` <195CACBC-7E0B-4598-986C-0814289C6ECD-ee4meeAH724@public.gmane.org>
2015-02-02 10:25   ` Mika Westerberg
2015-02-02 15:53   ` One Thousand Gnomes

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=0NJ5000Y0JIKT300@st11p00mm-asmtp001.mac.com \
    --to=alex.daoud-ee4meeah724@public.gmane.org \
    --cc=gnomes-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.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