From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] eGalax Touchscreen
Date: Fri, 05 Oct 2012 20:57:11 +0200 [thread overview]
Message-ID: <874nm8ycfs.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <506DBC0A.4030501@mind.be> (Arnout Vandecappelle's message of "Thu, 04 Oct 2012 18:40:42 +0200")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Hi,
>> What I have to do to get the touchscreen running?
>> Any help will be welcome.
Arnout> This is not really a buildroot-related question,
Arnout> linux-input at vger.kernel.org would be more appropriate.
Or eGalaxy support for their non-upstream driver.
Arnout> Still, some ideas:
Arnout> - I never heard of /dev/uinput or /dev/hidraw. Input devices
Arnout> can usually be found in /dev/input/. Perhaps you need udev
Arnout> rules to create /dev/uinput or /dev/hidraw?
uinput is the interface for injecting input events into the kernel
(E.G. for userspace input drivers), and hidraw is the interface
to communicate with non-input devices (ab)using the hid protocol.
Arnout> For future posts, please
Arnout> - mention the buildroot and kernel versions you use;
Arnout> - post a defconfig instead of a a full config;
Arnout> - post text attachments with disposition:inline so people can
Arnout> quote them.
Indeed.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-10-05 18:57 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
2012-10-05 18:57 ` Peter Korsgaard [this message]
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=874nm8ycfs.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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