Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] eGalax Touchscreen
Date: Thu, 04 Oct 2012 18:40:42 +0200	[thread overview]
Message-ID: <506DBC0A.4030501@mind.be> (raw)
In-Reply-To: <CAA8O6f7aq+f95GQMLhLMx+4ystqCcj5JOMAnLDD01dQfRHU36g@mail.gmail.com>

On 03/10/12 11:39, Christian M?ller wrote:
> Hello all
> I'm trying to setup EGalax Touchscreen. The controller-ic is an etr-4000 usb.
> I patched the Kernel described in "eGTouch Linux Programming Guide v2.5c".
> (http://home.eeti.com.tw/web20/eGalaxTouchDriver/linuxDriver.htm)
> In dmesg output the controller is listet, but there is no /dev/uinput and no /dev/hidrawX devicefile.
> Device isn't also listet under /proc/bus/input/devices.
> What I have to do to get the touchscreen running?
> Any help will be welcome.

  This is not really a buildroot-related question, linux-input at vger.kernel.org
would be more appropriate.

  Still, some ideas:

- I never heard of /dev/uinput or /dev/hidraw.  Input devices can usually be
found in /dev/input/.  Perhaps you need udev rules to create /dev/uinput or
/dev/hidraw?

- Look in /sys/devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.0/input/input6
(and 7, 8, 9, 10); it should have an eventXX directory containing a 'dev' file.
That file contains the major:minor number of the (character) device node for
the input event device.  You should have a /dev/input/eventXX device node
with the same numbers.  That's the device you need.


  For future posts, please

- mention the buildroot and kernel versions you use;

- post a defconfig instead of a a full config;

- post text attachments with disposition:inline so people can quote them.


  Good luck!

  Regards,
  Arnout

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2012-10-04 16:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-03  9:39 [Buildroot] eGalax Touchscreen Christian Möller
2012-10-04 16:40 ` Arnout Vandecappelle [this message]
2012-10-05 18:57   ` Peter Korsgaard
2012-10-04 17:28 ` Belisko Marek

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=506DBC0A.4030501@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox