All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] udev: generalize the check in touchscreen rule
Date: Wed, 11 Apr 2012 14:15:57 +0100	[thread overview]
Message-ID: <1487451.qaDevSNUCm@helios> (raw)
In-Reply-To: <CAAQYJAsGkFkBnFXfWzcx6UTm12SY39=VU6SFKT_iTsxH6=wmtg@mail.gmail.com>

On Wednesday 11 April 2012 15:09:10 Andrea Adami wrote:
> On Wed, Apr 11, 2012 at 2:55 PM, Paul Eggleton
> <paul.eggleton@linux.intel.com> wrote:
> > On Wednesday 11 April 2012 13:57:29 Andrea Adami wrote:
> >> Finally, bluelightning reported that on ipaq h1940 the rule did not
> >> match and added a .bbappend in meta-handheld.
> > 
> > FYI this is because pressure support was removed from the driver. I don't
> > know if there's ever hope of it coming back.
> 
> Well, there was a NACKed patch:
> 
> https://lkml.org/lkml/2011/6/23/817
> 
> Mark Brown:
> "It seems much more sane to fix this in tslib, the kernel is not actually
> reporting pressure meaningfully here and there's already BTN_TOUCH to
> report if the pen is down."

Interesting. FWIW, I can report that with a patch to the rule such as this one 
at least on h1940 the touchscreen works fine, and there was no need to 
additionally fix anything in tslib.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2012-04-11 13:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-02 21:35 [PATCH] udev: generalize the check in touchscreen rule Andrea Adami
2012-04-11  8:59 ` Andrea Adami
2012-04-11 10:16   ` Richard Purdie
2012-04-11 10:40     ` Koen Kooi
2012-04-11 11:57       ` Andrea Adami
2012-04-11 12:55         ` Paul Eggleton
2012-04-11 13:09           ` Andrea Adami
2012-04-11 13:15             ` Paul Eggleton [this message]
2012-04-11 13:18               ` Paul Eggleton
2012-04-11 13:32                 ` Andrea Adami
2012-04-11 12:12     ` Marko Katić

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=1487451.qaDevSNUCm@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.