From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] GTK+ for framebuffer?
Date: Mon, 9 Sep 2013 15:35:55 +0200 [thread overview]
Message-ID: <20130909153555.530a1e8a@skate> (raw)
In-Reply-To: <20130909131647.GA4041@zuhnb712>
Dear Woody Wu,
On Mon, 9 Sep 2013 21:16:47 +0800, Woody Wu wrote:
> Thanks for the example. Finally I found my command line was correct (I
> used tslib and has not yet tried evdev with success), the problem
> actually came from a xorg server bug in version 1.12.4 (which is used by
> buildroot 2013.08). I just fixed the bug in xorg and posted a patch on
> this list. The bug make the the xserver option such as "device=xxxx" is
> parsed as (key=device=, value=xxxx), but it should be (key=device,
> value=xxxx).
Ok.
> BTW: before I am going to try 'evdev', would you tell me what's the
> major difference between using 'evdev' and 'tslib' for my touchscreen?
> Which way is better? Thanks.
tslib is a userspace library that you can add between the evdev input
device and X.org to apply some additional filtering and other
algorithms on the touchscreen events. See the tslib documentation for
details.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-09-09 13:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 10:09 [Buildroot] GTK+ for framebuffer? Woody Wu
2013-09-03 11:31 ` Thomas Petazzoni
2013-09-04 2:40 ` Woody Wu
2013-09-04 7:35 ` Thomas Petazzoni
2013-09-05 6:02 ` Woody Wu
2013-09-05 7:10 ` Thomas Petazzoni
2013-09-05 8:19 ` Woody Wu
2013-09-09 1:39 ` Woody Wu
2013-09-09 7:08 ` Thomas Petazzoni
2013-09-09 13:16 ` Woody Wu
2013-09-09 13:35 ` Thomas Petazzoni [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=20130909153555.530a1e8a@skate \
--to=thomas.petazzoni@free-electrons.com \
--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