All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chase Douglas <chase.douglas@canonical.com>
To: Chris Friesen <cbf123@mail.usask.ca>
Cc: dtor@mail.ru, sebastian_kapfer@gmx.net,
	dmitry.torokhov@gmail.com, linux-input@vger.kernel.org
Subject: Re: alps.c patch for Dell E5410?
Date: Mon, 25 Apr 2011 12:19:53 -0400	[thread overview]
Message-ID: <4DB59F29.9000503@canonical.com> (raw)
In-Reply-To: <4DAF46A2.6050703@mail.usask.ca>

On 04/20/2011 04:48 PM, Chris Friesen wrote:
> Hi everyone,
> 
> I've got an E5410 on which I'm trying to get the touchpad working
> properly. I'm running Fedora 14 with 2.6.35 and by default it's just
> recognized as a mouse.
> 
> I found a patch on the web at:
> https://confluence.nau.edu/display/~cmg238@nau.edu/Recognize+ALPS+Touchpad+on+Dell+E6510+in+Ubuntu
> 
> It appears similar (but not identical) to the patch that was added for
> the HP Pavilion dm3 but then backed out.
> 
> With the patch applied, the kernel appears to recognize it as a
> DualPoint Stick and a DualPoint Touchpad.  On this particular machine
> the stick doesn't seem to be actually wired up, but the trackpad looks
> visually identical to the E6510.
> 
> However, even after it was recognized I haven't yet been able to get
> scrolling to work, and "synclient -m 100" doesn't give anything
> useful--but various comments have led me to wonder if it actually should
> at this point.
> 
> So what's the deal here?  Is someone working on getting full support for
> these things?  Should "synclient -m 100" work?

I don't personally have much news to tell you. I don't have the
hardware, and I've been busy with other work. I won't be able to help
out here.

-- Chase

      reply	other threads:[~2011-04-25 16:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-20 20:48 alps.c patch for Dell E5410? Chris Friesen
2011-04-25 16:19 ` Chase Douglas [this message]

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=4DB59F29.9000503@canonical.com \
    --to=chase.douglas@canonical.com \
    --cc=cbf123@mail.usask.ca \
    --cc=dmitry.torokhov@gmail.com \
    --cc=dtor@mail.ru \
    --cc=linux-input@vger.kernel.org \
    --cc=sebastian_kapfer@gmx.net \
    /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.