All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Yves DUF <yves.duf@laposte.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-input@vger.kernel.org
Subject: Re: Help on Driver touchkit_ps2.c
Date: Thu, 10 Jan 2013 09:33:22 -0800	[thread overview]
Message-ID: <50EEFB62.2090303@gmail.com> (raw)
In-Reply-To: <CANe8kDHzsfnXJGtqrJUSwnRm2apQSc2WKCLhwQAayUog=wdPsA@mail.gmail.com>

On 01/09/2013 02:07 PM, Yves DUF wrote:
> Hello Mister Mattock.
>
> I hope this email will not bother you. It's about the eGalax
> Touchscreen driver you modify more or less recently.
>
> I try to use it on a archos 9 tablet PC, with tricks from that link and others:
> http://forum.archosfans.com/viewtopic.php?f=50&t=27303
>
> But no matter how hard I try, the touchscreen doesn't work on my archos 9
> PC tablet. I use the nomux option, the good serio1 on raw_device, the
> module is present ... But it's impossible to install the eGalaxy
> driver, I fall on the "no PS2 mouse present".
>
> I've tried this on Ubuntu 12.04 (with both vanilla & recompiled kernel to
> add touchkit.c module), debian 6.06 (kernel 2.6.32) and Bodhi linux (kernel
> 3.5) and to version of eGalaxy userland driver (the latest, and an old one
> 3.07)
>
> In fact the touch_kit_detect function failed on the first ps2_command
> (when it tried to send the 0xA 1 0xE.
>
> I'm sorry to bother you, but if you got some clue to make the touch screen
> work, I would be very gratefull.
>
> Yves.
>


from what I remember I just fixed some web addresses(no real code 
changes). best thing for you to do is try to contact the 
authors/maintainers of the code so that they can fix their code.

I added some Cc's

cheers,

Justin P. Mattock

           reply	other threads:[~2013-01-10 17:33 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CANe8kDHzsfnXJGtqrJUSwnRm2apQSc2WKCLhwQAayUog=wdPsA@mail.gmail.com>]

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=50EEFB62.2090303@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yves.duf@laposte.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.