From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Mon, 9 Sep 2013 15:35:55 +0200 Subject: [Buildroot] GTK+ for framebuffer? In-Reply-To: <20130909131647.GA4041@zuhnb712> References: <20130903100905.GA324@zuhnb712.ap.bm.net> <20130903133145.370bb2d4@skate> <20130904024019.GA875@zuhnb712.ap.bm.net> <20130904093510.031f559b@skate> <20130905060235.GA15735@zuhnb712.ap.bm.net> <20130905091054.51fd4ce0@skate> <20130909013956.GA15333@zuhnb712.ap.bm.net> <20130909090808.7513d104@skate> <20130909131647.GA4041@zuhnb712> Message-ID: <20130909153555.530a1e8a@skate> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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