All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Hans de Goede <hdegoede@redhat.com>, linux-input@vger.kernel.org
Subject: Re: [PATCH 0/6] Fixes for ALPS trackstick
Date: Thu, 15 Jan 2015 13:02:16 -0800	[thread overview]
Message-ID: <20150115210216.GD19367@dtor-ws> (raw)
In-Reply-To: <201501152128.41419@pali>

On Thu, Jan 15, 2015 at 09:28:41PM +0100, Pali Rohár wrote:
> On Thursday 15 January 2015 20:38:18 Dmitry Torokhov wrote:
> > On Thu, Jan 15, 2015 at 08:19:59PM +0100, Pali Rohár wrote:
> > > On Thursday 15 January 2015 19:18:20 Dmitry Torokhov wrote:
> > > > On Thu, Jan 15, 2015 at 11:49:32AM +0100, Pali Rohár wrote:
> > > > > On Wednesday 14 January 2015 23:55:48 Dmitry Torokhov 
> wrote:
> > > > > > Hi Pali,
> > > > > > 
> > > > > > This series try to address the issue you brought
> > > > > > regarding trackstick initialization on Dell Latitudes
> > > > > > in a different way than the patches you proposed.
> > > > > > Basically in this series we move resetting and all
> > > > > > detection in alps_detect() and make sure we keep the
> > > > > > state so alps_init() can reuse it and not perform the
> > > > > > detection all over again. Doing this allows us to set
> > > > > > up device characteristics (name, version, etc)
> > > > > > properly from the get go while still performing reset
> > > > > > only once.
> > > > > > 
> > > > > > This is untested as I do not have any ALPS devices
> > > > > > anymore so I'd appreciate you giving it a spin.
> > > > > > 
> > > > > > Thanks!
> > > > > 
> > > > > Hi Dmitry,
> > > > > 
> > > > > on top of which branch/repository should I apply your
> > > > > patches?
> > > > 
> > > > Should be applicable to my 'next' branch (which I just
> > > > upreved to 3.19-rc4).
> > > > 
> > > > Thanks.
> > > 
> > > Not working at top of next (0c3e994).
> > > 
> > > Applying: Input: ALPS - renumber protocol numbers
> > > Applying: Input: ALPS - make Rushmore a separate protocol
> > > error: patch failed: drivers/input/mouse/alps.c:1275
> > > error: drivers/input/mouse/alps.c: patch does not apply
> > > Patch failed at 0002 Input: ALPS - make Rushmore a separate
> > > protocol
> > 
> > Hmm.. I created a new alps branch (based on 3.19-rc4), can you
> > try it?
> > 
> > Thanks.
> 
> Compiled from your new alps branch (with "if (!priv)" fix) and 
> modprobing psmouse.ko caused laptop freeze :-( Even sysrq not 
> responded. So something is not working...

Hmm, is it on text console or in X? Any chance you could go through
pathes - there are only 8 of them including 2 of yours that should be
unmodified.

Thanks.


-- 
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-01-15 21:02 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-14 22:55 [PATCH 0/6] Fixes for ALPS trackstick Dmitry Torokhov
2015-01-14 22:55 ` [PATCH 1/6] Input: ALPS - renumber protocol numbers Dmitry Torokhov
2015-01-14 22:55 ` [PATCH 2/6] Input: ALPS - make Rushmore a separate protocol Dmitry Torokhov
2015-01-14 22:55 ` [PATCH 3/6] Input: ALPS - split protocol data from model info Dmitry Torokhov
2015-01-14 22:55 ` [PATCH 4/6] Input: ALPS - consolidate setting protocol parameters Dmitry Torokhov
2015-01-14 22:55 ` [PATCH 5/6] Input: ALPS - fix trackstick detection on some Dell Latitudes Dmitry Torokhov
2015-01-15 20:21   ` Pali Rohár
2015-01-15 21:00     ` Dmitry Torokhov
2015-01-17 10:26   ` Pali Rohár
2015-02-02  5:34     ` Dmitry Torokhov
2015-02-02 10:51       ` Pali Rohár
2015-01-14 22:55 ` [PATCH 6/6] Input: ALPS - mix trackstick and external PS/2 mouse data Dmitry Torokhov
2015-01-15 20:34   ` Pali Rohár
2015-01-15 21:00     ` Dmitry Torokhov
2015-01-18  9:45   ` Pali Rohár
2015-01-15 10:49 ` [PATCH 0/6] Fixes for ALPS trackstick Pali Rohár
2015-01-15 18:18   ` Dmitry Torokhov
2015-01-15 19:19     ` Pali Rohár
2015-01-15 19:38       ` Dmitry Torokhov
2015-01-15 20:28         ` Pali Rohár
2015-01-15 21:02           ` Dmitry Torokhov [this message]
2015-01-17 10:01             ` Pali Rohár
2015-01-18  7:22               ` Dmitry Torokhov
2015-01-18  9:47                 ` Pali Rohár
2015-01-24 22:20                   ` Pali Rohár
2015-02-02  5:49                   ` Dmitry Torokhov
2015-02-02 10:49                     ` Pali Rohár
2015-02-02 14:27                       ` Pali Rohár
2015-02-08 12:26                         ` Pali Rohár
2015-02-10  6:32                           ` Dmitry Torokhov
2015-02-11 18:13                             ` Pali Rohár
2015-02-12  7:52                           ` Dmitry Torokhov
2015-02-12 20:25                             ` Pali Rohár
2015-02-05 11:41                     ` Pali Rohár

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=20150115210216.GD19367@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-input@vger.kernel.org \
    --cc=pali.rohar@gmail.com \
    /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.